IPMI Forward Progress Log Monitor (Events)

Event 8039

WBEM Severity: Critical
Event Summary: SMI training has failed
Event Description: SMI training has failed. Data field contains the physical location of the memory controller.
Probable Cause: Transmit Failure
Event Category: System Hardware
Event Sub-Category: Unknown
Cause 1: SMI (Scalable Memory Interconnect) link training has failed.
Recommended Action 1: If seating is not an issue, replace the EMB (Extended Memory Buffer), followed by the CPU. If not resolved, call support.

Event 8040

WBEM Severity: Critical
Event Summary: DIMM at field location has been previously deallocated and remains deallocated
Event Description: DIMM at field location has been previously deallocated and remains deallocated.
Probable Cause: Transmit Failure
Event Category: Memory
Event Sub-Category: DIMM
Cause 1: A DIMM has been deallocated due to failure during memory init sequence. The most probable cause is a faulty DIMM. Other possible causes could be due to SMI failure, DDR3 training failure, or bad SMB (Scalable Memory Buffer) initialization.
Recommended Action 1: The first action will be to replace the DIMM. If that does not solve the issue, replace CPU. If problem still continues to exist, replace the system board.

Event 8044

WBEM Severity: Degraded/Warning
Event Summary: Multi-blade conjoined rendezvous has failed
Event Description: Multi-blade conjoined rendezvous has failed
Probable Cause: SBL (Scalable Blade Link) or CPU
Event Category: System Hardware
Event Sub-Category: Unknown
Cause 1: Event occurs when rendezvous among all known logical processors does not occur. All processors need to checkin with the monarch processor.
Recommended Action 1: Check if the SBL (Scalable Blade Link) connector is damaged. Replace if damaged. If not, check, then replace processor. If problem persists, contact Support.

Event 8045

WBEM Severity: Information
Event Summary: Unable to fully allocate memory to optimize interleaving ranges
Event Description: Unable to fully allocate memory to optimize interleaving ranges.
Probable Cause: Unknown
Event Category: Memory
Event Sub-Category: DIMM
Cause 1: Memory configuration is likely to be incorrect. Mixed DIMMs or possible deallocated DIMMs can cause this issue.
Recommended Action 1: Check memory configuration. If not optimal loading, replace the affected DIMMs. If problem persists, refer to the Service Guide for proper DIMM load order.

Event 8046

WBEM Severity: Degraded/Warning
Event Summary: Expected blades failed to rendezvous at memory checkpoint
Event Description: Expected processor failed to rendezvous at memory checkpoint. Data field displays which processors checked in.
Probable Cause: SBL (Scalable Blade Link) or CPU
Event Category: System Hardware
Event Sub-Category: Unknown
Cause 1: Processors failed to rendezvous at memory checkpoint
Recommended Action 1: Reboot. If problem persists, replace SBL (Scalable Blade Link), if applicable. If this does not resolve, then replace processor, then contact Support.

Event 8047

WBEM Severity: Degraded/Warning
Event Summary: Expected blades failed to rendezvous at memory test checkpoint
Event Description: Expected blades failed to rendezvous at memory test checkpoint. The data represents the processor thread(s) that has rendezvous with the system. If bit0 is set to 0, it means thread 0 has is missing. If bit is set to 0, it means thread is missing. In the 9300 series processors, each set of 8 threads belongs to one processor in the system.
Probable Cause: Transmit Failure
Event Category: Processor
Event Sub-Category: Checkpoint
Cause 1: Expected processors failed to rendezvous at memory test checkpoint
Recommended Action 1: Reseat the SBL and Reboot. If problem still exists, then replace the processor belonging to the missing thread (see event description for data mask). If problem persists, then contact Support.

Event 8066

WBEM Severity: Fatal/Nonrecoverable
Event Summary: System topology (CPUs and IOHs) discovered is not a supported topology.
Event Description: System topology (CPUs and IOHs) discovered is not a supported topology.
Probable Cause: Transmit Failure
Event Category: System Hardware
Event Sub-Category: Unknown
Cause 1: A QPI hardware error may have occurred.
Recommended Action 1: Try rebooting the server. If problem persists contact support.

Event 8067

WBEM Severity: Fatal/Nonrecoverable
Event Summary: Could not find default QPI data.
Event Description: Could not find default QPI data.
Probable Cause: Transmit Failure
Event Category: System Hardware
Event Sub-Category: Unknown
Cause 1: A hardware error may have occurred.
Recommended Action 1: Try rebooting the server. If problem persists contact support.

Event 8068

WBEM Severity: Degraded/Warning
Event Summary: Detected a CPU QPI link's operation is degraded.
Event Description: A QPI link on the processor is degraded. An additional QPI_CPU_LINK_DEGRADED event or QPI_IOH_LINK_DEGRADED event will be logged to indicate the physical location information for the processor or IOH on the other side of the degraded QPI link.
Probable Cause: QPI link error
Event Category: System Interconnect
Event Sub-Category: QPI link
Cause 1: QPI link hardware has been detected operating with degraded performance.
Recommended Action 1: Reboot. If problem persists contact support.

Event 8080

WBEM Severity: Fatal/Nonrecoverable
Event Summary: The CPUs across the system or SBL domain must all be the same type.
Event Description: The CPUs across the system/SBL domain must all be the same part number.
Probable Cause: mismatched hardware
Event Category: Processor
Event Sub-Category: part number
Cause 1: The part number of CPUs in the system/SBL domain are not the same.
Recommended Action 1: The CPUs in the system or SBL domain must be the same part number. Check the FRU data using the DF command at the CM> menu. The S/SPEC should match and the core stepping should have a delta no greater than 1 across all CPUs.

Event 8083

WBEM Severity: Critical
Event Summary: One or more of the blades in the domain could not communicate.
Event Description: One or more of the blades in the domain could not communicate. This affects power control.
Probable Cause: Peer to Peer communication failure
Event Category: blade to blade (internal to enclosure) network
Event Sub-Category: Unknown
Cause 1: Connection problem between blade and the enclosure
Recommended Action 1: iLO will attempt to correct communication issues. If this fails verify FW is at a supported revision and matched across the blades. Consider cycling stby power to the affected blades.

Event 8084

WBEM Severity: Degraded/Warning
Event Summary: The Mezzanine IO Cards must be the same in all blades.
Event Description: The Mezzanine IO Cards must be the same in all blades.
Probable Cause: loading of mezz should be consistent across blades
Event Category: iLO
Event Sub-Category: Domain
Cause 1: The Mezzanine IO Cards in all blades of the Domain are different
Recommended Action 1: The Mezzanine IO Cards must be the same in all blades of the Domain.

Event 8090

WBEM Severity: Degraded/Warning
Event Summary: This event was originated as a Framework Assert Status Code.
Event Description: Results from Framework code assert. Framework Code is some of the code HP integrates into the SFW ROM.
Probable Cause: System Firmware Defect
Event Category: System Firmware
Event Sub-Category: Unknown
Cause 1: System firmware has detected an internal error.
Recommended Action 1: Look at previous events and ASCII information in this event for more information. If problem persists, contact support.

Event 8103

WBEM Severity: Critical
Event Summary: SFW ROM versions across the partition are mismatched.
Event Description: A CPU Socket's SFW ROM has a different version and date stamp than the System Monarch's SFW ROM.
Probable Cause: Firmware mismatch
Event Category: System Firmware
Event Sub-Category: Unknown
Cause 1: One or more processor System Firmware ROM version is mismatched with the Monarch CPU.
Recommended Action 1: Update SFW. If the failure persists on the same CPU, replace the system board.

Event 8261

WBEM Severity: Critical
Event Summary: IOH persistent error condition detected.
Event Description: A persistent error could not be cleared in the IOH.
Probable Cause: I/O Device Error
Event Category: Failed to clear error
Event Sub-Category: PCIe Link
Cause 1: A persistent error condition could not be cleared on an IOH Root Port, may be caused by a faulty PCI express card.
Recommended Action 1: Replace the PCI express card, verify the latest supported System Firmware bundle is installed.

Event 8262

WBEM Severity: Critical
Event Summary: Generic FRU has header checksum error
Event Description: System Firmware finds that FRU data read from shared memory which MFW writes to is corrupt.
Probable Cause: Underlying Resource Unavailable
Event Category: System Firmware
Event Sub-Category: Data checksum error
Cause 1: 1. FRU not properly programmed 2. Manageability FW may not be working correctly
Recommended Action 1: Review the event log for related MFW events to determine if there is a FRU read problem. Try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system. If this still fails, it is likely the FRU requires replacement.

Event 8263

WBEM Severity: Degraded/Warning
Event Summary: MFW is posting a Data Object Table which is one revision below what SFW expects
Event Description: MFW posts a Data Object Table in Shared memory when it boots. SFW uses this table to get all the system data it needs. SFW is designed to not fail with a table which is 1 revision old, but not with older ones. However there is no reason for customers to ever run with old tables, so this should be fixed.
Probable Cause: Manageability FW is old revision
Event Category: System Firmware
Event Sub-Category: Shared Memory Compatibility
Cause 1: Manageability FW is not at the current supported revision for this SFW.
Recommended Action 1: Update Manageability FW.

Event 8264

WBEM Severity: Fatal/Nonrecoverable
Event Summary: System Firmware will not work correctly with the shared memory table loaded
Event Description: The Manageability FW Shared memory table has a date code which is not compatible with this SFW
Probable Cause: Incorrect Manageability Firmware Version
Event Category: System Firmware
Event Sub-Category: Shared memory compatibility
Cause 1: The System Firmware has detected that Manageability FW has loaded an incompatible shared memory table.
Recommended Action 1: Ensure the system FW versions are at a supported revision level. Reset MFW via text or Web Interface .

Event 8321

WBEM Severity: Degraded/Warning
Event Summary: CPU Late Test failed due to PAL Test Info call failed
Event Description: CPU Late Test failed due to PAL Test Info call failed. Data field contains physical location of the processor.
Probable Cause: Transmit Failure
Event Category: System Hardware
Event Sub-Category: Processor
Cause 1: A SFW or CPU error may have occurred.
Recommended Action 1: If the problem persists replace the processor.

