HP Integrity Superdome SX2000 HP Insight Manager WBEM Provider Events Referenc - Page 11

was a Diagnostic Interrupt initiated by IPMI command. Either the Transfer Of Control, INIT, TOC

Page 11 highlights

Event ID Event Severity 518 Error 700 Error 744 Warning 735 Warning 729 Error 745 Error 746 Error 751 Warning 747 Warning Event Description Uncorrectable multi-bit ECC error has occurred. Probable Cause: There has been an ECC double-bit error in one of the server's ECC memory modules. When an ECC double-bit memory error is detected, the system generates a Non-Maskable Interrupt that halts the system to prevent errors from propagating to other subsystems. Data being written or transmitted at the time may have been lost. Recommended Action: Make a note of the failed memory bank/board number and slot number, contact HP support to replace the failed module. WBEM EventID: 159. WBEM ProviderName: SEL02_IndicationProvider. Generic trap for Critical or Fatal type E0 event from system firmware. Probable Cause: This event is generated when a critical or fatal event has occurred as reported by system firmware. The server is not operational and is in a state where it cannot provide more details about the failure. To obtain more information, log into the server's Management Processor Card and look at the event log for more details on the failure. Recommended Action: Contact HP Support for best course of action. HP may require a reboot, reconfiguration, or reflash of firmware. WBEM EventID: 162. WBEM ProviderName: SEL02_IndicationProvider. System event log almost full. Probable Cause: The System Event Log is almost full. Recommended Action: Review the log for any important events, then clear it. WBEM EventID: 163. WBEM ProviderName: SEL02_IndicationProvider. BMC entering special mode. Probable Cause: BMC entering special mode. The system is not operating in a normal configuration. Some protection features may be disabled in this mode. Recommended Action: The Special Mode must be exited to ensure proper operation of the server. WBEM EventID: 166. WBEM ProviderName: SEL02_IndicationProvider. System shut-down or reset caused by sensor reading. Probable Cause: A sensor reading in the system was determined to be non-recoverable and the system was shut down or reset. Recommended Action: Read the system logs to find which sensor was out of range. WBEM EventID: 167. WBEM ProviderName: SEL02_IndicationProvider. TOC interrupt (crash dump). Probable Cause: The critical interrupt sensor has detected that there was a Diagnostic Interrupt initiated by IPMI command. Either the Transfer Of Control (TOC) button was pressed or the interrupt was initiated remotely. The system will reboot after the interrupt processing is finished. Recommended Action: If this is unexpected behavior, then check logs for events that would have caused an INIT, TOC, or RESET. WBEM EventID: 169. WBEM ProviderName: SEL02_IndicationProvider. INIT Initiated. Probable Cause: The critical interrupt sensor has detected that there was a Diagnostic Interrupt initiated by IPMI command. Either the Transfer Of Control (TOC) button was pressed or the interrupt was initiated remotely. The system will reboot after the interrupt processing is finished. Recommended Action: If this is unexpected behavior, then check logs for events that would have caused an INIT, TOC, or RESET. WBEM EventID: 170. WBEM ProviderName: SEL02_IndicationProvider. PCI parity error detected. Probable Cause: An I/O device (or host bridge) detected a bus parity error, OR An I/O device (or host bridge) mastered a bus transaction and received a parity error response from the target. Recommended Action: For an I/O bus parity error, consult the error logs for additional information. Determine and replace the failed I/O device. For an I/O host bridge failure, contact your HP representative to check the I/O host bridge. WBEM EventID: 171. WBEM ProviderName: SEL02_IndicationProvider. PCI system error detected. Probable Cause: An I/O device (or host bridge) detected an internal error. OR An I/O device (or host bridge) detected a bus error. Recommended Action: For an I/O device failure, consult the error logs for additional information. Determine and replace the failed I/O device. For an I/O host bridge failure, contact your HP representative to check the I/O host bridge. WBEM EventID: 172. WBEM ProviderName: SEL02_IndicationProvider. Platform Events 11

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112

