HP XC System Software Installation Guide Version 4.0

.
.
.
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 where a node is expected to be plugged in but is not found, a
message similar to the following appears:
Switch 172.20.65.3 port 31 ... Node at Switch 172.20.65.3,
Port 31 Not Found. Disabled node inserted in database.
The most common reasons for this are:
• The console port or node NIC is not plugged in.
• The node is not set to network boot.
After the discovery process is complete, a list of the nodes that were not found appears. Determine
why the node or nodes was not found and rerun the discover command with the
--replacenode= option to properly discover the node.
The discover command attempts to account for all the nodes that it expects to find. If the
discover command cannot account for all nodes, the missing node or nodes are assumed to
be at the end of the administration or branch switches. The discover command cannot determine
this situation without user intervention, however. Therefore, you are prompted to specify what
port is the last one used on the switch. As a result, the following messages are displayed:
Last port detected on switch 172.20.65.2 was port 37
Is this correct? [y/n] y
Last port detected on switch 172.20.65.5 was port 44
Is this correct? [y/n] y
Last port detected on switch 172.20.65.6 was port 43
Is this correct? [y/n] n
In this example, all nodes were found except the node at port 44 on switch 172.20.65.6.
Entering n creates a disabled node entry, which completes the expected number of nodes.
14.2 Troubleshooting the Cluster Configuration Process
The following list provides hints to troubleshoot problems you might encounter during the initial
configuration of the system with the cluster_config utility:
• Use the following command to view the node role assignments:
# shownode config | more
• The results of successful and unsuccessful services configuration are logged in the /var/
log/nconfig.log file on each node.
• DNS is not functioning or the IP address of the external connection on the head node is not
available from DNS when you see the following message:
gethostbyaddr failure
To resolve this problem, edit the /etc/resolv.conf file and fix incorrect DNS entries.
176 Troubleshooting