Table 11. Troubleshooting the shared VLAN (continued)
1.
Can ping the Storage Node from the
Management Node but cannot ping the
Cluster Nodes
2.
Can ping the Cluster Nodes from the
Management Node but cannot ping the
Storage Nodes
3.
Cannot ping either the Storage Nodes or
the Cluster Nodes.
4.
Cannot ping the Cluster Nodes in one of
the expansion cabinets.
1.
Verify links between the Management
Node, Storage Nodes, Cisco 3550, 3500,
and 400x switches.
2.
Reboot the Management Node and press
F1 to enter SETUP. Verify that Ethernet
devices are turned on.
3.
Verify correct driver level for 1GB fibre
Ethernet. Verify status using the ifconfig
command.
4.
Verify the correct level of the driver is
installed for the 1 GB fibre ethernet
5.
Check the Cisco (3500,4003, or 4006)
switch for green status lights or system
and status LEDs. If the green lights are
on the switch is OK.
6.
Verify 1 GB fibre ethernet connections
are good by swapping a known good
cable to isolate the failing device.
7.
Replace the failing fibre cable, GBIC, or
network interface card.
If following the steps in Table 11 on page 60 did not correct the problem, continue
with the steps shown in “Cluster with one network”.
Cluster with one network
Ping failure on one or some nodes:
If one or more nodes experience a ping
failure, it indicates a problem with the node hardware or software.
1.
Attempt to telnet to the node via the serial console or KVM and verify the
node is operational.
a.
If telnet succeeds, check the
syslog
for errors.
1)
If there are errors, go to“Isolating software problems” on page 69 and
continue with the steps shown there.
2)
If there are no errors, it indicates a network problem. Go to Table 12 and
continue with the steps shown there.
b.
If telnet fails, it indicates a node hardware problem. Go to “Isolating
hardware problems” on page 63 for problem resolution.
Ping failure on all nodes:
If all nodes experience a ping failure, it indicates a
problem on one of the following:
v
Network. Go toTable 12 and continue with the steps shown there.
v
Network adapter on the Management Node.
v
DHCP configuration
v
Network configuration
v
Cisco blade failure
Table 12. Network troubleshooting for a cluster with one network
Symptom
Action
Chapter 10. Hardware/software problem determination
61
Summary of Contents for System Cluster 1350
Page 1: ...eServer Cluster 1350 Cluster 1350 Installation and Service IBM...
Page 2: ......
Page 3: ...eServer Cluster 1350 Cluster 1350 Installation and Service IBM...
Page 8: ...vi Installation and Service...
Page 10: ...viii Installation and Service...
Page 12: ...x Installation and Service...
Page 20: ...2 Installation and Service...
Page 30: ...12 Installation and Service...
Page 32: ...14 Installation and Service...
Page 52: ...34 Installation and Service...
Page 68: ...50 Installation and Service...
Page 70: ...52 Installation and Service...
Page 72: ...54 Installation and Service...
Page 74: ...56 Installation and Service...
Page 92: ...74 Installation and Service...
Page 96: ...78 Installation and Service...
Page 98: ...80 Installation and Service...
Page 104: ...86 Installation and Service...
Page 110: ...92 Installation and Service...
Page 124: ...106 Installation and Service...
Page 126: ...108 Installation and Service...
Page 138: ...120 Installation and Service...
Page 139: ...Part 4 Appendixes Copyright IBM Corp 2003 121...
Page 140: ...122 Installation and Service...
Page 144: ...126 Installation and Service...
Page 148: ...130 Installation and Service...
Page 154: ...136 Installation and Service...
Page 160: ...142 Installation and Service...
Page 169: ......
Page 170: ...IBMR Printed in U S A...