HP XC System Software Installation Guide Version 3.1

http://www.docs.hp.com/en/highperfcomp.html
The remainder of this section provides troubleshooting hints to help you solve some common problems
that may occur during the discovery process. The following conditions are described:
• “Discovery Process Hangs While Discovering Console Ports” (page 190)
• “ProCurve Switches Do Not Obtain Their IP Addresses” (page 190)
• “ProCurve Switches May Take Time to Get IP Addresses” (page 190)
• “Not All Console Ports Are Discovered” (page 190)
• “Some Console Ports Have Not Obtained Their IP Addresses” (page 191)
• “Not All Nodes Are Discovered” (page 191)
After performing the suggested corrective action, rerun the discover command.
Important Note About HP BladeSystems and Enclosures:
Troubleshooting procedures differ if your hardware configuration contains HP server blades and enclosures.
For more information, see the HP XC Systems With HP Server Blades and Enclosures HowTo, which is available
at the following Web site:
http://www.docs.hp.com/en/highperfcomp.html
N.1.1 Discovery Process Hangs While Discovering Console Ports
This information applies only to HP XC systems with nodes that use Integrated Lights Out (iLO) as the
console management device.
If the discovery process hangs when it tries to discover the console ports (that is, those named cp-n), it
may be because the iLO console management devices do not have telnet enabled. See Appendix C
(page 119), which describes how to enable telnet on iLO devices.
N.1.2 ProCurve Switches Do Not Obtain Their IP Addresses
The discovery process requires the correct MAC address of the Root Administration Switch to discover
the hardware components in the system. The Root Administration Switch in an HP XC system is typically
a ProCurve 2848 or a ProCurve 2824 switch.
To determine which switch is the Root Administration Switch, look for the switch that has the head node's
NIC plugged into port 42 (for the ProCurve 2848) or port 22 (for the ProCurve 2824) of the switch.
During the discovery process, do not provide the MAC address of the Root Console switch, typically a
ProCurve 2650 or ProCurve 2626 switch, which may have the console port for the head node plugged into
port 42.
If the correct MAC address has been provided to the discover command, and the switch has not obtained
its address, you may need to reset the ProCurve switch before running the discover command. At
power-up, the ProCurve switch will query the network for an IP address using DHCP. If a response is not
received, the switch continues to query for an address but at a decreasing rate of frequency.
The discover command waits a maximum of 10 minutes for the ProCurve switch to obtain an address
before terminating the process.
To reset the switch, press the front panel reset button, or log in to the switch through the serial cable and
issue the reset command.
N.1.3 ProCurve Switches May Take Time to Get IP Addresses
By default, ProCurve switches are configured to obtain their IP address using DHCP/Bootp. If the switch
does not receive an address, it continues to periodically send DHCP requests, with decreasing frequency.
The discovery process waits up to 10 minutes for any one switch to obtain its IP address. If the discover
process times out because it cannot communicate with a switch, reset all the switches in the cluster before
attempting to run the discover command again. This forces the switches to immediately start sending
DHCP requests again.
N.1.4 Not All Console Ports Are Discovered
The discovery process queries the ProCurve switches to obtain the MAC addresses of all console ports.
The MAC addresses are logged in the switch as the console port device issues a DHCP request to get an
IP address.
190 Troubleshooting