IBM eServer 445 xSeries Hardware Maintenance Manual And Troubleshooting Manual page 72

Follow the steps in this checkout procedure to identify server problems.
Note: For a 16-way configuration, the server must be started up as a standalone
62
xSeries 445 Type 8870: Hardware Maintenance Manual and Troubleshooting Guide
server (see "Starting the diagnostic programs" on page 70).
001
IS THE SERVER PART OF A CLUSTER?
YES. Schedule maintenance for the server. Shut down all servers related to
the cluster. Run the storage test.
NO. Go to step 002 .
002
IF THE SYSTEM IS NOT PART OF A CLUSTER:
If the operating system is running, do the following:
1. Check the Light Path (see "Light path LED errors" on page 190).
2. Check the service processor system-error logs.
a. If the system-error log indicates a damaged field replaceable unit
(FRU), replace the FRU, and run diagnostics to confirm that the
problem has been solved.
b. If the system-error log does not indicate a damaged FRU, see "Error
symptoms" on page 230 and "Undetermined problems" on page
246.
If the operating system is not running, do the following:
1. Check the Light Path (see "Light path LED errors" on page 190).
2. Check the service processor system-error logs.
a. If the error log indicates a damaged field replaceable unit (FRU),
replace the FRU, and run diagnostics to confirm that the problem
has been solved.
b. If the error log does not indicate a damaged FRU, check the
operating system event logs; if these logs do not specify a particular
error, go to step 3.
3. Turn off the server and all external devices.
4. Check all cables and power cords.
5. Set all display controls to the middle position.
6. Turn on all external devices.
7. Turn on the server.
8. Monitor the screen and the serial port for POST errors, and record any
POST error messages that are displayed on the screen. If an error is
displayed, look up the first error (see "POST error codes" on page 224).
9. Run diagnostics (see "Starting the diagnostic programs" on page 70).
003
DID THE DIAGNOSTIC PROGRAM START?
NO. Find the failure symptom in "Error symptoms" on page 230.
YES. Run the diagnostic programs. If necessary, see "Diagnostic programs
and error messages" on page 68.
If you receive an error, see Chapter 7, "Symptom-to-FRU index," on page
187.
If the diagnostic programs were completed successfully and you still
suspect a problem, see "Undetermined problems" on page 246.
If the server does not turn on, see "Error symptoms" on page 230.