Checkout Procedure; About The Checkout Procedure; Performing The Checkout Procedure - IBM System x3550 M3 Type 4254 Problem Determination And Service Manual

Checkout procedure

The checkout procedure is the sequence of tasks that you should follow to
diagnose a problem in the server.

About the checkout procedure

Before you perform the checkout procedure for diagnosing hardware problems,
review the following information:
v Read the safety information that begins on page vii.
v The diagnostic programs provide the primary methods of testing the major
v When you run the diagnostic programs, a single problem might cause more than
v Before you run the diagnostic programs, you must determine whether the failing
v If the server is halted and a POST error code is displayed, see "Error logs" on
v For information about power-supply problems, see "Solving power problems" on
v For intermittent problems, check the error log; see "Error logs" on page 25 and

Performing the checkout procedure

To perform the checkout procedure, complete the following steps:
1. Is the server part of a cluster?
82
IBM System x3550 M3 Types 4254 and 7944: Problem Determination and Service Guide
components of the server, such as the system board, Ethernet controller,
keyboard, mouse (pointing device), serial ports, and hard disk drives. You can
also use them to test some external devices. If you are not sure whether a
problem is caused by the hardware or by the software, you can use the
diagnostic programs to confirm that the hardware is working correctly.
one error message. When this happens, correct the cause of the first error
message. The other error messages usually will not occur the next time you run
the diagnostic programs.
Exception: If multiple error codes or light path diagnostics LEDs indicate a
microprocessor error, the error might be in the microprocessor or in the
microprocessor socket. See "Microprocessor problems" on page 92 for
information about diagnosing microprocessor problems.
server is part of a shared hard disk drive cluster (two or more servers sharing
external storage devices). If it is part of a cluster, you can run all diagnostic
programs except the ones that test the storage unit (that is, a hard disk drive in
the storage unit) or the storage adapter that is attached to the storage unit. The
failing server might be part of a cluster if any of the following conditions is true:
– You have identified the failing server as part of a cluster (two or more servers
sharing external storage devices).
– One or more external storage units are attached to the failing server and at
least one of the attached storage units is also attached to another server or
unidentifiable device.
– One or more servers are located near the failing server.
Important: If the server is part of a shared hard disk drive cluster, run one test
at a time. Do not run any suite of tests, such as "quick" or "normal" tests,
because this might enable the hard disk drive diagnostic tests.
page 25. If the server is halted and no error message is displayed, see
"Troubleshooting tables" on page 84 and "Solving undetermined problems" on
page 155.
page 154.
"Diagnostic programs and messages" on page 115.