HP Integrity rx8620 HP Insight Manager WBEM Provider Events Reference - Page 11

was a Diagnostic Interrupt initiated by IPMI command. Either the Transfer Of Control - reviews

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

Page 11 highlights

Event ID Event Severity Event Description 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: 739. WBEM ProviderName: FPL_IndicationProvider02 740 Error Missing Entity. Probable Cause: A required device was not detected. Recommended Action: Install missing, required device. WBEM EventID: 740. WBEM ProviderName: FPL_IndicationProvider02 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 744 Warning EventID: 744. WBEM ProviderName: FPL_IndicationProvider02 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: 745. WBEM ProviderName: FPL_IndicationProvider02 746 Error 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: 746. WBEM ProviderName: FPL_IndicationProvider02 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: 747 Warning 747. WBEM ProviderName: FPL_IndicationProvider02 748 Error OS run-time critical shutdown. Probable Cause: The OS caused the system to shut down. Recommended Action: Look at OS logs and crash data to determine why the system shut down. WBEM EventID: 748. WBEM ProviderName: FPL_IndicationProvider02 ACPI state S5 (soft-off, entered by override). Probable Cause: The system has been powered OFF with a hard power-down. Recommended Action: HP recommends that when you powered down the system you use the normal shutdown procedure to properly shut down the operating system. Otherwise, data-loss and/or hardware failure can occur. WBEM EventID: 749. WBEM ProviderName: 749 Warning FPL_IndicationProvider02 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: 751. WBEM 751 Warning ProviderName: FPL_IndicationProvider02 Temperature sensor crossed lower non-critical threshold. Probable Cause: The temperature inside the server has gone outside the factory specified range for normal operation. You should quit applications and power down the server to protect its hardware from damage. This event may indicate one of the following conditions: A failed fan, blocked air vents or poor ventilation around the server, open server chassis cover, or missing drive slot covers, high temperature in the room where the server resides, an unusually hot hardware component located near one of the server's temperature sensors. Recommended Action: Find cause of temperature anomaly and 752 Warning fix it. WBEM EventID: 752. WBEM ProviderName: FPL_IndicationProvider02 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
Event Description
Event Severity
Event ID
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: 739. WBEM ProviderName: FPL_IndicationProvider02
Error
739
Missing Entity. Probable Cause: A required device was not detected. Recommended
Action: Install missing, required device. WBEM EventID: 740. WBEM ProviderName:
FPL_IndicationProvider02
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: 744. WBEM ProviderName: FPL_IndicationProvider02
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: 745. WBEM ProviderName:
FPL_IndicationProvider02
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: 746. WBEM ProviderName:
FPL_IndicationProvider02
Error
746
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:
747. WBEM ProviderName: FPL_IndicationProvider02
Warning
747
OS run-time critical shutdown. Probable Cause: The OS caused the system to shut
down. Recommended Action: Look at OS logs and crash data to determine why the
system shut down. WBEM EventID: 748. WBEM ProviderName:
FPL_IndicationProvider02
Error
748
ACPI state S5 (soft-off, entered by override). Probable Cause: The system has been
powered OFF with a hard power-down. Recommended Action: HP recommends
that when you powered down the system you use the normal shutdown procedure
to properly shut down the operating system. Otherwise, data-loss and/or hardware
failure can occur. WBEM EventID: 749. WBEM ProviderName:
FPL_IndicationProvider02
Warning
749
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: 751. WBEM
ProviderName: FPL_IndicationProvider02
Warning
751
Temperature sensor crossed lower non-critical threshold. Probable Cause: The
temperature inside the server has gone outside the factory specified range for normal
operation. You should quit applications and power down the server to protect its
hardware from damage. This event may indicate one of the following conditions: A
failed fan, blocked air vents or poor ventilation around the server, open server chassis
cover, or missing drive slot covers, high temperature in the room where the server
resides, an unusually hot hardware component located near one of the server's
temperature sensors. Recommended Action: Find cause of temperature anomaly and
fix it. WBEM EventID: 752. WBEM ProviderName: FPL_IndicationProvider02
Warning
752
Platform Events
11