IBM LS42 - BladeCenter - 7902, Руководство по обслуживанию

Страница: 101 / 194

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 light path diagnostics LEDs indicate a
microprocessor error, the error might be in a microprocessor or in a
microprocessor socket. See “Microprocessor problems” on page 93 for
information about diagnosing microprocessor problems.
v
If the blade server is halted, review and follow the instructions that are
displayed. If the blade server is halted and no error message is displayed, see
“Troubleshooting tables” and “Solving undetermined problems” on page 164.
v
For intermittent problems, check the error log; see “Error logs” on page 72.
v
If no LEDs are lit on the blade server front panel, verify the blade server status
and errors in the management-module Web interface; also see “Solving
undetermined problems” on page 164.
v
If device errors occur, see “Troubleshooting tables.”
Performing the checkout procedure
To perform the checkout procedure, complete the following steps:
1. If the blade server is running, turn off the blade server (see “Turning off the
blade server” on page 6).
2. Turn on the blade server (see “Turning on the blade server” on page 5). Make
sure that the blade server has control of the video (the KVM button is lit). If the
blade server does not start, see “Troubleshooting tables.”
3.
Record any POST beep codes that sound or POST error messages that are
displayed on the monitor. If an error is displayed, follow the recommended
steps that are also displayed (see “POST” on page 65).
4. Check the control panel blade-error LED; if it is lit, check the light path
diagnostics LEDs (see “Light path diagnostics” on page 103).
5. 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
6.
Did a single beep sound and are there readable instructions on the main menu?
v
No: Find the failure symptom in “Troubleshooting tables”; if necessary, see
“Solving undetermined problems” on page 164.
v
Yes: Run the diagnostic programs (see Chapter 5, “Diagnostics,” on page 65).
– If you receive an error, see Chapter 5, “Diagnostics,” on page 65.
– If the diagnostic programs were completed successfully and you still
suspect a problem, see “Solving undetermined problems” on page 164.
Troubleshooting tables
Use the troubleshooting tables to find solutions to problems that have identifiable
symptoms. If these symptoms relate to shared BladeCenter unit resources, see
“Solving shared BladeCenter resource problems” on page 160.
If you cannot find a problem in these tables, see Chapter 5, “Diagnostics,” on page
65 for information about testing the blade server.
Chapter 5. Diagnostics
89