IBM BladeCanter HS20 Installation And User Manual page 78

Table 5. Light Path Diagnostics (continued)
Lit blade-error
LED Cause
DIMM x error A memory error occurred.
Processor x error The microprocessor has failed.
Temperature error The system temperature has exceeded a
threshold level.
System board error The system board has failed
IDE bus x error The IDE bus indicated by the error LED has
failed.
NMI error The system board has failed.
Processor The processors do not match.
mismatch
64
BladeCenter HS20 Type 8832: Installation and User's Guide
Action
Replace the DIMM indicated by the lit DIMM
failure LED.
Note: Multiple DIMM LEDs do not necessarily
indicate multiple DIMM failures. If more than
one DIMM LED is lit, reseat or replace one
DIMM at a time until error goes away. Check
the system error log in the BladeCenter
management module for information about the
error.
If the problem remains, have the blade server
serviced.
Verify that the microprocessor indicated by the
lit LED is installed correctly. (See "Installing an
additional microprocessor" on page 25 for
installation instructions.)
If the problem remains, have the
microprocessor replaced.
1. Check to see if a blower on the
BladeCenter unit has failed. If it has,
replace the fan.
2. Make sure the room temperature is not too
high. (See "Features and specifications" on
page 5 for temperature information.)
If the problem remains, have the blade server
serviced.
Replace the blade server cover, reinsert the
blade server in the BladeCenter unit, and then
restart the server.
If the problem remains, have the blade server
serviced.
Have the blade server serviced.
1. Replace the blade server cover, reinsert
the blade server in the BladeCenter unit,
and then restart the server.
2. Check the system error log in the
BladeCenter management module for
information about the error.
If the problem remains, have the blade server
serviced.
Verify that microprocessors 1 and 2 have the
same cache size and type and the same clock
speed. Internal and external clock frequencies
must be identical.
If the problem remains, have the blade server
serviced.