IBM System Cluster 1350, Установка и обслуживание

Страница: 85 / 170

Storage checks
Table 17. Troubleshooting the Fibre Storage network
Symptom Action
1. Cannot see disk drives from the Storage
Node 1. Reboot the Storage Node and press the
Alt/Q
keys to go into Qlogic setup.
Verify that the 700 FastT is a listed
device.
2. Check the Fibre connections between the
server HBA and the hubs on the 700
FastT. Green connection lights hould be
on.
3.
Check cabling on the 1742 FastT
outbound hubsw to the storage
expansion units. Look for links lights
and proper cabling. Also verify that all
transfer rate speed switches are set to 2
gigabytes.
4. Check blade and ESM firmware levels
and update to current levels.
If following the steps in Table 17 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, go to “GPFS” on page 72 and continue with the file system
problem determination.
v
If fdisk -l reports missing disks, check that the adapter device driver is
configured
– If the adapter device driver is configured, go to “Storage” on page 73 and
continue with storage subsystem problem determination.
– If the adapter device driver is not configured, check the adapter hardware
and then go to “Linux” on page 72 and continue with Linux problem
determination.
PFA alert indicates internal disk: Go to “Storage” on page 73 and perform disk
problem determination.
I/O errors in syslog: Execute problem determination for the indicated disk,
adapter or storage subsystem.
Ethernet checks
Ping failure over Ethernet:
Check nodes using rconsole command or ping nodes
via Myricom:
v
If node responds, go to “Cisco switches” on page 73 and continue with Ethernet
problem determination.
v
If command fails, go to “Node” on page 72 and continue with Node checks.
Myricom checks
Ping failure over Myricom: Check nodes using rconsole command or ping nodes
via Ethernet:
v
If node responds, go to “Myrinet” on page 73 and continue with Myricom
problem determination.
v
If command fails, go to “Node” on page 72 and continue with Node checks.
Chapter 10. Hardware/software problem determination
67