System Event Log Messages for IPMI Systems
The tables in this chapter list the system event log (SEL) messages, their severity, and cause.
![]() ![]() |
NOTE: For corrective actions, see the appropriate documentation. |
Temperature Sensor Events
The temperature sensor event messages help protect critical components by alerting the systems management console when the temperature rises inside the chassis. These event messages use additional variables, such as sensor location, chassis location, previous state, and temperature sensor value or state.
Voltage Sensor Events
The voltage sensor event messages monitor the number of volts across critical components. These messages provide status and warning information for voltage sensors for a particular chassis.
Fan Sensor Events
The cooling device sensors monitor how well a fan is functioning. These messages provide status warning and failure messages for fans for a particular chassis.
Processor Status Events
The processor status messages monitor the functionality of the processors in a system. These messages provide processor health and warning information of a system.
Power Supply Events
The power supply sensors monitor the functionality of the power supplies. These messages provide status and warning information for power supplies for a particular system.
Memory ECC Events
The memory ECC event messages monitor the memory modules in a system. These messages monitor the ECC memory correction rate and the type of memory events that occurred.
BMC Watchdog Events
The BMC watchdog operations are performed when the system hangs or crashes. These messages monitor the status and occurrence of these events in a system.
Memory Events
The memory modules can be configured in different ways in particular systems. These messages monitor the status, warning, and configuration information about the memory modules in the system.
Hardware Log Sensor Events
The hardware logs provide hardware status messages to the system management software. On particular systems, the subsequent hardware messages are not displayed when the log is full. These messages provide status and warning messages when the logs are full.
Drive Events
The drive event messages monitor the health of the drives in a system. These events are generated when there is a fault in the drives indicated.
Intrusion Events
The chassis intrusion messages are a security measure. Chassis intrusion alerts are generated when the system's chassis is opened. Alerts are sent to prevent unauthorized removal of parts from the chassis.
BIOS Generated System Events
The BIOS-generated messages monitor the health and functionality of the chipsets, I/O channels, and other BIOS-related functions.
Event Message |
Severity |
Cause |
---|---|---|
System Event I/O channel chk. |
Critical |
This event is generated when a critical interrupt is generated in the I/O Channel. |
System Event PCI Parity Err. |
Critical |
This event is generated when a parity error is detected on the PCI bus. |
System Event Chipset Err. |
Critical |
This event is generated when a chip error is detected. |
System Event PCI System Err. |
Information |
This event indicates historical data, and is generated when the system has crashed and recovered. |
System Event PCI Fatal Err. |
Critical |
This error is generated when a fatal error is detected on the PCI bus. |
System Event PCIE Fatal Err. |
Critical |
This error is generated when a fatal error is detected on the PCIE bus. |
POST Err |
Critical |
This event is generated when an error occurs during system boot. See the system documentation for more information on the error code. |
POST fatal error #<number> or <error description> |
Critical |
This event is generated when a fatal error occurs during system boot. See Table 4-13 for more information. |
Memory Spared redundancy lost |
Critical |
This event is generated when memory spare is no longer redundant. |
Memory Mirrored redundancy lost |
Critical |
This event is generated when memory mirroring is no longer redundant. |
Memory RAID redundancy lost |
Critical |
This event is generated when memory RAID is no longer redundant. |
Err Reg Pointer OEM Diagnostic data event was asserted |
Information |
This event is generated when an OEM event occurs. OEM events can be used by Dell service team to better understand the cause of the failure. |
System Board PFault Fail Safe state asserted |
Critical |
This event is generated when the system board voltages are not at normal levels. |
System Board PFault Fail Safe state deasserted |
Information |
This event is generated when earlier PFault Fail Safe system voltages return to a normal level. |
Memory Add (BANK# DIMM#) presence was asserted |
Information |
This event is generated when memory is added to the system. |
Memory Removed (BANK# DIMM#) presence was asserted |
Information |
This event is generated when memory is removed from the system. |
Memory Cfg Err configuration error (BANK# DIMM#) was asserted |
Critical |
This event is generated when memory configuration is incorrect for the system. |
Mem Redun Gain redundancy regained |
Information |
This event is generated when memory redundancy is regained. |
Mem ECC Warning transition to non-critical from OK |
Warning |
This event is generated when correctable ECC errors have increased from a normal rate. |
Mem ECC Warning transition to critical from less severe |
Critical |
This event is generated when correctable ECC errors reach a critical rate. |
Mem CRC Err transition to non-recoverable |
Critical |
This event is generated when CRC errors enter a non-recoverable state. |
Mem Fatal SB CRC
uncorrectable ECC was |
Critical |
This event is generated while storing CRC errors to memory. |
Mem Fatal NB CRC
uncorrectable ECC was |
Critical |
This event is generated while removing CRC errors from memory. |
Mem Overtemp critical over temperature was asserted |
Critical |
This event is generated when system memory reaches critical temperature. |
USB Over-current transition to non-recoverable |
Critical |
This event is generated when the USB exceeds a predefined current level. |
Hdwr version err hardware incompatibility |
Critical |
This event is generated when there is a mismatch between the BMC and iDRAC firmware and the processor in use or vice versa. |
Hdwr version err hardware incompatibility (BMC/iDRAC Firmware and CPU mismatch) was deasserted |
Information |
This event is generated when an earlier mismatch between the BMC and iDRAC firmware and the processor is corrected. |
SBE Log Disabled correctable memory error logging disabled was asserted |
Critical |
This event is generated when the ECC single bit error rate is exceeded. |
CPU Protocol Err
transition to |
Critical |
This event is generated when the processor protocol enters a non-recoverable state. |
CPU Bus PERR
transition to |
Critical |
This event is generated when the processor bus PERR enters a non-recoverable state. |
CPU Init Err
transition to |
Critical |
This event is generated when the processor initialization enters a non-recoverable state. |
CPU Machine Chk
transition to |
Critical |
This event is generated when the processor machine check enters a non-recoverable state. |
Logging Disabled all event logging disabled was asserted |
Critical |
This event is generated when all event logging is disabled. |
LinkT/FlexAddr: Link Tuning sensor, device option ROM failed to support link tuning or flex address (Mezz XX) was asserted |
Critical |
This event is generated when the PCI device option ROM for a NIC does not support link tuning or the Flex addressing feature. |
LinkT/FlexAddr: Link Tuning sensor, failed to program virtual MAC address (<location>) was asserted. |
Critical |
This event is generated when BIOS fails to program virtual MAC address on the given NIC device. |
PCIE NonFatal Er: Non Fatal IO Group sensor, PCIe error(<location>) |
Warning |
This event is generated in association with a CPU IERR. |
I/O Fatal Err: Fatal IO Group sensor, fatal IO error (<location>) |
Critical |
This event is generated in association with a CPU IERR and indicates the PCI/PCIe device that caused the CPU IERR. |
Unknown system event sensor unknown system hardware failure was asserted |
Critical |
This event is generated when an unknown hardware failure is detected. |
POST Code Table
Table 4-13 lists the POST Code errors that are generated when a fatal error occurs during system boot.
Operating System Generated System Events
Cable Interconnect Events
The cable interconnect messages in Table 4-15 are used for detecting errors in the hardware cabling.
Battery Events
Power And Performance Events
The power and performance events are used to detect degradation in system performance with change in power supply.
Entity Presence Events
The entity presence messages are used for detecting different hardware devices.
Miscellaneous
The following table provides events related to hardware and software components like mezzanine cards, sensors, firmware etc. and compatibility issues.