Event Description
Event
Severity
Event ID
Uncorrectable multi-bit ECC error has occurred. Probable Cause: There has been an
ECC double-bit error in one of the server's ECC memory modules. When an ECC
double-bit memory error is detected, the system generates a Non-Maskable Interrupt
that halts the system to prevent errors from propagating to other subsystems. Data
being written or transmitted at the time may have been lost. Recommended Action:
Make a note of the failed memory bank/board number and slot number, contact HP
support to replace the failed module. WBEM EventID: 159. WBEM ProviderName:
SEL02_IndicationProvider.
Error
518
Generic trap for Critical or Fatal type E0 event from system firmware. Probable Cause:
This event is generated when a critical or fatal event has occurred as reported by
system firmware. The server is not operational and is in a state where it cannot
provide more details about the failure. To obtain more information, log into the
server's Management Processor Card and look at the event log for more details on
the failure. Recommended Action: Contact HP Support for best course of action. HP
may require a reboot, reconfiguration, or reflash of firmware. WBEM EventID: 162.
WBEM ProviderName: SEL02_IndicationProvider.
Error
700
System event log almost full. Probable Cause: The System Event Log is almost full.
Recommended Action: Review the log for any important events, then clear it. WBEM
EventID: 163. WBEM ProviderName: SEL02_IndicationProvider.
Warning
744
BMC entering special mode. Probable Cause: BMC entering special mode. The system
is not operating in a normal configuration. Some protection features may be disabled
in this mode. Recommended Action: The Special Mode must be exited to ensure
proper operation of the server. WBEM EventID: 166. WBEM ProviderName:
SEL02_IndicationProvider.
Warning
735
System shut-down or reset caused by sensor reading. Probable Cause: A sensor
reading in the system was determined to be non-recoverable and the system was
shut down or reset. Recommended Action: Read the system logs to find which sensor
was out of range. WBEM EventID: 167. WBEM ProviderName:
SEL02_IndicationProvider.
Error
729
TOC interrupt (crash dump). Probable Cause: The critical interrupt sensor has detected
that there was a Diagnostic Interrupt initiated by IPMI command. Either the Transfer
Of Control (TOC) button was pressed or the interrupt was initiated remotely. The
system will reboot after the interrupt processing is finished. Recommended Action:
If this is unexpected behavior, then check logs for events that would have caused an
INIT, TOC, or RESET. WBEM EventID: 169. WBEM ProviderName:
SEL02_IndicationProvider.
Error
745
INIT Initiated. Probable Cause: The critical interrupt sensor has detected that there
was a Diagnostic Interrupt initiated by IPMI command. Either the Transfer Of Control
(TOC) button was pressed or the interrupt was initiated remotely. The system will
reboot after the interrupt processing is finished. Recommended Action: If this is
unexpected behavior, then check logs for events that would have caused an INIT,
TOC, or RESET. WBEM EventID: 170. WBEM ProviderName:
SEL02_IndicationProvider.
Error
746
PCI parity error detected. Probable Cause: An I/O device (or host bridge) detected a
bus parity error, OR An I/O device (or host bridge) mastered a bus transaction and
received a parity error response from the target. Recommended Action: For an I/O
bus parity error, consult the error logs for additional information. Determine and
replace the failed I/O device. For an I/O host bridge failure, contact your HP
representative to check the I/O host bridge. WBEM EventID: 171. WBEM
ProviderName: SEL02_IndicationProvider.
Warning
751
PCI system error detected. Probable Cause: An I/O device (or host bridge) detected
an internal error. OR An I/O device (or host bridge) detected a bus error.
Recommended Action: For an I/O device failure, consult the error logs for additional
information. Determine and replace the failed I/O device. For an I/O host bridge
failure, contact your HP representative to check the I/O host bridge. WBEM EventID:
172. WBEM ProviderName: SEL02_IndicationProvider.
Warning
747
Platform Events
11