Event 8322

WBEM Severity: Degraded/Warning
Event Summary: The TPM DOT information has a bad checksum.
Event Description: The TPM DOT information is corrupted. The checksum does not match with the data in the table.
Probable Cause: Transmit Failure
Event Category: System Firmware
Event Sub-Category: TPM
Cause 1: The System Firmware has detected a bad checksum in the TPM shared memory table.
Recommended Action 1: Review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem. Try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system.

Event 8323

WBEM Severity: Degraded/Warning
Event Summary: The TPM mode at next boot command could not be cleared in the TPM DOT table.
Event Description: The TPM mode at next boot command could not be cleared in the TPM DOT table.
Probable Cause: Unknown
Event Category: System Firmware
Event Sub-Category: Unknown
Cause 1: The system could not clear the command to change the TPM state at next boot in the NVM (Non-Volatile Memory) possibly due to an error on manageability firmware/hardware
Recommended Action 1: Review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem. Try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system.

Event 8324

WBEM Severity: Degraded/Warning
Event Summary: The TPM DOT checksum could not be recalculated.
Event Description: The TPM DOT checksum could not be recalculated.
Probable Cause: Unknown
Event Category: System Firmware
Event Sub-Category: Unknown
Cause 1: The System Firmware has detected a bad checksum in the TPM shared memory table and failed to fix the checksum in Non-Volatile Memory. Manageability may not be able to update NVM.
Recommended Action 1: Review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem. Try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system.

Event 8325

WBEM Severity: Degraded/Warning
Event Summary: The TPM DOT information could not be updated with the TPM presence indication
Event Description: The TPM DOT information could not be updated with the TPM presence indication
Probable Cause: Unknown
Event Category: System Firmware
Event Sub-Category: Unknown
Cause 1: The system could not initialize the value of the TPM presence flag in NVM (Non-Volatile Memory) possibly due to an error on manageability
Recommended Action 1: Review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem. Try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system.

Event 8326

WBEM Severity: Degraded/Warning
Event Summary: The TPM DOT could not be updated with the TPM absent flag.
Event Description: The TPM DOT information could not be updated to indicate the absence of the TPM
Probable Cause: Unknown
Event Category: System Firmware
Event Sub-Category: Unknown
Cause 1: The system could not initialize the value of the TPM presence flag to Absent in NVM (Non-Volatile Memory) possibly due to an error on Manageability
Recommended Action 1: Review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem. Try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system.

Event 8327

WBEM Severity: Degraded/Warning
Event Summary: The TPM DOT information could not be initialized successfully.
Event Description: The TPM DOT information could not be initialized successfully.
Probable Cause: Unknown
Event Category: System Firmware
Event Sub-Category: Unknown
Cause 1: The System Firmware has detected an uninitialized shared memory table for the TPM and failed to initialize it. This can be caused by an error with Manageability firmware/hardware.
Recommended Action 1: Review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem. Try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system.

Event 8328

WBEM Severity: Degraded/Warning
Event Summary: The TPM DOT information does not appear to be initialized or is corrupted.
Event Description: The TPM DOT information does not appear to be initialized or is corrupted.
Probable Cause: Unknown
Event Category: System Firmware
Event Sub-Category: Unknown
Cause 1: The System Firmware detected that Manageability FW has loaded an invalid shared memory table for the TPM
Recommended Action 1: Review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem. Try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system.

Event 8329

WBEM Severity: Degraded/Warning
Event Summary: The TPM DOT information is not initialized.
Event Description: The TPM DOT information is not initialized.
Probable Cause: Unknown
Event Category: System Firmware
Event Sub-Category: Unknown
Cause 1: The System Firmware has detected an uninitialized shared memory table for the TPM. This can be caused by manageability firmware/hardware.
Recommended Action 1: The system will try to initialize the memory table. If the error persists, review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem. Try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system. Replace the battery.

Event 8330

WBEM Severity: Degraded/Warning
Event Summary: The TPM related information could not be written to the Non-Volatile Memory.
Event Description: The TPM related information could not be written to the Non-Volatile Memory.
Probable Cause: Unknown
Event Category: System Firmware
Event Sub-Category: Unknown
Cause 1: The system could not save the TPM configuration to NVM (Non-Volatile Memory) This can be caused by manageability firmware/hardware.
Recommended Action 1: Review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem. Try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system.

Event 8331

WBEM Severity: Degraded/Warning
Event Summary: The TPM DOT table could not initialize the TPM mode at next boot element
Event Description: The TPM DOT table could not be initialized with the TPM mode at next boot element. An error has occurred.
Probable Cause: Unknown
Event Category: System Firmware
Event Sub-Category: Unknown
Cause 1: The system could not initialized the value of TPM state at next boot in NVM (Non-Volatile Memory). This can be caused by manageability firmware/hardware.
Recommended Action 1: Review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem. Try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system.

Event 8332

WBEM Severity: Degraded/Warning
Event Summary: The command to change the TPM state has failed.
Event Description: The command to change the TPM state has failed.
Probable Cause: Unknown
Event Category: System Firmware Security
Event Sub-Category: Unknown
Cause 1: The request to change the TPM state has failed. An error occurred with the TPM
Recommended Action 1: Review the event log for TPM related messages. Reboot the system. Replace the TPM board.

Event 8333

WBEM Severity: Degraded/Warning
Event Summary: The system reset failed when the TPM code attempted to change its status
Event Description: The system reset request failed when the TPM code attempted to change its status (enable, disable, reset)
Probable Cause: Unknown
Event Category: System Firmware
Event Sub-Category: Unknown
Cause 1: The reset command failed to reset the system.
Recommended Action 1: Reboot the system. Verify that the system is at the latest firmware revision.

Event 8449

WBEM Severity: Major
Event Summary: One or more processor threads failed to start boot
Event Description: One or more processor threads failed to start boot. See the following EVN_CPU_PHYSICAL_LOCATION for the CPU Physical Location.
Probable Cause: Processor Problem (Internal Machine Error)
Event Category: Processor
Event Sub-Category:
Cause 1: A CPU error occurred.
Recommended Action 1: Replace the failed CPU, as indicated by the physical location. If the failure persists, contact support.

Event 8480

WBEM Severity: Degraded/Warning
Event Summary: Detected a IOH QPI link's operation is degraded.
Event Description: A QPI link on the IOH is degraded. An additional QPI_CPU_LINK_DEGRADED event will be logged to indicate the physical location information for the CPU on the other side of the degraded QPI link.
Probable Cause: QPI link error
Event Category: System Interconnect
Event Sub-Category: QPI link
Cause 1: QPI link hardware has been detected operating with degraded performance.
Recommended Action 1: Reboot. If problem persists contact support.

Event 8495

WBEM Severity: Fatal/Nonrecoverable
Event Summary: The system has been issued an INIT. All activity will be halted.
Event Description: The system has been issued an INIT, (similar to PA-RISC TOC). This means all system processing and I/O activity will be irrecoverably halted and the computer system will be restarted.
Probable Cause: User requested INIT
Event Category: iLO
Event Sub-Category: INIT
Cause 1: A user has issued an INIT interrupt to the system.
Recommended Action 1: None. The system will restart on its own.

Event 8502

WBEM Severity: Degraded/Warning
Event Summary: The EM has determined that power must be shed and has asserted Power Alert.
Event Description: The EM has determined that power must be shed and has asserted the Power Alert signal. Throttling is likely to occur in order for the blade to shed power.
Probable Cause: Power Problem
Event Category: Other Power
Event Sub-Category: Enclosure PSU
Cause 1: Typically caused by a power supply failure reducing the power pool available to the EM to distribute to the blades.
Recommended Action 1: Identify any failed power supplies and replace them.

Event 8503

WBEM Severity: Degraded/Warning
Event Summary: iLO entering special mode.
Event Description: iLO entering a special mode.
Probable Cause: special running mode
Event Category: iLO
Event Sub-Category: running mode
Cause 1: iLO entering special mode. The system is not operating in a normal mode. Some protection features may be disabled in this mode.
Recommended Action 1: The special mode must be exited to ensure proper operation of the server.

Event 8509

WBEM Severity: Degraded/Warning
Event Summary: A firmware update has failed.
Event Description: A firmware update has failed.
Probable Cause: a requested firmware update failed
Event Category: iLO
Event Sub-Category: firmware update
Cause 1: An attempted firmware update has failed with an error.
Recommended Action 1: Check to make sure that the bits are accessible and system power is off (if required). Try the update again.

Event 8510

WBEM Severity: Critical
Event Summary: A failure has occurred while attempting to update the iLO ROM.
Event Description: A failure has occurred while attempting to update the iLO ROM. The ROM may be in a corrupt state. The error code included in data field is for developer use only.
Probable Cause: FLASH device or interface (SPI bus) failure
Event Category: Other Storage Device
Event Sub-Category: error in read/write of FLASH over SPI bus
Cause 1: Something has interfered with firmware update while it attempted to update the bits in the iLO ROM.
Recommended Action 1: DO NOT REMOVE POWER FROM THE SYSTEM. DO NOT RESET iLO. Attempt the update again or attempt update to original version. Refer to recipe notes to verify no procedural issues.

Event 8511

WBEM Severity: Critical
Event Summary: A failure has occurred while attempting to update the SFW ROM.
Event Description: A failure has occurred while attempting to update the System Firmware (SFW) ROM. The ROM may be in a corrupt state. The error code included in data field is for developer use only.
Probable Cause: FLASH device or interface (SPI bus) failure
Event Category: Other Storage Device
Event Sub-Category: error in read/write of FLASH over SPI bus
Cause 1: Something has interfered with firmware update while it attempted to update the bits in the SFW ROM. The Aux ROM and either of the direct attach SFW ROMs or any combination there of may be affected.
Recommended Action 1: Attempt the update again. If this fails you may want to reset iLO or remove stby power from the system and try the update again.

Event 8512

