IBM eserver Cluster 1350, Installation And Service Manual

Page: 63 / 122

Troubleshooting the KVM network
Use the following troubleshooting information to resolve KVM network failures:
Table 20. Troubleshooting the KVM network
Symptom Action
The Keyboard/Video/Mouse
(KVM) switch selector shows
some or all systems are
non-active (indicated by a red
X) but the system is turned
on.
1. Check that the connections for the KVM harness on the
back of the system are securely plugged in.
2. Check the connection of the inbound/outbound Cat 5
connections on the KVM switch conversion dongle.
3. Check that the link LED on the dongle is lit. If the LED
is lit, a good connection exists with the node keyboard
port. If no link LED is lit and you are having problems
with KVM connectivity, replace the dongle (FRU
32P1654).
4. Make sure that the terminator is in place at the first
dongle on the KVM chain.
5. Use a known good Cat 5 (straight through) cable to
direct connect or bypass possible bad cables.
6. Reboot the failing node to reset connection to the KVM
switch.
File-system failure
Use the following information to resolve file-system failures:
To check the disks, at the command prompt, type:
fdisk -l
v
If
fdisk -l
completes, 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” on page
45 and continue with storage subsystem problem resolution.
– If the adapter device driver is not configured, check the adapter hardware and
then go to the applicable Linux documentation that came with your software
and resolve the configuration issue.
PFA alert indicates internal disk
Go to “Checking storage” on page 45 and perform disk problem resolution.
I/O errors in syslog
Complete the problem resolution for the indicated disk, adapter or storage
subsystem.
Chapter 8. Troubleshooting hardware and software problems
47