HP Integrity rx2800 HP Insight Management WBEM Provider Events Reference Guide - Page 14

Missing Entity. Probable Cause: A required device was not detected. Recommended

Get HP Integrity rx2800 - i2 PDF manuals and user guides View all HP Integrity rx2800 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 14 highlights

735 Warning 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. 736 Error Watchdog timer expired - hard reset. Probable Cause: Watchdog timer expired, and a hard reset of the system occurred. Recommended Action: Some process took longer than it should. Identify that process and contact the vendor of that application. WBEM EventID: 178. WBEM ProviderName: SEL02_IndicationProvider. 736 Error Watchdog timer expired - hard reset. Probable Cause: Watchdog timer expired, and a hard reset of the system occurred. Recommended Action: Some process took longer than it should. Identify that process and contact the vendor of that application. WBEM EventID: 178. WBEM ProviderName: SEL02_IndicationProvider. 737 Error Watchdog timer expired - power-off. Probable Cause: Watchdog timer expired, and the system was powered-off. Recommended Action: Some process took longer than it should. Identify that process and contact the vendor of that application. WBEM EventID: 179. WBEM ProviderName: SEL02_IndicationProvider. 737 Error Watchdog timer expired - power-off. Probable Cause: Watchdog timer expired, and the system was powered-off. Recommended Action: Some process took longer than it should. Identify that process and contact the vendor of that application. WBEM EventID: 179. WBEM ProviderName: SEL02_IndicationProvider. 738 Error Watchdog timer expired - power-cycle. Probable Cause: Watchdog timer expired, and the system was power-cycled. Recommended Action: Some process took longer than it should. Identify that process and contact the vendor of that application. WBEM EventID: 180. WBEM ProviderName: SEL02_IndicationProvider. 738 Error Watchdog timer expired - power-cycle. Probable Cause: Watchdog timer expired, and the system was power-cycled. Recommended Action: Some process took longer than it should. Identify that process and contact the vendor of that application. WBEM EventID: 180. WBEM ProviderName: SEL02_IndicationProvider. 739 Error Missing FRU device. Probable Cause: A required device was not detected. See the System Event Log (SEL). Recommended Action: Install missing, required device. WBEM EventID: 182. WBEM ProviderName: SEL02_IndicationProvider. 739 Error Missing FRU device. Probable Cause: A required device was not detected. See the System Event Log (SEL). Recommended Action: Install missing, required device. WBEM EventID: 182. WBEM ProviderName: SEL02_IndicationProvider. 740 Error Missing Entity. Probable Cause: A required device was not detected. Recommended Action: Install missing, required device. WBEM EventID: 183. WBEM ProviderName: SEL02_IndicationProvider. 740 Error Missing Entity. Probable Cause: A required device was not detected. Recommended Action: Install missing, required device. WBEM EventID: 183. WBEM ProviderName: SEL02_IndicationProvider. 744 Warning 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. 744 Warning 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. 745 Error 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. 14 WBEM Provider Event Tables

  • 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
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
Watchdog timer expired - hard reset. Probable Cause: Watchdog timer expired, and
a hard reset of the system occurred. Recommended Action: Some process took longer
than it should. Identify that process and contact the vendor of that application. WBEM
EventID: 178. WBEM ProviderName: SEL02_IndicationProvider.
Error
736
Watchdog timer expired - hard reset. Probable Cause: Watchdog timer expired, and
a hard reset of the system occurred. Recommended Action: Some process took longer
than it should. Identify that process and contact the vendor of that application. WBEM
EventID: 178. WBEM ProviderName: SEL02_IndicationProvider.
Error
736
Watchdog timer expired - power-off. Probable Cause: Watchdog timer expired, and
the system was powered-off. Recommended Action: Some process took longer than
it should. Identify that process and contact the vendor of that application. WBEM
EventID: 179. WBEM ProviderName: SEL02_IndicationProvider.
Error
737
Watchdog timer expired - power-off. Probable Cause: Watchdog timer expired, and
the system was powered-off. Recommended Action: Some process took longer than
it should. Identify that process and contact the vendor of that application. WBEM
EventID: 179. WBEM ProviderName: SEL02_IndicationProvider.
Error
737
Watchdog timer expired - power-cycle. Probable Cause: Watchdog timer expired,
and the system was power-cycled. Recommended Action: Some process took longer
than it should. Identify that process and contact the vendor of that application. WBEM
EventID: 180. WBEM ProviderName: SEL02_IndicationProvider.
Error
738
Watchdog timer expired - power-cycle. Probable Cause: Watchdog timer expired,
and the system was power-cycled. Recommended Action: Some process took longer
than it should. Identify that process and contact the vendor of that application. WBEM
EventID: 180. WBEM ProviderName: SEL02_IndicationProvider.
Error
738
Missing FRU device. Probable Cause: A required device was not detected. See the
System Event Log (SEL). Recommended Action: Install missing, required device.
WBEM EventID: 182. WBEM ProviderName: SEL02_IndicationProvider.
Error
739
Missing FRU device. Probable Cause: A required device was not detected. See the
System Event Log (SEL). Recommended Action: Install missing, required device.
WBEM EventID: 182. WBEM ProviderName: SEL02_IndicationProvider.
Error
739
Missing Entity. Probable Cause: A required device was not detected. Recommended
Action: Install missing, required device. WBEM EventID: 183. WBEM ProviderName:
SEL02_IndicationProvider.
Error
740
Missing Entity. Probable Cause: A required device was not detected. Recommended
Action: Install missing, required device. WBEM EventID: 183. WBEM ProviderName:
SEL02_IndicationProvider.
Error
740
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
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
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
14
WBEM Provider Event Tables