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 DSA Preboot diagnostic programs provide the primary methods of testing the
major components of the server, such as the system board, Ethernet controller,
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.
v
When you run the diagnostic programs, a single problem might cause more than
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 LEDs indicate a microprocessor error, the
error might be in a microprocessor or in a microprocessor socket. See
“Microprocessor problems” on page 145 for information about diagnosing
microprocessor problems.
v
Before you run the DSA diagnostic programs, you must determine whether the
failing 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.
v
If the server is halted and a POST error code is displayed, see “Error logs” on
page 125. If the server is halted and no error message is displayed, see
“Troubleshooting tables” on page 139 and “Solving undetermined problems” on
page 229.
v
For information about power-supply problems, see “Solving power problems” on
page 227.
v
For intermittent problems, check the error log; see “Error logs” on page 125 and
“Diagnostic programs and messages” on page 155.
Chapter 5. Diagnostics
137
Summary of Contents for 4367
Page 1: ...System x3200 M2 Types 4367 and 4368 Problem Determination and Service Guide ...
Page 2: ......
Page 3: ...System x3200 M2 Types 4367 and 4368 Problem Determination and Service Guide ...
Page 32: ...14 System x3200 M2 Types 4367 and 4368 Problem Determination and Service Guide ...
Page 50: ...32 System x3200 M2 Types 4367 and 4368 Problem Determination and Service Guide ...
Page 64: ...46 System x3200 M2 Types 4367 and 4368 Problem Determination and Service Guide ...
Page 138: ...120 System x3200 M2 Types 4367 and 4368 Problem Determination and Service Guide ...
Page 258: ...240 System x3200 M2 Types 4367 and 4368 Problem Determination and Service Guide ...
Page 265: ......
Page 266: ... Part Number 49Y0163 Printed in USA 1P P N 49Y0163 ...