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

This is an internal SW error. See Cause/Action . Probable Cause: A CPU has tried

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 86 highlights

12163 Warning 12164 Error 12165 Warning 12168 Warning 12193 Error 12194 Error 12195 Error 12196 Error The operating system has recovered from a PCI error. Probable Cause: See log with keyword PCI_LBA_DEV_SPEC_1 for more information. WBEM EventID: 6912. WBEM ProviderName: FPL_IndicationProvider. The request to power on, either via MP user interface, power button, or other, was denied by the Enclosure Manager. Probable Cause: The enclosure may not have sufficient power for the new blade. Recommended Action: Make sure enclosure has the appropriate number and configuration of power supplies. Reduce power required by the blade (for instance, remove some memory or a CPU.) Or, if there are powered-on blades that are not in use, power them off. WBEM EventID: 6581. WBEM ProviderName: FPL_IndicationProvider. The blade has been forced to power-on, either via the MP user interface or the power button. The blade did not negotiate with the enclosure to insure that there was sufficient power for this action. Probable Cause: A forced power on occurred. Usually this is performed when a normal power on request is denied. The Onboard Administrator may now be running in a non-redundant or over-budget power configuration. Recommended Action: Make sure Onboard Administator has the appropriate number and configuration of power supplies. Reduce power required by the blade (for instance, remove some memory or a CPU.) Or, if there are powered-on blades that are not in use, power them off. WBEM EventID: 6582. WBEM ProviderName: FPL_IndicationProvider. The MP has repeatedly tried to communicate with the enclosure manager and has not received any response. Probable Cause: The MP has repeatedly requested communication with the Onboard Administrator and has not received a response. This may be because the EM has a fault condition, or is busy, being reset, or removed. Recommended Action: The communication loss may have been temporary and nothing needs to be done if the communication is now working. Check the Fault LED on the enclosure manager. Reset the enclosure manager. Reset the management processor. Replace the enclosure manager. WBEM EventID: 6583. WBEM ProviderName: FPL_IndicationProvider. This is an internal SW error. See Cause/Action . Probable Cause: A CPU has tried to acquired the same semaphore twice which resulted in a deadlock. This is an internal SFW error and is not recoverable. Recommended Action: Collect the entire FPL, SEL, console logs and forward them to the SFW team. Also note all activities around the time of this event. The entire logs must analyzed by the SFW team before further actions can be taken. The system must be cold reset to resume normal operation. WBEM EventID: 6693. WBEM ProviderName: FPL_IndicationProvider. This is an internal SW error. See Cause/Action. Probable Cause: A CPU has tried to acquired the same semaphore twice which resulted in a deadlock. This is an internal SFW error and is not recoverable. Recommended Action: Collect the entire FPL, SEL, console logs and forward them to the SFW team. Also note all activities around the time of this event. The entire logs must analyzed by the SFW team before further actions can be taken. The system must be cold reset to resume normal operation. WBEM EventID: 6694. WBEM ProviderName: FPL_IndicationProvider. This is an internal SW error. See Cause/Action. Probable Cause: A CPU has tried to acquired the same semaphore twice which resulted in a deadlock. This is an internal SFW error and is not recoverable. Recommended Action: Collect the entire FPL, SEL, console logs and forward them to the SFW team. Also note all activities around the time of this event. The entire logs must analyzed by the SFW team before further actions can be taken. The system must be cold reset to resume normal operation. WBEM EventID: 6695. WBEM ProviderName: FPL_IndicationProvider. This is an internal SW error. See Cause/Action. Probable Cause: A CPU has tried to acquired the same semaphore twice which resulted in a deadlock. This is an internal SFW error and is not recoverable. Recommended Action: Collect the entire FPL, SEL, console logs and forward them to the SFW team. Also note all activities around the time of this event. The entire logs must analyzed by the SFW team before further actions can be taken. The system must be cold reset to resume normal operation. WBEM EventID: 6696. WBEM ProviderName: FPL_IndicationProvider. 86 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
The operating system has recovered from a PCI error. Probable Cause: See log with
keyword PCI_LBA_DEV_SPEC_1 for more information. WBEM EventID: 6912. WBEM
ProviderName: FPL_IndicationProvider.
Warning
12163
The request to power on, either via MP user interface, power button, or other, was
denied by the Enclosure Manager. Probable Cause: The enclosure may not have
sufficient power for the new blade. Recommended Action: Make sure enclosure has
the appropriate number and configuration of power supplies. Reduce power required
by the blade (for instance, remove some memory or a CPU.) Or, if there are
powered-on blades that are not in use, power them off. WBEM EventID: 6581. WBEM
ProviderName: FPL_IndicationProvider.
Error
12164
The blade has been forced to power-on, either via the MP user interface or the power
button. The blade did not negotiate with the enclosure to insure that there was
sufficient power for this action. Probable Cause: A forced power on occurred. Usually
this is performed when a normal power on request is denied. The Onboard
Administrator may now be running in a non-redundant or over-budget power
configuration. Recommended Action: Make sure Onboard Administator has the
appropriate number and configuration of power supplies. Reduce power required
by the blade (for instance, remove some memory or a CPU.) Or, if there are
powered-on blades that are not in use, power them off. WBEM EventID: 6582. WBEM
ProviderName: FPL_IndicationProvider.
Warning
12165
The MP has repeatedly tried to communicate with the enclosure manager and has
not received any response. Probable Cause: The MP has repeatedly requested
communication with the Onboard Administrator and has not received a response.
This may be because the EM has a fault condition, or is busy, being reset, or removed.
Recommended Action: The communication loss may have been temporary and
nothing needs to be done if the communication is now working. Check the Fault LED
on the enclosure manager. Reset the enclosure manager. Reset the management
processor. Replace the enclosure manager. WBEM EventID: 6583. WBEM
ProviderName: FPL_IndicationProvider.
Warning
12168
This is an internal SW error. See Cause/Action . Probable Cause: A CPU has tried to
acquired the same semaphore twice which resulted in a deadlock. This is an internal
SFW error and is not recoverable. Recommended Action: Collect the entire FPL, SEL,
console logs and forward them to the SFW team. Also note all activities around the
time of this event. The entire logs must analyzed by the SFW team before further
actions can be taken. The system must be cold reset to resume normal operation.
WBEM EventID: 6693. WBEM ProviderName: FPL_IndicationProvider.
Error
12193
This is an internal SW error. See Cause/Action. Probable Cause: A CPU has tried to
acquired the same semaphore twice which resulted in a deadlock. This is an internal
SFW error and is not recoverable. Recommended Action: Collect the entire FPL, SEL,
console logs and forward them to the SFW team. Also note all activities around the
time of this event. The entire logs must analyzed by the SFW team before further
actions can be taken. The system must be cold reset to resume normal operation.
WBEM EventID: 6694. WBEM ProviderName: FPL_IndicationProvider.
Error
12194
This is an internal SW error. See Cause/Action. Probable Cause: A CPU has tried to
acquired the same semaphore twice which resulted in a deadlock. This is an internal
SFW error and is not recoverable. Recommended Action: Collect the entire FPL, SEL,
console logs and forward them to the SFW team. Also note all activities around the
time of this event. The entire logs must analyzed by the SFW team before further
actions can be taken. The system must be cold reset to resume normal operation.
WBEM EventID: 6695. WBEM ProviderName: FPL_IndicationProvider.
Error
12195
This is an internal SW error. See Cause/Action. Probable Cause: A CPU has tried to
acquired the same semaphore twice which resulted in a deadlock. This is an internal
SFW error and is not recoverable. Recommended Action: Collect the entire FPL, SEL,
console logs and forward them to the SFW team. Also note all activities around the
time of this event. The entire logs must analyzed by the SFW team before further
actions can be taken. The system must be cold reset to resume normal operation.
WBEM EventID: 6696. WBEM ProviderName: FPL_IndicationProvider.
Error
12196
86
WBEM Provider Event Tables