David> Ran into a little situation today where we need to cycle David> power/reboot a bunch of nodes that are down and out, by telnet David> to the relevant terminal server ports and the advanced David> management module. This involves multiple consoles, windows, David> command line, GUI, the works, as follows: David> Subject: RHEL cluster, 4.0 through 5.3. David> Issue: How to find IP addresses of terminal server ports which David> service individual nodes which are down and out. (need to David> telnet to them for troubleshooting/maintenance/rebooting) I use 'conserver' (http://www.conserver.org) to manage a bunch of serial console ports. Works great to map the hostname to it's console. It supports telnet/ipmi access too, but I haven't used that feature yet. So I just do 'console <hostname>' and I get connected to the terminal server which holds the serial port without me having to remember anything. David> And: IP address and/or hostname of advanced management module David> which runs on the clusters . Some clusters have a "magic David> decoder ring" file that gives this information; most don't. Why don't you stuff this info into DNS? <hostname>-ilom/ilo/rlm/mgt is how we do things here, so I don't have to remember IPs, I just goto the right hostname. David> Any thoughts? Workaround so far has been via eyeballing racks David> of blades and doing various arithmetic problems in our heads. Yuck. Be lazy. Write it out once on install and stuff the info in DNS. Even if it's just an internal sub-domain which does the management interfaces. host.mgt.work.com would be one way. More details on how you do things now would be helpful too. John