WBEM Severity: Critical
Event Summary: A failure has occurred while attempting to update the FPGA ROM.
Event Description: A failure has occurred while attempting to update the FPGA ROM. The ROM may be in a corrupt state. The error code included in data field is for developer use only.
Probable Cause: ROM device or interface failure
Event Category: Other Storage Device
Event Sub-Category: error in read/write of ROM over interface
Cause 1: Something has interfered with firmware update while it attempted to update the bits in the FPGA ROM.
Recommended Action 1: Do not remove power from the system. Do not reset iLO. Attempt the update again.

Event 8513

WBEM Severity: Critical
Event Summary: A failure has occurred while attempting to update the Power Monitor PIC.
Event Description: A failure has occurred while attempting to update the Power Monitor PIC. The PIC may be in a corrupt state. The error code included in data field is for developer use only.
Probable Cause: PIC device or interface (i2c) failure
Event Category: Other Storage Device
Event Sub-Category: Error during read/write to PIC (ROM space)
Cause 1: Something has interfered with firmware update while it attempted to update the bits in the Power Monitor PIC.
Recommended Action 1: Attempt the update again. If this fails try resetting iLO and attempt the update again.

Event 8514

WBEM Severity: Degraded/Warning
Event Summary: Failed to save non-volatile EFI variables into NVM
Event Description: System firmware was unable to save the active non-volatile EFI variables to persistent storage. The event data field represents an internal return code.
Probable Cause: MFW Performance Problem
Event Category: Support Firmware
Event Sub-Category: Unknown
Cause 1: An error occurred in the interface between system firmware and manageability firmware.
Recommended Action 1: Reboot the server and verify that the system board (Monarch Blade system board if a multi-blade server) is functioning properly. If not, replace the system board. Check system logs to see if other NVM errors are related to this same system board. If so, replace the system board. Verify system and manageability firmware are at their supported revisions, and if not, update firmware to the latest supported revisions. If problems persist, contact Support.

Event 8515

WBEM Severity: Critical
Event Summary: The system has been placed in security override mode.
Event Description: Security override is set. Security enforcement is disabled. This mode will timeout in 15 minutes or less. To Manually exit this mode go to the Access Settings web page.
Probable Cause: User initiated security override.
Event Category: iLO
Event Sub-Category: security
Cause 1: A user has asserted the physical presence button for a duration greater than 8 seconds and less than 12 seconds.
Recommended Action 1: This mode will timeout in 15 minutes or less. To manually exit this mode go to the Access Settings web page. You can also press the physical presence button for less than 4 seconds to reset iLO and clear this mode.

Event 8516

WBEM Severity: Critical
Event Summary: The system is entering TPM physical presence mode.
Event Description: The system is entering TPM physical presence mode.
Probable Cause: User initiated via physical presence button
Event Category: iLO
Event Sub-Category: TPM
Cause 1: A user has asserted the TPM physical presence button for a duration of greater than 4 seconds and less than 8 seconds.
Recommended Action 1: No action is required. This event indicates that the system was placed in a mode where restricted commands can now be executed by the TPM. Asserting the physical presence button for less than 4 seconds will reset iLO and clear the TPM physical presence mode.

Event 8517

WBEM Severity: Critical
Event Summary: The TPM did not accept the start-up request
Event Description: The TPM did not accept the start-up request.
Probable Cause: TPM is defective or tampering has occurred
Event Category: System HW Security
Event Sub-Category: Unknown
Cause 1: The TPM can be defective or has detected a tampering attempt.
Recommended Action 1: Verify for possible tampering. Replace the board hosting the TPM chip.

Event 8519

WBEM Severity: Fatal/Nonrecoverable
Event Summary: The thread has received an interruption during boot.
Event Description: Thread has received an unexpected interruption during SFW boot and at EFI environment.
Probable Cause: Unknown
Event Category: System Firmware
Event Sub-Category: Unknown
Cause 1: Firmware or EFI applications or Hardware Errors.
Recommended Action 1: Review the interruption log on the console. Reboot the system. If problem persists, contact support.

Event 8523

WBEM Severity: Fatal/Nonrecoverable
Event Summary: ACPI parser error due to a missing AML identifier
Event Description: The ACPI subsystem encountered a missing AML identifier while parsing the DSDT table. This will likely prevent the Operating System from booting successfully.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: ACPI Subsystem
Cause 1: The ACPI subsystem could not find the CPU AML identifier while parsing the DSDT table.
Recommended Action 1: Ensure SFW component is at supported level.

Event 8524

WBEM Severity: Fatal/Nonrecoverable
Event Summary: Failed to acquire platform specific data in ACPI
Event Description: Could not acquire platform data needed by the ACPI subsystem.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: ACPI subsystem
Cause 1: ACPI received an invalid pointer to platform data. Possible causes for this are a corrupted System Firmware image or an error in the memory subsystem.
Recommended Action 1: Ensure SFW component is at supported level. Check for errors in the memory subsystem if the problem persists.

Event 8525

WBEM Severity: Fatal/Nonrecoverable
Event Summary: ACPI parser error due to a missing AML identifier
Event Description: The ACPI subsystem encountered a missing AML identifier while parsing the DSDT table. This will likely prevent the Operating System from booting successfully.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: ACPI Subsystem
Cause 1: The ACPI subsystem could not find the HPET AML identifier while parsing the DSDT table.
Recommended Action 1: Ensure SFW component is at supported level.

Event 8526

WBEM Severity: Fatal/Nonrecoverable
Event Summary: ACPI parser error due to a missing AML identifier
Event Description: The ACPI subsystem encountered a missing AML identifier while parsing the DSDT table. This will likely prevent the Operating System from booting successfully.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: ACPI Subsystem
Cause 1: The ACPI subsystem could not find the ICH AML identifier while parsing the DSDT table.
Recommended Action 1: Ensure SFW component is at supported level.

Event 8527

WBEM Severity: Fatal/Nonrecoverable
Event Summary: Failed to acquire platform specific data in ACPI
Event Description: System failed to acquire I/O data in the ACPI subsystem.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: Unknown
Cause 1: Corrupted SFW image.
Recommended Action 1: Ensure SFW component is at supported level.

Event 8528

WBEM Severity: Fatal/Nonrecoverable
Event Summary: ACPI parser error due to a missing AML identifier
Event Description: The ACPI subsystem encountered a missing AML identifier while parsing the DSDT table. This will likely prevent the Operating System from booting successfully.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: ACPI Subsystem
Cause 1: The ACPI subsystem could not find the IPMI AML identifier while parsing the DSDT table.
Recommended Action 1: Ensure SFW component is at supported level.

Event 8529

WBEM Severity: Fatal/Nonrecoverable
Event Summary: The ACPI subsystem failed to load the DSDT table from flash device.
Event Description: The ACPI subsystem failed to load the DSDT table from flash device.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: ACPI Subsystem
Cause 1: The ACPI subsystem failed to load the DSDT table from flash device.
Recommended Action 1: Ensure SFW component is at supported level.

Event 8530

WBEM Severity: Fatal/Nonrecoverable
Event Summary: System firmware protocol failed while executing ACPI subsystem code
Event Description: System firmware protocol failed while executing ACPI subsystem code. This affects system resources communicated to the Operating System.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: ACPI
Cause 1: The failure is possibly related to using a corrupted System Firmware binary.
Recommended Action 1: Ensure SFW component is at supported level.

Event 8531

WBEM Severity: Major
Event Summary: The ACPI subsystem failed to load the SSDT table from the flash device.
Event Description: The ACPI subsystem failed to load the SSDT table from the flash device. This can cause the Operating System to lose some system resources.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: ACPI Subsystem
Cause 1: The ACPI could not load the SSDT table from the flash device.
Recommended Action 1: Ensure SFW component is at supported level.

Event 8532

WBEM Severity: Fatal/Nonrecoverable
Event Summary: ACPI parser error due to a missing AML identifier
Event Description: The ACPI subsystem encountered a missing AML identifier while parsing the DSDT table. This will likely prevent the Operating System from booting successfully.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: ACPI Subsystem
Cause 1: The ACPI subsystem could not find the memory AML identifier while parsing the DSDT table.
Recommended Action 1: Ensure SFW component is at supported level.

Event 8533

WBEM Severity: Fatal/Nonrecoverable
Event Summary: Failed to acquire platform specific data in ACPI
Event Description: System failed to acquire memory data in the ACPI subsystem.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: memory range
Cause 1: Corrupted SFW image.
Recommended Action 1: Ensure SFW component is at supported level.

Event 8535

WBEM Severity: Fatal/Nonrecoverable
Event Summary: Failed to acquire platform specific data in ACPI
Event Description: System failed to acquire partition information in the ACPI subsystem.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: Unknown
Cause 1: Invalid SFW image.
Recommended Action 1: Ensure SFW component is at supported level.

Event 8536

WBEM Severity: Fatal/Nonrecoverable
Event Summary: ACPI parser error due to a missing platform AML identifier
Event Description: The ACPI subsystem encountered a missing AML identifier while parsing the DSDT table. This will likely prevent the Operating System from booting successfully.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: ACPI subsystem
Cause 1: The ACPI subsystem could not find the Platform AML identifier while parsing the DSDT table.
Recommended Action 1: Ensure SFW component is at supported level.

Event 8537

WBEM Severity: Fatal/Nonrecoverable
Event Summary: ACPI parser error due to a missing AML identifier
Event Description: The ACPI subsystem encountered a missing AML identifier while parsing the DSDT table. This will likely prevent the Operating System from booting successfully.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: ACPI Subsystem
Cause 1: The ACPI subsystem could not find the Power Management AML identifier while parsing the DSDT table.
Recommended Action 1: Ensure SFW component is at supported level.

Event 8538

WBEM Severity: Fatal/Nonrecoverable
Event Summary: ACPI parser error due to a missing AML identifier
Event Description: The ACPI subsystem encountered a missing AML identifier while parsing the DSDT table. This will likely prevent the Operating System from booting successfully.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: ACPI Subsystem
Cause 1: The ACPI subsystem could not find the root-complex AML identifier while parsing the DSDT table.
Recommended Action 1: Ensure SFW component is at supported level.

Event 8539

