IBM eserver Cluster 1350, Installation And Service Manual

Page: 61 / 122

v
Go to “Node checks” on page 42 and perform node checks.
Checking storage
Use the following information to resolve fibre-storage network failures:
Table 18. Troubleshooting the fibre-storage network
Symptom Action
Cannot see disk drives from
the storage node.
1. Reboot the storage node and press the Alt/Q keys to
go into Qlogic setup. Make sure that the FAStT700 is a
listed device.
2. Check the fibre connections between the server host
bus adapter (HBA) and the hubs on the FAStT700. The
green connection LED should be lit.
3. Check cabling on the FastT outbound hubs to the
storage expansion units. Look for link lights and proper
cabling. Also make sure that all transfer rate speed
switches are set to 2 Gigabytes.
4. Check the Blade Server and Enhanced System
Manager (ESM) firmware levels and update to current
levels.
If following the steps in Table 18 did not correct the problem, continue with the
steps shown in “File system failure.”
File system failure
Check disks using fdisk -l :
v If fdisk -l completes without error, go to “GPFS checks” on page 49 and
continue with the file system problem resolution.
v If fdisk -l reports missing disks, check that the adapter device driver is
configured:
– If the adapter device driver is configured, go to “Checking storage” and
continue with storage subsystem problem resolution.
– If the adapter device driver is not configured, check the adapter hardware and
then refer to the applicable documentation that came with your software and
complete the problem resolution process.
PFA alert indicates internal disk
Go to “Checking storage” and perform disk problem resolution.
I/O errors in syslog
Complete the problem resolution for the indicated disk, adapter, or storage
subsystem.
Ping failure over the Ethernet
Check the nodes using the rconsole command or ping nodes using the Myrinet
switch:
v If the node responds, refer to the applicable documentation that came with the
switch and complete the problem resolution process.
v
If the node does not respond, go to “Node checks” on page 42 and continue with
Node checks.
Ping failure over a Myrinet switch
Check the nodes using the rconsole command or ping nodes via the Ethernet:
v If node responds, go to “Configuring SNMP alerts from Myrinet” on page 49 and
continue with Myrinet problem resolution.
Chapter 8. Troubleshooting hardware and software problems
45