HP XC System Software Installation Guide Version 4.0

NOTE: If the --oldmp option was used on the discover command line, it is assumed that
all Management Processors (MPs) have their IP addresses set statically, and therefore are not
subject to this step in the discovery process.
If some console ports are not configured to use DHCP, they will not be discovered. Therefore,
the first item to verify is whether the nondiscovered console ports are configured to use DHCP.
If all console ports are properly configured to use DHCP, verify the wiring against the descriptions
in the HP XC Hardware Preparation Guide. It is important to point out that because of hardware
limitations in the ProCurve switch, empty ports are included in the port layout.
14.1.5 Some Console Ports Have Not Obtained Their IP Addresses
Use the following procedure to determine why all console ports have been discovered, but some
console ports have not obtained their IP addresses after a reasonable time.
1. View the last 10 lines of the system log file:
# tail -f /var/log/messages
2. Look for instances where a network component issues a DHCPREQUEST, the head node sends
back a DHCPOFFER, but the console port does not send back a corresponding DHCPACK. For
example:
Sep 7 09:47:46 src_s@n4 dhcpd: DHCPDISCOVER from 00:30:6e:22:66:02 \
via eth1
Sep 7 09:47:46 src_s@n4 dhcpd: DHCPOFFER on 172.21.0.3 to \
00:30:6e:22:66:02 via eth1
Sep 7 09:47:46 src_s@n4 dhcpd: DHCPREQUEST for 172.21.0.14 from \
00:30:6e:22:66:02 via eth1
eth1
3. If this is the case, turn on and turn off power on the affected nodes. If more than a few nodes
are affected, turn on and turn off power on the nodes in the cabinet.
IMPORTANT: Just turning the power off on the node is not sufficient because power is
present on the console port whenever AC power is present. To totally reset a node, you must
remove power by unplugging the node or by using the circuit breakers on the cabinet power
distribution unit (PDU).
14.1.6 Not All Nodes Are Discovered
In much the same way as the console ports are queried, the discovery process queries the ProCurve
switches to obtain the MAC address of a node. For the discovery process to do this, the nodes
must be configured to boot off the network interface that is connected to the Root Administration
Switch. If the node is not configured to network boot, it is likely that the node will not be properly
discovered.
The discovery process uses the number of nodes as a checkpoint to determine whether it has
discovered all the nodes in the system. As a result, the system checks the ports on a switch for
an open port. If one is found, this does not necessarily indicate a problem but rather where the
nodes on the particular switch end.
When this nonresponding port is found, the discovery process proceeds to the next switch in
the list. It will do this until it discovers all nodes or runs out of ports. As a result, it is important
that all nodes in the cluster be available during the discovery process.
To determine what node failed in the discover process, examine the output of the discover
command when it is parsing the switch output to gather the node input. For example, assume
that the following was displayed during the discovery process:
14.1 Troubleshooting the Discovery Process 175