The following tables list the system event log (SEL) messages, their severity, and cause.
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.
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.
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.
The processor status messages monitor the functionality of the processors in a system. These messages provide processor health and warning information of a system.
|
Event Message
|
Severity
|
Cause
|
|---|
|
<Processor Entity> status processor sensor IERR, where <Processor Entity> is the processor that generated the event. For example, PROC for a single processor system and PROC # for multiprocessor system.
| Critical
| IERR internal error generated by the <Processor Entity>.
|
|
<Processor Entity> status processor sensor Thermal Trip.
| Critical
| The processor generates this event before it shuts down because of excessive heat caused by lack of cooling or heat synchronization.
|
|
<Processor Entity> status processor sensor recovered from IERR.
| Information
| This event is generated when a processor recovers from the internal error.
|
|
<Processor Entity> status processor sensor disabled.
| Warning
| This event is generated for all processors that are disabled.
|
|
<Processor Entity> status processor sensor terminator not present.
| Information
| This event is generated if the terminator is missing on an empty processor slot.
|
|
< Processor Entity> presence was deasserted.
| Critical
| This event is generated when the system could not detect the processor.
|
|
<Processor Entity> presence was asserted.
| Information
| This event is generated when the earlier processor detection error was corrected.
|
|
<Processor Entity> thermal tripped was deasserted.
| Information
| This event is generated when the processor has recovered from an earlier thermal condition.
|
|
<Processor Entity> configuration error was asserted.
| Critical
| This event is generated when the processor configuration is incorrect.
|
|
<Processor Entity> configuration error was deasserted.
| Information
| This event is generated when the earlier processor configuration error was corrected.
|
|
<Processor Entity> throttled was asserted.
| Warning
| This event is generated when the processor slows down to prevent over heating.
|
|
<Processor Entity> throttled was deasserted.
| Information
| This event is generated when the earlier processor throttled event was corrected.
|
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.
|
Event Message
|
Severity
|
Cause
|
|---|
|
<Power Supply Sensor Name> power supply sensor removed.
| Critical
| This event is generated when the power supply sensor is removed.
|
|
<Power Supply Sensor Name> power supply sensor AC recovered.
| Information
| This event is generated when the power supply has been replaced.
|
|
<Power Supply Sensor Name> power supply sensor returned to normal state.
| Information
| This event is generated when the power supply that failed or removed was replaced and the state has returned to normal.
|
|
<Entity Name> PS Redundancy sensor redundancy degraded.
| Information
| Power supply redundancy is degraded if one of the power supply sources is removed or failed.
|
|
<Entity Name> PS Redundancy sensor redundancy lost.
| Critical
| Power supply redundancy is lost if only one power supply is functional.
|
|
<Entity Name> PS Redundancy sensor redundancy regained.
| Information
| This event is generated if the power supply has been reconnected or replaced.
|
|
<Power Supply Sensor Name> predictive failure was asserted
| Warning
| This event is generated when the power supply is about to fail.
|
|
<Power Supply Sensor Name> input lost was asserted
| Critical
| This event is generated when the power supply is unplugged.
|
|
<Power Supply Sensor Name> predictive failure was deasserted
| Information
| This event is generated when the power supply has recovered from an earlier predictive failure event.
|
|
<Power Supply Sensor Name> input lost was deasserted
| Information
| This event is generated when the power supply is plugged in.
|
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.
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.
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.
|
Event Message
|
Severity
|
Cause
|
|---|
|
Memory RAID redundancy degraded.
| Information
| This event is generated when there is a memory failure in a RAID-configured memory configuration.
|
|
Memory RAID redundancy lost.
| Critical
| This event is generated when redundancy is lost in a
RAID-configured memory configuration.
|
|
Memory RAID redundancy regained
| Information
| This event is generated when the redundancy lost or degraded earlier is regained in a RAID-configured memory configuration.
|
|
Memory Mirrored redundancy degraded.
| Information
| This event is generated when there is a memory failure in a mirrored memory configuration.
|
|
Memory Mirrored redundancy lost.
| Critical
| This event is generated when redundancy is lost in a mirrored memory configuration.
|
|
Memory Mirrored redundancy regained.
| Information
| This event is generated when the redundancy lost or degraded earlier is regained in a mirrored memory configuration.
|
|
Memory Spared redundancy degraded.
| Information
| This event is generated when there is a memory failure in a spared memory configuration.
|
|
Memory Spared redundancy lost.
| Critical
| This event is generated when redundancy is lost in a spared memory configuration.
|
|
Memory Spared redundancy regained.
| Information
| This event is generated when the redundancy lost or degraded earlier is regained in a spared memory configuration.
|
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.
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.
|
Event Message
|
Severity
|
Cause
|
|---|
|
Drive <Drive #> asserted fault state.
| Critical
| This event is generated when the specified drive in the array is faulty.
|
|
Drive <Drive #> de-asserted fault state.
| Information
| This event is generated when the specified drive recovers from a faulty condition.
|
|
Drive <Drive #>
drive presence was asserted
| Informational
| This event is generated when the drive is installed.
|
|
Drive <Drive #>
predictive failure was asserted
| Warning
| This event is generated when the drive is about to fail.
|
|
Drive <Drive #>
predictive failure was deasserted
| Informational
| This event is generated when the drive from earlier predictive failure is corrected.
|
|
Drive <Drive #>
hot spare was asserted
| Warning
| This event is generated when the drive is placed in a hot spare.
|
|
Drive <Drive #>
hot spare was deasserted
| Informational
| This event is generated when the drive is taken out of hot spare.
|
|
Drive <Drive #>
consistency check in progress was asserted
| Warning
| This event is generated when the drive is placed in consistency check.
|
|
Drive <Drive #>
consistency check in progress was deasserted
| Informational
| This event is generated when the consistency check of the drive is completed.
|
|
Drive <Drive #>
in critical array was
asserted
| Critical
| This event is generated when the drive is placed in critical array.
|
|
Drive <Drive #>
in critical array was deasserted
| Informational
| This event is generated when the drive is removed from critical array.
|
|
Drive <Drive #>
in failed array was asserted
| Critical
| This event is generated when the drive is placed in the fail array.
|
|
Drive <Drive #>
in failed array was deasserted
| Informational
| This event is generated when the drive is removed from the fail array.
|
|
Drive <Drive #>
rebuild in progress was asserted
| Informational
| This event is generated when the drive is rebuilding.
|
|
Drive <Drive #>
rebuild aborted was asserted
| Warning
| This event is generated when the drive rebuilding process is aborted.
|
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.
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
POST fatal error #<number> or <error description>
| Critical
| This event is generated when an error occurs during system boot. See the system documentation for more information on the error code.
|
|
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.
|
|
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 returns 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
asserted
| Critical
| This event is generated when CRC errors occur while storing to memory.
|
|
Mem Fatal NB CRC
uncorrectable ECC was
asserted
| Critical
| This event is generated when CRC errors occur while removing 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
(BMC/iDRAC Firmware and CPU mismatch) was asserted
| 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 the earlier mismatch between the BMC and iDRAC firmware and the processor is corrected.
|
|
Hdwr version err
hardware incompatibility
(BMC/iDRAC Firmware and CPU mismatch) was deasserted
| Information
| This event is generated when an earlier hardware mismatch 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
non-recoverable
| Critical
| This event is generated when the processor protocol enters a non-recoverable state.
|
|
CPU Bus PERR
transition to
non-recoverable
| Critical
| This event is generated when the processor bus PERR enters a non-recoverable state.
|
|
CPU Init Err
transition to
non-recoverable
| Critical
| This event is generated when the processor initialization enters a non-recoverable state.
|
|
CPU Machine Chk
transition to
non-recoverable
| 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 which device 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.
|
The cable interconnect messages are used for detecting errors in the hardware cabling.
The power and performance events are used to detect degradation in system performance with change in power supply.
The entity presence messages are used for detecting different hardware devices.