WBEM Severity: Fatal/Nonrecoverable
Event Summary: ACPI parser error due to a missing AML identifier
Event Description: The ACPI subsystem encountered a missing AML identifier while parsing the DSDT table. This will likely prevent the Operating System from booting successfully.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: ACPI Subsystem
Cause 1: The ACPI subsystem could not find the root-port AML identifier while parsing the DSDT table.
Recommended Action 1: Ensure SFW component is at supported level.

Event 8540

WBEM Severity: Fatal/Nonrecoverable
Event Summary: ACPI parser error due to a missing AML identifier
Event Description: The ACPI subsystem encountered a missing AML identifier while parsing the DSDT table. This will likely prevent the Operating System from booting successfully.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: ACPI Subsystem
Cause 1: The ACPI subsystem could not find the Serial Port AML identifier while parsing the DSDT table.
Recommended Action 1: Ensure SFW component is at supported level.

Event 8541

WBEM Severity: Fatal/Nonrecoverable
Event Summary: ACPI parser error due to a missing AML identifier
Event Description: The ACPI subsystem encountered a missing AML identifier while parsing the DSDT table. This will likely prevent the Operating System from booting successfully.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: ACPI Subsystem
Cause 1: The ACPI subsystem could not find the Server AML identifier while parsing the DSDT table.
Recommended Action 1: Ensure SFW component is at supported level.

Event 8542

WBEM Severity: Fatal/Nonrecoverable
Event Summary: ACPI failed to set its tables
Event Description: The ACPI tables could not be set. This prevents the Operating System from consuming ACPI resources properly.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: ACPI Subsystem
Cause 1: The ACPI driver in firmware failed to set the tables.
Recommended Action 1: Ensure SFW component is at supported level.

Event 8543

WBEM Severity: Fatal/Nonrecoverable
Event Summary: ACPI parser error due to a missing AML identifier
Event Description: The ACPI subsystem encountered a missing AML identifier while parsing the DSDT table. This will likely prevent the Operating System from booting successfully.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: ACPI Subsystem
Cause 1: The ACPI subsystem could not find the slot AML identifier while parsing the DSDT table.
Recommended Action 1: Ensure SFW component is at supported level.

Event 8544

WBEM Severity: Fatal/Nonrecoverable
Event Summary: ACPI parser error due to a missing AML identifier
Event Description: The ACPI subsystem encountered a missing AML identifier while parsing the DSDT table. This will likely prevent the Operating System from booting successfully.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: ACPI Subsystem
Cause 1: The ACPI subsystem could not find the Platform AML identifier while parsing the DSDT table.
Recommended Action 1: Ensure SFW component is at supported level.

Event 8546

WBEM Severity: Fatal/Nonrecoverable
Event Summary: Failed to acquire platform specific data in ACPI
Event Description: System failed to acquire Trusted Platform Module data in the ACPI subsystem.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: Unknown
Cause 1: Invalid SFW image.
Recommended Action 1: Ensure SFW component is at supported level.

Event 9071

WBEM Severity: Degraded/Warning
Event Summary: Fans are entering blowout mode.
Event Description: Fans are entering blowout mode. See data field for more information.
Probable Cause: Sensor Failure
Event Category: Other Cooling
Event Sub-Category: temp, fan, lid sensors
Cause 1: A sensor may have been unreadable meaning that it could not be read on the i2c bus. See the data field for the sensor that caused the error forcing fans into blowout mode.
Recommended Action 1: Investigate the sensor implicated in the data field to determine the cause of failure. If a temperature sensor can't be read try AC cycling the complex; if a fan sensor can't be read try reseating the fan and AC cycling the complex; If none of this helps try replacing the FRU associated with sensor.

Event 9799

WBEM Severity: Major
Event Summary: Virtual Connect failed to write data into a FRU storage device
Event Description: After changing FRU data in memory, system firmware attempted to replicate the changes to the physical FRU, but received an unexpected error. The event data field encodes internal information, including the following: Second byte: Blade number within server, 0-n. Fourth byte: FRU ID.
Probable Cause: MFW Performance Problem
Event Category: Support Firmware
Event Sub-Category: Unknown
Cause 1: An error occurred in the interface between system firmware and manageability firmware.
Recommended Action 1: Reboot the server and verify that the system board or mezz card containing this FRU is functioning properly. If not, replace the failing hardware. Check system logs to see if other errors are related to this same FRU. If so, replace the system board or mezz card containing this FRU. Verify system and manageability firmware are at their supported revisions, and if not, update firmware to the latest supported revisions. If problems persist, contact Support.

Event 9801

WBEM Severity: Major
Event Summary: Virtual Connect failed to save a backup of non-volatile EFI variables into NVM
Event Description: System firmware was unable to save a backup of the active non-volatile EFI variables to persistent storage. If the server is removed from Virtual Connect service later, it will not be possible to restore the original variables. The event data field represents an internal return code.
Probable Cause: MFW Performance Problem
Event Category: Support Firmware
Event Sub-Category: Unknown
Cause 1: An error occurred in the interface between system firmware and manageability firmware.
Recommended Action 1: Reboot the server and verify that the system board (Monarch Blade system board if a multi-blade server) is functioning properly. If not, replace the system board. Check system logs to see if other NVM errors are related to this same system board. If so, replace the system board. Verify system and manageability firmware are at their supported revisions, and if not, update firmware to the latest supported revisions. If problems persist, contact Support.

Event 9802

WBEM Severity: Major
Event Summary: Virtual Connect failed to save non-volatile EFI variables into NVM
Event Description: System firmware was unable to save the active non-volatile EFI variables to persistent storage. The event data field represents an internal return code.
Probable Cause: MFW Performance Problem
Event Category: Support Firmware
Event Sub-Category: Unknown
Cause 1: An error occurred in the interface between system firmware and manageability firmware.
Recommended Action 1: Reboot the server and verify that the system board (Monarch Blade system board if a multi-blade server) is functioning properly. If not, replace the system board. Check system logs to see if other NVM errors are related to this same system board. If so, replace the system board. Verify system and manageability firmware are at their supported revisions, and if not, update firmware to the latest supported revisions. If problems persist, contact Support.

Event 9803

WBEM Severity: Major
Event Summary: Virtual Connect failed to erase the EFI variables backup from NVM
Event Description: System firmware was unable to erase a backup of the EFI variables present in persistent storage. The same backup will again be restored at the next reboot, overwriting any new variables produced during the current boot cycle. The event data field represents an internal return code.
Probable Cause: MFW Performance Problem
Event Category: Support Firmware
Event Sub-Category: Unknown
Cause 1: An error occurred in the interface between system firmware and manageability firmware.
Recommended Action 1: Reboot the server and verify that the system board (Monarch Blade system board if a multi-blade server) is functioning properly. If not, replace the system board. Check system logs to see if other NVM errors are related to this same system board. If so, replace the system board. Verify system and manageability firmware are at their supported revisions, and if not, update firmware to the latest supported revisions. If problems persist, contact Support.

Event 9838

WBEM Severity: Major
Event Summary: Virtual Connect failed to save FRU data into NVM
Event Description: After changing FRU data in memory, system firmware attempted to replicate the changes to NVM, but received an unexpected error. The event data field encodes internal information, including the following: Second byte: Blade number within server, 0-n. Fourth byte: FRU ID.
Probable Cause: MFW Performance Problem
Event Category: Support Firmware
Event Sub-Category: Unknown
Cause 1: An error occurred in the interface between system firmware and manageability firmware.
Recommended Action 1: Reboot the server and verify that the system board or mezz card containing this FRU is functioning properly. If not, replace the system board containing this FRU. Check system logs to see if other NVM errors are related to this same system board. If so, replace the system board containing this FRU. Verify system and manageability firmware are at their supported revisions, and if not, update firmware to the latest supported revisions. If problems persist, contact Support.

Event 9862

WBEM Severity: Critical
Event Summary: The iLO peer to peer LAN communication between MMP and AMP was lost.
Event Description: The iLO peer to peer LAN communication between a Monarch MP (MMP) and an Auxiliary MP (AMP) has been lost.
Probable Cause: iLO Peer to Peer LAN communication
Event Category: iLO
Event Sub-Category: Conjoined
Cause 1: The iLO peer to peer LAN communication between a Monarch MP (MMP) and an Auxiliary MP (AMP) has been lost.
Recommended Action 1: The management system will attempt to repair itself. If the management system does not recover refer to the Service Guide to determine how to reset iLO without a user interface.

Event 9863

WBEM Severity: Critical
Event Summary: The iLO peer to peer LAN communication between MMP and AMP was not established.
Event Description: The iLO peer to peer LAN communication between Monarch MP (MMP) and an Auxiliary MP (AMP) could not be established.
Probable Cause: iLO Peer to Peer LAN communication
Event Category: Enclosure internal network
Event Sub-Category: Unknown
Cause 1: The iLO peer to peer LAN communication between Monarch MP (MMP) and an Auxiliary MP (AMP) could not be established.
Recommended Action 1: The management system will attempt to repair itself. If the management system does not recover refer to the Service Guide to determine how to reset iLO without a user interface.

Event 9864

WBEM Severity: Critical
Event Summary: The iLO peer to peer LAN communication between DMP and AMP was lost.
Event Description: The iLO peer to peer LAN communication between a Domain MP (DMP) and an Auxiliary MP (AMP) has been lost.
Probable Cause: iLO Peer to Peer LAN communication
Event Category: iLO
Event Sub-Category: Conjoined
Cause 1: The iLO peer to peer LAN communication between a Domain MP (DMP) and an Auxiliary MP (AMP) has been lost.
Recommended Action 1: The management system will attempt to repair itself. If the management system does not recover refer to the Service Guide to determine how to reset iLO without a user interface.

Event 9865

WBEM Severity: Critical
Event Summary: The iLO peer to peer LAN communication between DMP and AMP was not established.
Event Description: The iLO peer to peer LAN communication between Domain MP (DMP) and an Auxiliary MP (AMP) could not be established.
Probable Cause: iLO Peer to Peer LAN communication
Event Category: iLO
Event Sub-Category: conjoined
Cause 1: The iLO peer to peer LAN communication between Domain MP (DMP) and an Auxiliary MP (AMP) could not be established.
Recommended Action 1: The management system will attempt to repair itself. If the management system does not recover refer to the Service Guide to determine how to reset iLO without a user interface.

