IBM System Cluster 1350, Installation And Service

Page: 81 / 170

Table 13. (continued)
Myrinet switch 172.20.10.1 myri001
First iTouch port server 172.30.20.1 ts001
Second iTouch port server 172.30.20.2 ts002
RSA cards (bottom card) 172.30.30.1 rsa001
RSA cards (next card) 172.30.30.2 rsa002
RSA cards (Myrinet switch) 172.30.30.3
Cisco 4003 switch (console
management) 172.30.80.1 cisco4003–001
Cisco 10/100 switch 172.30.40.1 cisco3550–001
Cisco GB switch 172.30.50.1 cisco3508–001
APC Masterswitch 172.20.60.1 apc001
Remote Console Manager 172.30.70.1 rcm001
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.
1.
Attempt to telnet to the node via the serial console.
a. If telnet succeeds, check the syslog for errors.
1) If there are errors, go to “Isolating software problems” on page 69 for
software problem resolution.
2) If there are no errors, it indicates a user application problem.
b. If telnet fails, try using a serial communications program like
Hyperterminal to connect to the node. If you still can not connect it
indicates a node hardware problem. Go to “Isolating hardware problems”
for problem resolution.
Table 14. Network troubleshooting for a cluster with two networks
Symptom Action
1. Cannot ping a node or nodes on the
cluster network from the Management
Node, yet therconsole command and
access from the KVM work correctly. 1. Use the ifconfig command to verify that
the IP settings are correct.
2. Verify that the cables are fully plugged
into the switch and node, and that
everything is plugged into the correct
port. Refer to the cabling information
printed on each cable label and“VLAN
options” on page 17if you are unsure
where a cable belongs. Verify that the
link lights are on.
3.
Swap ports on the Ethernet switch with a
Cluster Node port you know is working.
4. Verify the Ethernet switch port is
configured for the Management VLAN.
Isolating hardware problems
Node checks
Table 15. Troubleshooting the remote console network
Symptom Action
Chapter 10. Hardware/software problem determination
63