Blade server light path diagnostics LEDs

Use this information to diagnose and resolve possible errors displayed by the light path diagnostic LEDs.

The following table describes the LEDs on the light path diagnostics panels, on the system board, and on the optional expansion unit and suggested actions to correct the detected problems.

Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. See Parts listing to determine which components are consumable, structural, or CRU parts. If an action step is preceded by "(trained technician only)," that step must be performed only by a trained technician.
Lit light path diagnostics LED	Description	Action
None	An error has occurred and cannot be isolated, or the service processor has failed.	Make sure that the light path diagnostics LED is lit, to ensure that there is enough power in the blade server to light the rest of the LEDs. See Viewing the light path diagnostics LEDs in the blade server. Check the BMC log for information about an error that is not represented by a light path diagnostics LED. See Using the Setup utility.
Battery error	The system battery is not installed or is not working.	Reseat the battery. See Removing the battery and Installing the battery. Replace the battery. See Removing the battery and Installing the battery.
DIMM x error	A memory error occurred.	Look for system-event and IMM/AMM logs related to memory and resolve those events (see IMM error messages and UEFI/POST error codes).
Front panel missing error	The front control panel is not installed correctly.	Make sure that the front control panel is installed correctly and the control panel cable is installed securely on the system board (see Installing the control panel).
LP active	The system board light path LEDs have power.	Check for error LEDs that are lit on the system board. If this LED fails to light, install the blade server in a chassis for approximately 2 hours to enable the light path diagnostics panel to charge.
Microprocessor error	The microprocessor has failed or overheated, or the start microprocessor is missing.	Check the Integrated Management Module (IMM) log for more information. See Viewing event logs through the Setup utility. If the log shows that a microprocessor is disabled or that a microprocessor error has occurred, perform one of the following actions: (Trained technician only) Reseat the microprocessor that is indicated by the lit LED. See Removing a microprocessor and heat sink and Installing a microprocessor and heat sink. (Trained technician only) Replace the microprocessor that is indicated by the lit LED. See Removing a microprocessor and heat sink and Installing a microprocessor and heat sink.
Microprocessor mismatch	Microprocessor mismatch.	Make sure that microprocessors 1 and 2 are identical (number of cores, cache size and type, clock speed, internal and external clock frequencies). Verify the type of microprocessors installed by using the Configuration/Setup utility. See Using the Setup utility. (Trained technician only) Replace microprocessor 2 with an identical microprocessor to microprocessor 1. See Removing a microprocessor and heat sink and Installing a microprocessor and heat sink.
NMI error	The system board has failed.	Replace the blade server cover, reinsert the blade server in the BladeCenter unit, and then restart the blade server. Check the BMC log for information about the error. See Using the Setup utility. (Trained technician only) Replace the system-board assembly. See Removing the system-board assembly and Installing the system-board assembly.
SAS x error	A storage drive has failed.	Run the SAS Attached Disk diagnostic test. If the drives passes diagnostics but continues to have a problem, replace the storage drive with a new one. See IBM Dynamic System Analysis Preboot diagnostic program.
System board error	The system board has failed.	(Trained technician only) Replace the system-board assembly. See Removing the system-board assembly and Installing the system-board assembly.
Temperature error	The system temperature has exceeded a threshold level.	Check the function of the shared BladeCenter unit resources. See Solving shared BladeCenter resource problems. Make sure the air vents are not blocked and that all blade bays in the BladeCenter unit have a blade server or a blade filler installed. Make sure that the room temperature is not too high. See Features and specifications for temperature information.

Give documentation feedback