HP XC System Software Installation Guide Version 3.0

Some Console Ports Have Not Obtained Their IP Address
Use the following procedure to determine why all console ports have been discovered, but some have not
obtained their IP addresses after a reasonable time:
1. View 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, cycle power on the affected nodes. If more than a few nodes are affected, cycle
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).
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 or not 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:
.
.
.
Switch 172.20.65.3 port 4 ... Node Found
Switch 172.20.65.3 port 5 ... Node Found
Switch 172.20.65.3 port 6 ... NO Node Found
Switch 172.20.65.4 port 1 ... Node Found
.
.
.
In this case, a node is plugged into port 6 of the Branch Root switch at address 172.20.65.3. To resolve
the discovery problem, examine this node to see what actions it is taking during power-on. Is it booting from
the network? Is the proper network interface plugged into the switch?
After these issues are resolved, run the discover command again.
If discover encounters a port that it believes should have a node plugged into it, a message similar to the
following is displayed:
Switch 172.20.65.3 port 31 ... Node at Switch 172.20.65.3,
Port 31 Not Found. Disabled node inserted in database.
Troubleshooting the Discovery Process 143