HP Insight Management WBEM Provider Events Reference Guide

A processor has mapped out all spare cache lines. Probable Cause: The processor is
not functioning properly due to excessive cache errors. Recommended Action: Replace
the processor. The processor is at physical location. WBEM EventID: 10400. WBEM
ProviderName: FPL_IndicationProvider.Warning14910
A measured voltage in the server has gone far outside the factory specified lower
voltage range. Probable Cause: The voltage in the server has gone outside the factory
set range. A bad component, blown fuse, poorly seated module, loose cable, or debris
could be responsible for this failure. Recommended Action: Check all boards, power
supplies, and modules that either supply or use this voltage rail. WBEM EventID:
113. WBEM ProviderName: SEL02_IndicationProvider.Error14918
Voltage sensor crossed lower non-recoverable threshold. Probable Cause: The voltage
in the server has gone far outside the factory set range and could damage system
components. A bad component, blown fuse, poorly seated module, loose cable, or
debris could be responsible for this failure. Recommended Action: Check all boards,
power supplies, and modules that either supply or use this voltage rail. WBEM
EventID: 114. WBEM ProviderName: SEL02_IndicationProvider.Error14919
A measured voltage in the server has gone outside the factory specified upper voltage
range. Probable Cause: The voltage in the server has gone outside the factory set
range. A bad component, blown fuse, poorly seated module, loose cable, or debris
could be responsible for this failure. Recommended Action: Check all boards, power
supplies, and modules that either supply or use this voltage rail. WBEM EventID:
115. WBEM ProviderName: SEL02_IndicationProvider.Warning14920
Voltage sensor crossed upper non-recoverable threshold. Probable Cause: The voltage
in the server has gone far outside the factory set range and could damage system
components. A bad component, blown fuse, poorly seated module, loose cable, or
debris could be responsible for this failure. Recommended Action: Check all boards,
power supplies, and modules that either supply or use this voltage rail. WBEM
EventID: 116. WBEM ProviderName: SEL02_IndicationProvider.Error14922
The server's built-in sensors have detected an open chassis door. Probable Cause:
The server has detect that the chassis door or other access panel is not securely closed.
Recommended Action: Close any open panels or chassis doors. WBEM EventID: 127.
WBEM ProviderName: SEL02_IndicationProvider.Warning14941
Hot Swap Cage: SCSI cable removed. Probable Cause: This alert indicates that a SCSI
cable, Jumper or Duplex Connector has either been disconnected or removed. This
may make some SCSI devices inaccessible. Recommended Action: Ensure that all
the required SCSI cables, jumpers or duplex connectors are correctly connected to
the cage, disks, and/or the controller. WBEM EventID: 174. WBEM ProviderName:
SEL02_IndicationProvider.Warning14971
Power Pod Voltage Fault. Probable Cause: The voltage in the server has gone outside
the factory set range. A bad component, blown fuse, poorly seated module, loose
cable, or debris could be responsible for this failure. Recommended Action: Check
all boards, power supplies, and modules that either supply or use this voltage rail.
WBEM EventID: 121. WBEM ProviderName: SEL02_IndicationProvider.Error15065
Machine Check Initiated. Probable Cause: A Machine Check Abort event means the
hardware detected a critical error. This event is generated whenever a system error
due to processor, firmware, hardware and operating system is encountered. MCA
events may be either recoverable or non-recoverable. If it is recoverable, the system
will attempt to recover from the error for the purpose of maintaining high availability.
An example of which is automatic disabling of a failing processor. For non-recoverable
errors, the system will either stop or reboot to prevent data corruption and unreliable
operation. Recommended Action: When this event is generated, it is highly advisable
to consult both the operating system and hardware event logs to find out if there are
other events that may help identify the cause of the MCA. If an MCA event occurs
that causes the system to reboot, the failing component may be automatically disabled
and the system continue to run but at a degraded performance level while awaiting
repair. Therefore, for an MCA event, HP recommends contacting HP Customer
Support to determine if a repair is needed. WBEM EventID: 173. WBEM
ProviderName: SEL02_IndicationProvider.Error15069
Platform Events 103