Event 9866

WBEM Severity: Fatal/Nonrecoverable
Event Summary: Insufficient power; more power supplies may be needed.
Event Description: Insufficient power; more power supplies may be needed.
Probable Cause: Power Problem
Event Category: System Power
Event Sub-Category: Unknown
Cause 1: Power request to OA denied with the reason insufficient power. Either not enough BPS, or too much power draw from other blades installed in enclosure. Consult OA to determine if there is enough room to add BPS.
Recommended Action 1: Install more power supply units, or reduce the current draw on the power system. Power Cap is one method that could be used to reduce current draw. You may want to verify that none of your BPS have failed.

Event 9867

WBEM Severity: Critical
Event Summary: A Socket Monarch Thread has stopped making forward progress.
Event Description: The socket monarch thread has stopped making forward progress. It may be in an infinite loop or the thread itself (hardware) has failed.
Probable Cause: Timeout
Event Category: Processor
Event Sub-Category: Processor HW Failure or Firmware Fault
Cause 1: Unexpected Firmware or Hardware Errors.
Recommended Action 1: AC power cycle the system. If the problem still occurs, contact support.

Event 9868

WBEM Severity: Critical
Event Summary: The Partition Monarch Thread has stopped making forward progress.
Event Description: The socket monarch thread has stopped making forward progress. It may be in an infinite loop or the thread itself (hardware) has failed.
Probable Cause: Timeout
Event Category: Processor
Event Sub-Category: Processor HW failure or Firmware Fault.
Cause 1: Unexpected Firmware or Hardware Errors.
Recommended Action 1: AC power cycle the system. If the problem still occurs, contact Support.

Event 9869

WBEM Severity: Critical
Event Summary: The processor module that contains the Monarch Thread was deconfigured.
Event Description: The processor module that contains the Monarch Thread that is not making forward progress has been deconfigured.
Probable Cause: Timeout
Event Category: Processor
Event Sub-Category: Processor Hardware Failure or Firmware Fault.
Cause 1: Unexpected Firmware or Hardware Error has been encountered.
Recommended Action 1: AC power cycle the system. If the problem still occurs, contact Support for help.

Event 9870

WBEM Severity: Critical
Event Summary: The ACPI subsystem encountered an unknown platform type.
Event Description: The ACPI subsystem failed to recognize the platform type of the server.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: NVM
Cause 1: ACPI failed to recognize the platform type of the server. This is likely due to corrupted NVM data.
Recommended Action 1: Verify that the System Firmware is at its supported revision, and if not, update firmware to the latest supported version. If problem persists contact support.

Event 9871

WBEM Severity: Major
Event Summary: Invalid partition size encountered by the ACPI subsystem.
Event Description: An incorrect partition size was communicated to the ACPI module.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: ACPI
Cause 1: Possible data corruption in non-volatile memory subsystem.
Recommended Action 1: Reset the system. Verify that the System Firmware is at its supported revision, and if not, update firmware to the latest supported version. If problem persists contact support.

Event 9874

WBEM Severity: Fatal/Nonrecoverable
Event Summary: System firmware failed to publish ACPI tables
Event Description: System firmware failed to publish ACPI resources to the Operating System
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: ACPI Module
Cause 1: The ACPI subsystem could not publish ACPI tables due to a System Firmware error.
Recommended Action 1: Verify that the System Firmware is at its supported revision, and if not, update firmware to the latest supported version. If problem persists contact support.

Event 9875

WBEM Severity: Major
Event Summary: software memory test failed
Event Description: Memory test failed. Data field contains the physical address that failed.
Probable Cause: Memory test failure
Event Category: Memory
Event Sub-Category: DIMM
Cause 1: Unexpected data accessed from the memory address during firmware memory test.
Recommended Action 1: The first action will be check the system event logs for de-allocated DIMM(s). Next reseat the DIMM(s). If the problem persists, then replace the DIMM(s) with supported DIMM(s) - See Service Guide. If that does not solve the issue, replace CPU. If problem still continues to exist, replace the system board.

Event 9876

WBEM Severity: Major
Event Summary: Scalable memory buffer (SMB) link initialization failed
Event Description: SMB (Scalable Memory Buffer) link initialization failed. Data field is the physical location of the failed SMB.
Probable Cause: CPU memory controller
Event Category: Memory
Event Sub-Category: memory controller
Cause 1: SMB (Scalable Memory Buffer) link initialization failed.
Recommended Action 1: The first action will be to replace the CPU. If that does not solve the issue, reseat and/or replace with supported DIMM(s) associated with the SMB - See Service Guide. If problem still continues to exist, replace the system board.

Event 9877

WBEM Severity: Major
Event Summary: Scalable memory buffer (SMB) channel training failed
Event Description: Scalable memory buffer (SMB) channel training failed. Data field contains the physical location of the failed SMB.
Probable Cause: CPU memory controller
Event Category: Memory
Event Sub-Category: memory controller
Cause 1: Scalable memory buffer (SMB) channel training failed.
Recommended Action 1: The first action will be to reset the CPU. If that does not solve the issue, replace CPU. If problem still continues to exist, replace the system board.

Event 9878

WBEM Severity: Major
Event Summary: Failed outbound read access to scalable memory buffer (SMB) due to timeout
Event Description: Failed outbound read access to scalable memory buffer (SMB) due to timeout. Data field is the physical location of the SMB that CPU attempted access to.
Probable Cause: CPU memory controller
Event Category: Memory
Event Sub-Category: memory controller
Cause 1: Failed outland read access to scalable memory buffer (SMB) due to timeout.
Recommended Action 1: The first action will be to replace the CPU. If problem still continues to exist, replace the system board.

Event 9879

WBEM Severity: Major
Event Summary: Failed outbound write access to scalable memory buffer (SMB) due to timeout.
Event Description: Failed outbound write access to scalable memory buffer (SMB). Data field is the physical location of the SMB that CPU attempted access to.
Probable Cause: CPU memory controller
Event Category: Memory
Event Sub-Category: memory controller
Cause 1: Failed outbound write access to memory controller due to timeout
Recommended Action 1: The first action will be to replace the CPU. If problem still continues to exist, replace the system board.

Event 9880

WBEM Severity: Major
Event Summary: Memory build-in self test (MBIST) failed
Event Description: Memory Build-in self test failed. Data field is the physical location of the Scalable memory buffer (SMB) that failed.
Probable Cause: System Hardware
Event Category: Memory
Event Sub-Category: DIMM
Cause 1: Memory Build-in self test failed
Recommended Action 1: The first action will be to check the SEL for the de-allocated DIMM(s). Next, reseat the failing DIMM(s). If that does not solve the issue, replace the DIMM(s) with supported DIMM(s) - See Service Guide. If problem still continues to exist, replace the system board.

Event 9881

WBEM Severity: Major
Event Summary: Memory build-in self test failed with timeout
Event Description: Memory built-in self test failed with timeout. Data field is the physical location of the Scalable memory buffer (SMB) that failed.
Probable Cause: Hardware
Event Category: Memory
Event Sub-Category: DIMM
Cause 1: Memory built-in self test failed with timeout
Recommended Action 1: The first action will be to check the SEL for the de-allocated DIMM(s). Next, reseat the failing DIMM(s). If that does not solve the issue, replace the DIMM(s) with supported DIMM(s) - See Service Guide. If problem still continues to exist, replace the system board.

Event 9882

WBEM Severity: Major
Event Summary: DIMM rank mismatch or rank not found during memory initialization
Event Description: DIMM rank mismatch or invalid data. Data field is the physical location of the failing DIMM.
Probable Cause: Hardware
Event Category: Memory
Event Sub-Category: DIMM
Cause 1: The DIMM rank data is invalid or does not match with the other DIMM pair.
Recommended Action 1: The first action will be to reseat the DIMM. If problem persists, replace DIMM with supported DIMM type (see Service Guide). If problem still continues to exist, contact support.

Event 9883

WBEM Severity: Major
Event Summary: Unable to acquire communications link to scalable memory buffer (SMB)
Event Description: Failed to acquire communication link to scalable memory buffer (SMB). Data field value is the physical location of the SMB.
Probable Cause: Hardware
Event Category: System Hardware
Event Sub-Category: CPU
Cause 1: Failed to acquire communication link to scalable memory buffer (SMB).
Recommended Action 1: The first action will be to replace the CPU. If problem still continues to exist, replace the system board.

Event 9884

WBEM Severity: Degraded/Warning
Event Summary: Invalid count reported for number of supported CPU p-states
Event Description: An invalid count has been reported for the number of supported CPU p-states.
Probable Cause: Processor Problem (Internal Machine Error)
Event Category: Processor
Event Sub-Category: PAL/Power-Management
Cause 1: The processor is reporting invalid data about its power management information.
Recommended Action 1: Verify that the System Firmware is at its supported revision, and if not, update firmware to the latest supported version. Replace the processor module. If problem persists contact support.

Event 9890

WBEM Severity: Degraded/Warning
Event Summary: Inbound access to memory controller timed out
Event Description: Failed inbound access to scalable memory buffer (SMB) due to timeout. Data field is the physical location of the SMB that CPU attempted access to.
Probable Cause: Hardware
Event Category: Memory
Event Sub-Category: memory controller
Cause 1: Failed inbound access to scalable memory buffer (SMB) due to timeout.
Recommended Action 1: The first action will be to replace the CPU. If problem still continues to exist, replace the system board.

Event 9891

WBEM Severity: Degraded/Warning
Event Summary: Frequency ratio for DIMM is incompatible
Event Description: Memory frequency ratio is not supported by system platform. Data field is the physical location of DIMM that failed.
Probable Cause: Hardware
Event Category: Memory
Event Sub-Category: DIMM
Cause 1: Memory frequency ratio is not supported by system platform.
Recommended Action 1: The first action will be to reseat the DIMM. If problem persists, replace DIMM with supported DIMM type (see Service Guide). If problem still continues to exist, contact support.

