HP Integrity Superdome SX1000 HP Insight Manager WBEM Provider Events Referenc - Page 10

Causes: 1. Bad System Firmware image in ROM 2. Power not reaching processors 3

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

Page 10 highlights

Event ID Event Severity Event Description 726 Error Power failure in power supply. Probable Cause: Indicates a failure with the AC power source that is connected to one of the redundant power supply units. Recommended Action: Check the power cord or source voltage. WBEM EventID: 726. WBEM ProviderName: FPL_IndicationProvider02 728 Error Voltage reached critical level. 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: 728. WBEM ProviderName: FPL_IndicationProvider02 729 Error 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: 729. WBEM ProviderName: FPL_IndicationProvider02 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. WBEM EventID: 730. WBEM ProviderName: FPL_IndicationProvider02 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. WBEM EventID: 731. WBEM ProviderName: FPL_IndicationProvider02 The power supply sensors detect a possible problem. Probable Cause: The power supply fan(s) is slowing Recommended Action: Check power supply fan(s). WBEM 732 Warning EventID: 732. WBEM ProviderName: FPL_IndicationProvider02 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. WBEM EventID: 733. WBEM ProviderName: 733 Warning FPL_IndicationProvider02 734 Error Cooling unit failure. Probable Cause: A cooling unit has failed. Recommended Action: Replace the indicated cooling unit. WBEM EventID: 734. WBEM ProviderName: FPL_IndicationProvider02 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: 735. WBEM ProviderName: 735 Warning FPL_IndicationProvider02 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: 736. WBEM ProviderName: FPL_IndicationProvider02 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: 737. WBEM ProviderName: FPL_IndicationProvider02 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: 738. WBEM ProviderName: FPL_IndicationProvider02 10 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
Event Description
Event Severity
Event ID
Power failure in power supply. Probable Cause: Indicates a failure with the AC power
source that is connected to one of the redundant power supply units. Recommended
Action: Check the power cord or source voltage. WBEM EventID: 726. WBEM
ProviderName: FPL_IndicationProvider02
Error
726
Voltage reached critical level. 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: 728. WBEM ProviderName: FPL_IndicationProvider02
Error
728
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: 729. WBEM ProviderName:
FPL_IndicationProvider02
Error
729
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. WBEM EventID: 730. WBEM
ProviderName: FPL_IndicationProvider02
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. WBEM EventID:
731. WBEM ProviderName: FPL_IndicationProvider02
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). WBEM
EventID: 732. WBEM ProviderName: FPL_IndicationProvider02
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. WBEM EventID: 733. WBEM ProviderName:
FPL_IndicationProvider02
Warning
733
Cooling unit failure. Probable Cause: A cooling unit has failed. Recommended Action:
Replace the indicated cooling unit. WBEM EventID: 734. WBEM ProviderName:
FPL_IndicationProvider02
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. WBEM EventID: 735. WBEM ProviderName:
FPL_IndicationProvider02
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: 736. WBEM ProviderName: FPL_IndicationProvider02
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: 737. WBEM ProviderName: FPL_IndicationProvider02
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: 738. WBEM ProviderName: FPL_IndicationProvider02
Error
738
10
WBEM Provider Event Tables