Performing the checkout procedure
To perform the checkout procedure, complete the following steps:
1. Is the server part of a cluster?
2. Complete the following steps:
3. Did a single beep sound and are there readable instructions on the main menu?
Checkpoint codes (trained service technicians only)
A checkpoint code identifies the check that was occurring when the server stopped;
it does not provide error codes or suggest replacement components. Checkpoint
codes are shown on the checkpoint display, which is on the I/O board. By using the
checkpoint display, you do not have to wait for the video to initialize each time you
restart the server.
There are two types of checkpoint codes: CPLD hardware checkpoint codes and
BIOS checkpoint codes. The BIOS checkpoint codes might change when the BIOS
code is updated.
For a list of checkpoint codes for the xSeries 460 or MXE 460 server, see
http://w3.pc.ibm.com/helpcenter/infotips/techinfo/MIGR-58350.html.
v No: Go to step 2.
v Yes: Shut down all failing servers that are related to the cluster. Go to step 2.
a. Turn off the server and all external devices.
b. Check all cables and power cords.
c. Set all display controls to the middle positions.
d. Turn on all external devices.
e. Turn on the server. If the server does not start, see "Troubleshooting tables"
on page 36.
f. Check the system-error LED on the operator information panel. If it is
flashing, check the light path diagnostics LEDs (see "Light path diagnostics"
on page 49).
g. Check for the following results:
v Successful completion of POST, indicated by a single beep
v Successful completion of startup, indicated by a readable display of the
operating-system desktop
v No: Find the failure symptom in "Troubleshooting tables" on page 36; if
necessary, see "Solving undetermined problems" on page 90.
v Yes: Run the diagnostic programs (see "Running the diagnostic programs" on
page 59).
– If you receive an error, see "Diagnostic error codes" on page 60.
– If the diagnostic programs were completed successfully and you still
suspect a problem, see "Solving undetermined problems" on page 90.
35
Chapter 2. Diagnostics