Event 9892

WBEM Severity: Degraded/Warning
Event Summary: Reached unexpected code paths in memory initialization code
Event Description: Reached unexpected code paths in memory initialization code.
Probable Cause: Hardware
Event Category: System Hardware
Event Sub-Category: SFW flash
Cause 1: Reached unexpected code paths in memory initialization code.
Recommended Action 1: Ensure SFW component is at supported level. If problem persists, contact support.

Event 9893

WBEM Severity: Degraded/Warning
Event Summary: LAI expander detected
Event Description: Unsupported memory LAI expander detected
Probable Cause: Hardware
Event Category: System Hardware
Event Sub-Category: System Board
Cause 1: Unsupported memory LAI expander detected
Recommended Action 1: Contact support.

Event 9894

WBEM Severity: Degraded/Warning
Event Summary: Pre-initialization of memory controller failed
Event Description: Failed to initialize internal communications engine on CPU. Field value is the physical location of the CPU's scalable memory buffer (SMB) that failed.
Probable Cause: Hardware
Event Category: Processor
Event Sub-Category: memory controller
Cause 1: Failed to initialize internal communications engine on CPU.
Recommended Action 1: The first action will be to check SEL for de-allocated DIMM(s). Reseat and/or replace the DIMM(s). If that does not solve the issue, replace CPU. If problem still continues to exist, replace the system board.

Event 9895

WBEM Severity: Degraded/Warning
Event Summary: DDR channel training failed
Event Description: DDR training failure. Data field is the physical location of the failed DDR channel
Probable Cause: Hardware
Event Category: Memory
Event Sub-Category: DIMM
Cause 1: DDR3 training failure.
Recommended Action 1: The first action will be to check SEL for de-allocated DIMM(s). Reseat and/or replace the DIMM(s). If that does not solve the issue, replace CPU. If problem still continues to exist, replace the system board.

Event 9896

WBEM Severity: Degraded/Warning
Event Summary: DDR calibration for commands failed
Event Description: DDR calibration of command failed. Data field is the physical location of the scalable memory buffer (SMB) that failed.
Probable Cause: Hardware
Event Category: Memory
Event Sub-Category: DIMM
Cause 1: DDR calibration of command failed
Recommended Action 1: The first action will be to check SEL for de-allocated DIMM(s). Reseat and/or replace the DIMM(s). If that does not solve the issue, replace CPU. If problem still continues to exist, replace the system board.

Event 9897

WBEM Severity: Degraded/Warning
Event Summary: Invalid DIMM detected
Event Description: Invalid DIMM data found. Data field is the physical location of the failed DIMM
Probable Cause: Hardware
Event Category: Memory
Event Sub-Category: DIMM
Cause 1: Invalid DIMM data found
Recommended Action 1: The first action will be to reseat the DIMM. If that does not solve the issue, replace DIMM with supported DIMM type (See Service Guide). If problem still continues to exist, contact support.

Event 9898

WBEM Severity: Degraded/Warning
Event Summary: The primary system variables are uninitialized.
Event Description: The primary system variables are uninitialized.
Probable Cause: System Variables uninitialized
Event Category: Primary System Variables EEPROM
Event Sub-Category: Unknown
Cause 1: The primary system variables are uninitialized.
Recommended Action 1: The system variables must be initialized. Please run SYSSET to initialize them.

Event 9899

WBEM Severity: Degraded/Warning
Event Summary: integrated Lights Out firmware battery failure or NVRAM state change.
Event Description: Integrated Lights Out detected improper data in NVRAM (bad checksums.) Either the NVRAM layout changed, or the integrated Lights Out Battery may not be maintaining the data through A/C power cycles.
Probable Cause: Battery Failure
Event Category: Support Firmware
Event Sub-Category: Unknown
Cause 1: Determine if the firmware was recently upgraded. This is often the reason for the NVRAM to change. If not, and the A/C power has been removed, than it's possible the battery is indeed going bad and would need to be replaced.
Recommended Action 1: Verify current supported version of firmware. Replace battery.

Event 9900

WBEM Severity: Degraded/Warning
Event Summary: integrated Light Out firmware software error.
Event Description: Integrated Lights Out detected a software error and is logging an event. The data represents data associated with the error seen.
Probable Cause: Software Error
Event Category: Support Firmware
Event Sub-Category: Unknown
Cause 1: A software error was detected and is being logged. The internal data is connected to the location and module where the error occurred. The Forward Progress Log may receive additional (lower alert level) event entries with more data associated with this event.
Recommended Action 1: Verify that the most recent version of firmware is installed. Please send this notification to Superdome2_fw_problem_report@groups.hp.com

Event 9901

WBEM Severity: Degraded/Warning
Event Summary: Power was forced to ON without permission from the Onboard Administrator.
Event Description: Power was forced to ON without permission from the Onboard Administrator.
Probable Cause: Power Problem
Event Category: Other Power
Event Sub-Category: OA power request skipped.
Cause 1: A forced power on occurred. Usually this is performed when a normal power on request is denied. The Onboard Administrator may now be running in a non-redundant or over-budget power configuration.
Recommended Action 1: Make sure Onboard Administrator has the appropriate number and configuration of power supplies. Reduce power required by the blade (for instance, remove some memory or a CPU.) Or, if there are powered-on blades that are not in use, power them off.

Event 9902

WBEM Severity: Degraded/Warning
Event Summary: Integrated Lights Out unable to communicate with OA after multiple retries.
Event Description: Integrated Lights Out has repeatedly tried to communicate with the Onboard Administrator and has not received any response.
Probable Cause: OA fault, reset, removed or busy
Event Category: Support Hardware
Event Sub-Category: OA
Cause 1: iLO has repeatedly requested communication with the Onboard Administrator and has not received a response. This may be because the EM has a fault condition, or is busy, being reset, or removed.
Recommended Action 1: The communication loss may have been temporary and nothing needs to be done if the communication is now working. Check the Fault LED on the enclosure manager. Reset the enclosure manager. Reset iLO. Replace the enclosure manager.

Event 9903

WBEM Severity: Fatal/Nonrecoverable
Event Summary: Power could not turn on because CPUs in the system or SBL Domain are mismatched.
Event Description: The system/SBL domain has CPUs of multiple part numbers installed and was unable to turn on as a result.
Probable Cause: Consistency check
Event Category: Processor
Event Sub-Category: mismatch
Cause 1: The system/SBL domain has CPUs of different S/SPEC and/or a delta greater than 1 in core stepping.
Recommended Action 1: Determine which CPU part number you want to keep, and remove those that don't match. DF from the CM> menu will display S/SPEC and stepping to help identify mismatch. When the CPUs all match try to power on again.

Event 9904

WBEM Severity: Fatal/Nonrecoverable
Event Summary: The installed SBL is incompatible for the enclosure type, or blade bay.
Event Description: The installed SBL is incompatible with the current enclosure type or blade bay.
Probable Cause: Consistency check
Event Category: SBL
Event Sub-Category: mismatch
Cause 1: Each SBL2/SBL4 is constructed for the precise width of the enclosure bays. SBL2-7000, SBL2E-7000, and SBL4-7000 are designed for the c7000 enclosure. SBL2-3000, SBL2E-3000, and SBL4-3000 are designed for the c3000 enclosure. The SBL2-7000 and SBL2-3000 must be installed with the monarch blade in bay 1, 3, 5, or 7. The SBL2E-7000 and SBL2E-3000 must be installed with the monarch blade in bay 2, 4, or 6. The SBL4 must be installed with the monarch blade in bay 1 or 5. This event is being generated because the installed SBL does not match the environment.
Recommended Action 1: Change your installation to a supported configuration.

Event 9905

WBEM Severity: Fatal/Nonrecoverable
Event Summary: Power on failed due to an SBL (Scalable Blade Link) mismatch
Event Description: Power on failed because the installed SBL (Scalable Blade Link) is incompatible with the enclosure type or blade bay.
Probable Cause: Consistency check
Event Category: SBL
Event Sub-Category: mismatch
Cause 1: Each SBL2/SBL4 is constructed for the precise width of the enclosure bays. SBL2-7000, SBL2E-7000, and SBL4-7000 are designed for the c7000 enclosure. SBL2-3000, SBL2E-3000, and SBL4-3000 are designed for the c3000 enclosure. The SBL2-7000 and SBL2-3000 must be installed with the monarch blade in bay 1, 3, 5, or 7. The SBL2E-7000 and SBL2E-3000 must be installed with the monarch blade in bay 2, 4, or 6. The SBL4 must be installed with the monarch blade in bay 1 or 5. This event is being generated because the installed SBL does not match the environment.
Recommended Action 1: Change your installation to a supported configuration. Then attempt power on again.

Event 9906

WBEM Severity: Critical
Event Summary: Firmware on the system is mismatched
Event Description: The system has mismatched firmware on it.
Probable Cause: Firmware
Event Category: revision
Event Sub-Category: mismatched
Cause 1: One of the FW types within the system has a mismatch across blades.
Recommended Action 1: Use the SR command from the CM> menu or look in the iLO web GUI to identify the mismatched FW and bring it up to date with the rest of the system.

Event 9907

WBEM Severity: Fatal/Nonrecoverable
Event Summary: Power failed to turn on due to mismatched firmware
Event Description: Power failed to turn on due to a firmware mismatch.
Probable Cause: firmware
Event Category: revision
Event Sub-Category: mismatch
Cause 1: The revision of one of the ROMs in the system does not match the revision of its counterparts. One of the FW types within the system has a mismatch.
Recommended Action 1: Use the iLO SR command from the CM> menu or look in the iLO web GUI to identify the mismatched FW and bring it up to date with the rest of the system.

Event 9908

WBEM Severity: Critical
Event Summary: The CPU power pod is no longer powering the CPU.
Event Description: The CPU power pod is no longer powering the CPU.
Probable Cause: Power Problem
Event Category: Processor Power
Event Sub-Category: Unknown
Cause 1: The CPU power pod is no longer providing power to the CPU. It may not be plugged in to the system board, or it may have failed.
Recommended Action 1: If not plugged into the system board, plug it in. Check that the connector is not loose. If not then you should replace the FRU.

