IBM eserver Cluster 1350, Installation And Service Manual

Page: 57 / 122

Ping failure on all nodes on both networks
If all nodes on both networks experience a ping failure, it indicates a problem with
the system software or a user application. Telnet or use SSH to connect to the node
through the serial console:
1. If telnet or SSH succeeds, check the syslog for errors.
a. If there are errors, go to “Isolating software problems” on page 48 for
software problem resolution.
b. If there are no errors, this indicates a user application problem.
2. If telnet or SSH fails, connect to the node using a serial communications
program, like, Hyperterminal. If you still cannot connect it indicates a node
hardware problem. Go to “Isolating hardware problems” on page 42 for problem
resolution.
Table 15. Network troubleshooting for a cluster with two networks
Symptom Action
Cannot ping a node or nodes
on the cluster network from
the management node, yet the
rconsole command and
access from the KVM work
correctly.
1. Use the ifconfig command to make sure that the IP
address settings are correct.
2. Make sure that the cables are fully plugged into the
switch and node, and that everything is plugged into the
correct port. See the cabling information printed on
each cable label and“VLAN options” on page 14if you
are unsure where a cable belongs. Make sure that the
link LEDs are lit.
3. Swap ports on the Ethernet switch with a known
working cluster node port.
4. Make sure that the Ethernet switch port is configured
for the management VLAN.
Chapter 8. Troubleshooting hardware and software problems
41