Table of Contents
Advertisement
General checkout
The server diagnostic programs are stored in upgradable read-only memory (ROM)
on the system board. These programs are the primary method of testing the major
components of a server. Major components that can be tested include the system
board, Ethernet controller, video controller, RAM, keyboard, mouse (pointing
device), diskette drive, serial ports, hard drives, and parallel port. Not all servers
include all of these items; your hardware might differ. You can also use the
diagnostic programs to test some external devices. See "Diagnostic programs and
error messages" on page 15.
If you cannot determine whether a problem is caused by the hardware or by the
software, you can run the diagnostic programs to confirm that the hardware is
working properly.
When you run the diagnostic programs, a single problem might cause several error
messages. When this occurs, work to correct the cause of the first error message.
After the cause of the first error message is corrected, the other error messages
might not occur the next time you run the test.
A failed server might be part of a shared DASD cluster (two or more servers
sharing the same external storage device(s)). Prior to running diagnostics, verify
that the failing server is not part of a shared DASD cluster.
A server might be part of a cluster if:
v The customer identifies the server as part of a cluster.
v One or more external storage units are attached to the server and at least one of
v One or more servers are located near the failing server.
If the failing server is suspected to be part of a shared DASD cluster, all diagnostic
tests can be run except diagnostic tests which test the storage unit (DASD residing
in the storage unit) or the storage adapter attached to the storage unit.
Notes:
1.
2.
3.
4.
5.
6.
7.
© Copyright IBM Corp. 2003
the attached storage units is additionally attached to another server or
unidentifiable source.
For servers that are part of a shared DASD cluster, run one test at a time in
looped mode. Do not run all tests in looped mode, as this could enable the
DASD diagnostic tests.
If multiple error codes are displayed, diagnose the first error code displayed.
If the server stops working with a POST error, go to "Symptom-to-FRU index"
on page 115.
If the server stops working and no error is displayed, go to "Undetermined
problems" on page 143.
For information about power supply problems, see "Power supply LED errors"
on page 133.
For safety information, see "Safety information" on page 145.
For intermittent problems, check the error log; see "Error logs" on page 14.
1
Advertisement
Table of Contents
Troubleshooting