Event 9909

WBEM Severity: Critical
Event Summary: This blade has failed to show signs of boot.
Event Description: The blade logging the event has failed to boot.
Probable Cause: Processor Problem (Internal Machine Error)
Event Category: Processor
Event Sub-Category: Unknown
Cause 1: Something has caused the blade to fail to boot. No BOOT_START event was detected from this blade. Could be the result of a corrupted SFW ROM, a failing processor, or a board failure of the QPI link.
Recommended Action 1: At the next convenient opportunity power cycle the system power to all blades that are configured as part of a system with the failed blade. Look for other errors that may have been logged. Reflash the SFW.

Event 9910

WBEM Severity: Degraded/Warning
Event Summary: ICH Mezzanine card is missing
Event Description: ICH Mezzanine card is missing.
Probable Cause: communications error
Event Category: communication to ICH MEZZ FRU
Event Sub-Category: Unknown
Cause 1: The communications to the ICH MEZZ may have failed. Otherwise the ICH MEZZ is not present.
Recommended Action 1: The system will fail to power on if there is no ICH MEZZ on the monarch blade. Please validate proper loading of the ICH MEZZ card if a pc on fails.

Event 9911

WBEM Severity: Fatal/Nonrecoverable
Event Summary: The system failed to power on upon request.
Event Description: The system failed to power on.
Probable Cause: Power Problem
Event Category: System Power
Event Sub-Category: Unknown
Cause 1: Power on was denied because there was a failure in the power on sequence. This probably points towards HW or communication synchronization issues.
Recommended Action 1: Reset iLO and try again. If this doesn't work remove STBY power and try again.

Event 9912

WBEM Severity: Degraded/Warning
Event Summary: A blade failed to power on upon request.
Event Description: A blade failed to power on.
Probable Cause: Power Problem
Event Category: System Power
Event Sub-Category: Unknown
Cause 1: A blade has failed to power on.
Recommended Action 1: -

Event 9913

WBEM Severity: Fatal/Nonrecoverable
Event Summary: System failed to power on because the monarch blade failed to power on.
Event Description: System failed to power on because the monarch blade failed to power on.
Probable Cause: Power Problem
Event Category: System Power
Event Sub-Category: Monarch
Cause 1: A failure on the Monarch has resulted in a failure to power on. As a result the system will be powered off.
Recommended Action 1: Try power on again. Reset iLO and try power on again. Remove STBY power and then try power on again.

Event 9914

WBEM Severity: Critical
Event Summary: A previously powered on blade has lost power.
Event Description: A previously powered on blade has lost power.
Probable Cause: Power Problem
Event Category: System Power
Event Sub-Category: blade local
Cause 1: The blade indicated by the event has unexpectedly lost power.
Recommended Action 1: At the next available opportunity power off the system and power on again. Monitor the blade to make sure this event doesn't happen again.

Event 9915

WBEM Severity: Fatal/Nonrecoverable
Event Summary: The system has been powered off due to a power failure.
Event Description: The system has been powered off due to a power failure.
Probable Cause: Power Problem
Event Category: System Power
Event Sub-Category: Unknown
Cause 1: One or more blades had a power failure. As a result the system control is powering off the entire partition.
Recommended Action 1: Try power on again. If it fails try with a reset to iLO and a removal of STBY power. If system powers back on properly monitor to make sure this doesn't occur again.

Event 9916

WBEM Severity: Degraded/Warning
Event Summary: The system variables are mismatched.
Event Description: The system variables are mismatched
Probable Cause: mismatch in SYSVARs EEPROM
Event Category: EEPROM
Event Sub-Category: SYSVARS
Cause 1: The contents in the system variables EEPROMs don't match. This indicates that the system variables have been programmed, but they don't match.
Recommended Action 1: Run the SYSSET command to bring the system variables EERPOMs into alignment.

Event 9917

WBEM Severity: Critical
Event Summary: The Power Monitor is in programming mode
Event Description: The Power Monitor is left in programming mode. Power protection features are disabled while Power Monitor remains in this state.
Probable Cause: powered off in middle of power monitor update
Event Category: iLO
Event Sub-Category: power
Cause 1: The most likely cause is that the standby power was removed (blade removed from enclosure) while in the middle of updating the power monitory PIC. In this mode power protection is not enabled.
Recommended Action 1: Install current supported version of the Complex firmware (which includes power monitor firmware).

Event 9918

WBEM Severity: Fatal/Nonrecoverable
Event Summary: Power failed to turn on because there is no SBL (Scalable Blade Link) attached.
Event Description: Power failed to turn on because there is no SBL (Scalable Blade Link) attached. Power on is not allowed without an SBL attached.
Probable Cause: SBL or blade
Event Category: System Power
Event Sub-Category: SBL
Cause 1: Power can not be turned on without an attached SBL.
Recommended Action 1: Attach an appropriate SBL if you want to power on. If an SBL is already attached remove and inspect its pins. Also, inspect the blade side connector. If there are no bent pins and the connector looks ok reseat the SBL and try again.

Event 9919

WBEM Severity: Fatal/Nonrecoverable
Event Summary: Power on denied by the OA with an UNKNOWN error code.
Event Description: The OA has denied power to the SVB (sever blade) with an unknown error code. Any data included in the data field is a return code for developer debug.
Probable Cause: OA FW mismatch to iLO FW
Event Category: System Power
Event Sub-Category: peer to peer communication
Cause 1: iLO was denied power by the OA with an error code that was unknown to iLO.
Recommended Action 1: Refer to the recipe documentation to make sure that your OA version is compatible with the iLO FW you are using. Try resetting OA.

Event 9920

WBEM Severity: Degraded/Warning
Event Summary: Indicates an error has occurred while trying to reset SAS controllers.
Event Description: Indicates which of several errors has occurred while trying to reset PMC SAS controllers.
Probable Cause: Adapter/Card Error
Event Category: Device Firmware
Event Sub-Category: Unknown
Cause 1: An error has occurred while trying to reset the SAS controller after a GMCA or during I/O discovery.
Recommended Action 1: Replace drive. Update firmware on SAS controller. Verify that the system firmware is at a supported revision. If problem persists, contact support.

Event 9921

WBEM Severity: Fatal/Nonrecoverable
Event Summary: Power not turned on. The iLO peer to peer LAN communication is not functional.
Event Description: The power will not be turned on. The iLO peer to peer LAN communication is not fully functioning.
Probable Cause: probably the internal network is having issues
Event Category: System Power
Event Sub-Category: SBL
Cause 1: The iLO peer to peer LAN communication is not fully functioning. Could be caused by issues with the internal LAN or iLO code.
Recommended Action 1: Review the logs to determine details of failure. The management system will attempt to repair itself. If the management system does not recover refer to the Service Guide to determine how to reset iLO without a user interface.

Event 9922

WBEM Severity: Fatal/Nonrecoverable
Event Summary: The system will experience a hard reset as a result of a watchdog timeout.
Event Description: The system will experience a hard reset as a result of a watchdog timeout.
Probable Cause: watchdog timeout
Event Category: Software Application
Event Sub-Category: OS hang
Cause 1: The OS Watchdog has timed out.
Recommended Action 1: System will be reset. Determine why the OS did not reset the watchdog. Consider changing the action to "no action" for debug. Look for other unusual OS activity.

Event 9923

WBEM Severity: Fatal/Nonrecoverable
Event Summary: The system will power down as a result of a watchdog timeout.
Event Description: The system will power down as a result of a watchdog timeout.
Probable Cause: watchdog timeout
Event Category: Software Application
Event Sub-Category: OS hang
Cause 1: The OS Watchdog has timed out.
Recommended Action 1: Review logs and power system back on if no concerning events are observed. Determine why OS failed to reset the watchdog. Consider changing action to "no action" for debug. Look for other unusual OS activity.

Event 9924

WBEM Severity: Fatal/Nonrecoverable
Event Summary: The system will power cycle as a result of a watchdog timeout.
Event Description: The system will power cycle as a result of a watchdog timeout.
Probable Cause: watchdog timeout
Event Category: Software Application
Event Sub-Category: OS hang
Cause 1: The OS Watchdog has timed out.
Recommended Action 1: None. System will power back on in a moment.

Event 9925

WBEM Severity: Critical
Event Summary: Unable to retrieve error information after a fatal error.
Event Description: Unable to retrieve error information after a fatal error.
Probable Cause: fatal error without valid registers for HW setup
Event Category: System Firmware
Event Sub-Category: Unknown
Cause 1: A fatal error has occurred. In attempting to configure hardware for error information recovery the valid signature wasn’t found in the fatal error registers.
Recommended Action 1: Review logs for indicators of what might have happened, and monitor system health.

Event 9926

WBEM Severity: Critical
Event Summary: Failed to initialize shared memory.
Event Description: Failed to initialize shared memory.
Probable Cause: RAM access or FW/RTOS
Event Category: iLO
Event Sub-Category: shared memory
Cause 1: Either the hardware (RAM) did not respond to the initialization requests, or there was a FW issue during setup of the shared memory task.
Recommended Action 1: Try resetting iLO with an xd->R command from the iLO CM> prompt.

Event 9927

WBEM Severity: Critical
Event Summary: The Display Board is not responding and may be missing.
Event Description: The Display Board is not responding and may be missing.
Probable Cause: missing FRU
Event Category: FRU
Event Sub-Category: none
Cause 1: The Display Board is not responding. It is either missing or loose. This board includes sensors such as the altimeter and a thermal sensor so operation may be altered.
Recommended Action 1: Check if the board is present. If not replace it. If it is, remove it and re-insert it to ensure proper connectivity.

Event 9928

WBEM Severity: Critical
Event Summary: Indicates an inconsistency in bus numbering has been discovered.
Event Description: Indicates an inconsistency in bus numbering has been discovered.
Probable Cause: Hardware
Event Category: System Hardware
Event Sub-Category: Unknown
Cause 1: The bus number returned by GetSystemSocketsInfo() does not match what is expected.
Recommended Action 1: Ensure all systems in the enclosure are conjoined as required and functioning. Verify the SBL is installed and seated properly. If problem persists, contact support.

