HP Integrity Superdome SX2000 Windows Integrity Management Agents Reference - Page 10

INIT, TOC, or RESET. SNMP Trap: SystemHW - 745 in HPIFP02TRAP.MIB.

Page 10 highlights

Event ID Event Severity Event Description 730 Error The BMC firmware did not detect the system firmware boot Probable Cause: Possible Causes: 1. Bad System Firmware image in ROM 2. Power not reaching processors 3. Processor is in reset or is not properly seated in system 4. An unsupported processor was inserted in system 5. Communication with BMC is impaired. Recommended Action: To correct the problem, try the following: 1. Validate that processors are supported in this system. 2. Verify that processors are seated properly in system. 3. Check if system has booted (only a communication problem. - future events will also be lost.) 4. Attempt a system reset, INIT, and/or A/C cycle to clear the problem. 5. Update system firmware again if necessary. SNMP Trap: HPBmcFirmware - 730 in HPIFP02TRAP.MIB. 731 Error A/C Power failed, disconnected, or out of range Probable Cause: The input power to the supply has failed or gone out of range. Or the input cord has been disconnected. Recommended Action: Check the power cord or source voltage. SNMP Trap: hpPowerSupply - 731 in HPIFP02TRAP.MIB. The power supply sensors detect a possible problem Probable Cause: The power supply fan(s) is slowing Recommended Action: Check power supply fan(s). SNMP 732 Warning Trap: RedundantPower - 732 in HPIFP02TRAP.MIB. Cooling unit warning Probable Cause: The Cooling Unit may be running properly now, but it was detected in a degraded state. It may need to be replaced in the future. Recommended Action: Continue to monitor unit and contact HP support to determine 733 Warning appropriate action. SNMP Trap: SystemHW - 733 in HPIFP02TRAP.MIB. 734 Error Cooling unit failure Probable Cause: A cooling unit has failed. Recommended Action: Replace the indicated cooling unit. SNMP Trap: SystemHW - 734 in HPIFP02TRAP.MIB. 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 735 Warning proper operation of the server. SNMP Trap: SystemHW - 735 in HPIFP02TRAP.MIB. 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. SNMP Trap: SystemHW - 736 in HPIFP02TRAP.MIB. 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. SNMP Trap: SystemHW - 737 in HPIFP02TRAP.MIB. 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. SNMP Trap: SystemHW - 738 in HPIFP02TRAP.MIB. 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. SNMP Trap: SystemHW - 739 in HPIFP02TRAP.MIB. 740 Error Missing Entity Probable Cause: A required device was not detected. Recommended Action: Install missing, required device. SNMP Trap: SystemHW - 740 in HPIFP02TRAP.MIB. 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. SNMP 744 Warning Trap: SystemHW - 744 in HPIFP02TRAP.MIB. 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. SNMP Trap: SystemHW - 745 in HPIFP02TRAP.MIB. 10 Management Agents 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
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127

Event Description
Event Severity
Event ID
The BMC firmware did not detect the system firmware boot Probable Cause: Possible
Causes: 1. Bad System Firmware image in ROM 2. Power not reaching processors 3.
Processor is in reset or is not properly seated in system 4. An unsupported processor
was inserted in system 5. Communication with BMC is impaired. Recommended
Action: To correct the problem, try the following: 1. Validate that processors are
supported in this system. 2. Verify that processors are seated properly in system. 3.
Check if system has booted (only a communication problem. - future events will also
be lost.) 4. Attempt a system reset, INIT, and/or A/C cycle to clear the problem. 5.
Update system firmware again if necessary. SNMP Trap: HPBmcFirmware - 730 in
HPIFP02TRAP.MIB.
Error
730
A/C Power failed, disconnected, or out of range Probable Cause: The input power
to the supply has failed or gone out of range. Or the input cord has been disconnected.
Recommended Action: Check the power cord or source voltage. SNMP Trap:
hpPowerSupply - 731 in HPIFP02TRAP.MIB.
Error
731
The power supply sensors detect a possible problem Probable Cause: The power
supply fan(s) is slowing Recommended Action: Check power supply fan(s). SNMP
Trap: RedundantPower - 732 in HPIFP02TRAP.MIB.
Warning
732
Cooling unit warning Probable Cause: The Cooling Unit may be running properly
now, but it was detected in a degraded state. It may need to be replaced in the future.
Recommended Action: Continue to monitor unit and contact HP support to determine
appropriate action. SNMP Trap: SystemHW - 733 in HPIFP02TRAP.MIB.
Warning
733
Cooling unit failure Probable Cause: A cooling unit has failed. Recommended Action:
Replace the indicated cooling unit. SNMP Trap: SystemHW - 734 in
HPIFP02TRAP.MIB.
Error
734
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. SNMP Trap: SystemHW - 735 in HPIFP02TRAP.MIB.
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. SNMP
Trap: SystemHW - 736 in HPIFP02TRAP.MIB.
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. SNMP
Trap: SystemHW - 737 in HPIFP02TRAP.MIB.
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. SNMP
Trap: SystemHW - 738 in HPIFP02TRAP.MIB.
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.
SNMP Trap: SystemHW - 739 in HPIFP02TRAP.MIB.
Error
739
Missing Entity Probable Cause: A required device was not detected. Recommended
Action: Install missing, required device. SNMP Trap: SystemHW - 740 in
HPIFP02TRAP.MIB.
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. SNMP
Trap: SystemHW - 744 in HPIFP02TRAP.MIB.
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. SNMP Trap: SystemHW - 745 in HPIFP02TRAP.MIB.
Error
745
10
Management Agents Event Tables