Hi David, Not sure I fully understand the problem as described (why would you need a terminal server for the nodes if you have an AMM?) but I'll try to answer. IBM BladeCenter AMMs should know which blade is in which slot. If the blades have been appropriately named in the AMM, you ought to be able to interrogate the AMM for which blade is in which slot, and use that data to generate a map file of blade -> bladecenter:slot.
In the AMM shell, you should be able to do "list -l 2" to get a 2-levels-deep list of all the installed targets. Write a script (expect, anyone?) to collect this info from the various AMMs/BladeCenters and write that to a map file. Then you can run a script like "console node45" which will automatically connect you to the right AMM and node. Re-run the script when blades get moved around. If expect isn't your thing, you can probably enable SNMP access to the AMM and query it that way. Let me know if this is helpful or if I've totally missed the point of your question. Jim On 6/13/11 17:56 , David Hardy wrote: > Greetings, fellow Linux lovers; > > Ran into a little situation today where we need to cycle power/reboot > a bunch of nodes that are down and out, by telnet to the relevant > terminal server ports and the advanced management module. This > involves multiple consoles, windows, command line, GUI, the works, as > follows: > > > > Subject: RHEL cluster, 4.0 through 5.3. > > Issue: How to find IP addresses of terminal server ports which > service individual nodes which are down and out. (need to telnet to > them for troubleshooting/maintenance/rebooting) > > And: IP address and/or hostname of advanced management module which > runs on the clusters > . > Some clusters have a "magic decoder ring" file that gives this > information; most don't. > > Any thoughts? Workaround so far has been via eyeballing racks of > blades and doing various arithmetic problems in our heads.