Event 9929

WBEM Severity: Critical
Event Summary: A power supply has failed. Physical Location is included in data field.
Event Description: A power supply has failed. A Physical Location is included in the data field.
Probable Cause: Power Supply Failure
Event Category: System Power
Event Sub-Category: Unknown
Cause 1: A power supply has failed. The connection could be loose or there could be a hardware failure.
Recommended Action 1: Identify the failing supply from the physical location included in the alert. Check connections. If no loose connections are found replace the power supply.

Event 9930

WBEM Severity: Critical
Event Summary: A fan has failed.
Event Description: A fan has failed. Check the data field for Physical Location.
Probable Cause: Fan Failure
Event Category: System Hardware
Event Sub-Category: Unknown
Cause 1: A connection may be bad. Otherwise a fan has probably failed.
Recommended Action 1: Identify the Physical Location indicated in the data field. Check connections and fan health. If connections are ok replace failed fan.

Event 9985

WBEM Severity: Fatal/Nonrecoverable
Event Summary: System Firmware internal error detected resulting in execution of ASSERT macro
Event Description: This event is generated when an unexpected assert condition is encountered in System Firmware. The following events indicate which module generated the condition and the line number where it occurred.
Probable Cause: Unknown
Event Category: System Firmware
Event Sub-Category: ASSERT
Cause 1: The cause is unknown.
Recommended Action 1: Examine previous events and ASCII information following this event for more information. If problem persists, contact support.

Event 9986

WBEM Severity: Degraded/Warning
Event Summary: System Firmware internal error detected resulting in execution of ASSERT macro
Event Description: This event is generated when an unexpected assert condition is encountered in System Firmware. The following events indicate which module generated the condition and the line number where it occurred.
Probable Cause: Unknown
Event Category: System Firmware
Event Sub-Category: ASSERT
Cause 1: The cause is unknown.
Recommended Action 1: Examine previous events and ASCII information following this event for more information. If problem persists, contact support.

Event 9990

WBEM Severity: Major
Event Summary: Thread has failed Early Self-test and is now operating with degraded performance
Event Description: Thread has failed Early Self-test and is now operating with degraded performance. See the subsequent BOOT_CPU_PHYSICAL_LOCATION for physical location of cpu with degraded performance.
Probable Cause: Processor Problem (Internal Machine Error)
Event Category: Processor
Event Sub-Category: Unknown
Cause 1: Thread has failed early self-test.
Recommended Action 1: Reboot the system. If the problem persists, contact support for help to replace the CPU.

Event 10065

WBEM Severity: Minor
Event Summary: Failed to notify manageability of a change to the real-time-clock device.
Event Description: The EFI subsystem could not notify manageability of a change to the real-time-clock device.
Probable Cause: Transmit Failure
Event Category: System Firmware
Event Sub-Category: SFW/MFW communication channel
Cause 1: The EFI subsystem could not notify manageability of a change to the real-time-clock device.
Recommended Action 1: Verify that the System Firmware is at its supported revision, and if not, update firmware to the latest supported version. Restart the system. If problem persists contact support.

Event 10067

WBEM Severity: Critical
Event Summary: ACPI parser error due to a missing AML identifier
Event Description: The ACPI subsystem encountered a missing AML identifier while parsing the DSDT table. This could also prevent the Operating System from booting successfully. This could cause the Operating System to crash after it has booted successfully.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: ACPI Subsystem
Cause 1: The ACPI subsystem could not find the doorbell AML identifier while parsing the DSDT table.
Recommended Action 1: Ensure SFW component is at supported level.

Event 10072

WBEM Severity: Critical
Event Summary: Memory Configuration rendevous failed
Event Description: Memory configuration rendevous failed. Mark the start of the Memory Configuration rendevous point Data format: 0xAABB AA = Blade Number BB = Cpu Number
Probable Cause: System
Event Category: System Hardware
Event Sub-Category: NVRAM
Cause 1: Read from non-volatile memory failed.
Recommended Action 1: Reset the system and attempt to reboot again. If problem persists, contact support.

Event 10073

WBEM Severity: Degraded/Warning
Event Summary: iLO was unable to initialize user accounts.
Event Description: iLO was unable to initialize user accounts.
Probable Cause: bad data in EEPROM or checksum failed
Event Category: iLO
Event Sub-Category: Users
Cause 1: iLO was unable to read the default user account data from EEPROM. The default user data contained in the EEPROM was likely bad, or the checksum failed.
Recommended Action 1: There is no factory default password at this point- all passwords will be refused. Use the physical presence button to force iLO into security override mode. This will allow you to log into iLO without a user account. Use the UC command or web GUI to setup iLO user account(s) again.

Event 10166

WBEM Severity: Degraded/Warning
Event Summary: SFW discarded one or more in progress SFW events before they got logged by iLO.
Event Description: SFW events were discarded to speed up SFW startup. Event queues have been re-initialized and restarted.
Probable Cause: degraded iLO or SFW, perhaps an MCA loop.
Event Category: iLO
Event Sub-Category: Logs
Cause 1: The SFW event queue overflowed and remained that way for a duration of time. This could result from poor iLO queue draining (logging) performance, or could be related to the number of event being issued by SFW in a short period of time.
Recommended Action 1: None.

Event 10172

WBEM Severity: Degraded/Warning
Event Summary: The iLO config was unexpectedly defaulted. Settings may need to be re-entered.
Event Description: The iLO config was unexpectedly reset to default values. Settings may need to be re-entered.
Probable Cause: Software Error
Event Category: iLO
Event Sub-Category: config/NVRAM
Cause 1: Some bad data in the iLO config area of NVRAM was detected and as a result config was defaulted. It is not believe that this was caused by a battery failure or user action.
Recommended Action 1: Re-enter any lost configuration data.

Event Number: 10175

WBEM Severity: Degraded/Warning
Event Summary: The local blade failed to power off upon request.
Event Description: The local blade failed to power off upon request.
Probable Cause: Power Problem
Event Category: System Power
Event Sub-Category: Unknown
Cause 1: This blade has failed to power off.
Recommended Action 1: Try resetting iLO and attempting power off again.

Event 10176

WBEM Severity: Degraded/Warning
Event Summary: The system has failed to power off upon request.
Event Description: The system has failed to power off upon request.
Probable Cause: Power Problem
Event Category: System Power
Event Sub-Category: Unknown
Cause 1: the rack or one or more blades have failed to power off. The overall power off action has failed as a result.
Recommended Action 1: reset iLO and attempt power off again.

Event 10223

WBEM Severity:
Event Summary: A data table stored in non-volatile RAM is invalid.
Event Description: The DOT table saved in NVRAM is out of date or corrupt. All firmware in the system should be updated and NVRAM may need to be cleared.
Probable Cause: Software Error
Event Category: System Firmware
Event Sub-Category: DOT table stored in NVRAM
Cause 1: Manageability or System FW revisions are out of date or corrupted
Recommended Action 1: Ensure that all firmware in the system is up to date.

Event 10250

WBEM Severity: Degraded/Warning
Event Summary: Unable to retrieve information for restoring the state of PCIe after a GMCA
Event Description: Indicates which of several errors have occurred while trying to retrieve PCIe state save information from the DOT. Some attempts are made to recover from these errors, so they don't necessarily indicate a critical failure. If PCIe state save information could not be restored after all recovery attempts exhausted, the OS may not be able to dump to disk, and architected PCIe errors will not be logged.
Probable Cause: NVRAM corruption or SFW-MFW communication error
Event Category: System Firmware
Event Sub-Category: Data Object Table
Cause 1: An error has prevented system firmware from accessing the I/O state save area of the DOT. Possible causes are data corruption of NVRAM or communication error between SFW and MFW.
Recommended Action 1: Ensure system firmware recipe is accurate and up-to-date.

Event 10359

WBEM Severity: Fatal/Nonrecoverable
Event Summary: The system has lost AC power.
Event Description: The system has lost AC power. This will result in a loss of system power and standby power unless the AC power is restored.
Probable Cause: Power Supply Failure
Event Category: System Power
Event Sub-Category: Unknown
Cause 1: Most likely cause is removal of an AC power cord, or a bulk power supply failure.
Recommended Action 1: Make sure that the AC Power cord is properly installed, and the bulk power supply is functional

Event 10366

WBEM Severity: Degraded/Warning
Event Summary: The Power Button was asserted prior to changing the system power.
Event Description: The Power Button was asserted prior to changing the system power.
Probable Cause: Power Problem
Event Category: System Power
Event Sub-Category: power button asserted or stuck
Cause 1: The power button must be released before remotely controlling system power. The button may be stuck.
Recommended Action 1: Inspect the power button and correct anything which may affect its proper operation.

Event 10384

WBEM Severity: Degraded/Warning
Event Summary: ICH failed to respond to an i2c query
Event Description: The ICH failed respond to an i2c request.
Probable Cause: ICH device may have failed
Event Category: ICH mezz
Event Sub-Category: Unknown
Cause 1: The ICH device failed to respond to an i2c request. It is probable that the ICH device is in a failed state.
Recommended Action 1: Investigate the ICH MEZZ card to determine if there has been a failure.

Event 10405

WBEM Severity: Critical
Event Summary: The chassis has been open for an extended period of time.
Event Description: The chassis has been open for an extended period of time.
Probable Cause: Enclosure Door Open
Event Category: System Cooling
Event Sub-Category: Unknown
Cause 1: The chassis door or top cover is open. More specifically it has been open for an extended period of time.
Recommended Action 1: Close the door or top cover.

Event 10407

WBEM Severity: Fatal/Nonrecoverable
Event Summary: Indicates the API for nPar reset during a Global Machine Check Abort failed.
Event Description: The nPartition will remain in an MCA state and requires manual intervention to reboot it back up using the ParCon commands.
Probable Cause: Software Error
Event Category: Support Firmware
Event Sub-Category: Unknown
Cause 1: Firmware API call failed
Recommended Action 1: Use ParCon commands to reboot the partition.