Management Agents Events Reference
Event DescriptionEvent SeverityEvent ID
The operating system has recovered from a PCI error. Probable Cause: If the data
word is not 0x0000000400000000, then the problem is most likely with the PCI card.
If the value of the data word is 0x0000000400000000, then check event log with
keyword PCI_ERROR_STATUS. If PCI_ERROR_STATUS > 1, then the problem is in
the connection between System Bus Adapter and Lower Bus Adapter. If
PCI_ERROR_STATUS = 1, then the problem is in the Lower Bus Adapter. SNMP
Trap: hpevtSysOSRecovFrmPCIErrL1 - 12161 in HPIFPTRAP.MIB.
Warning12161
The operating system has recovered from a PCI error. Probable Cause: See event
with keyword PCI_LBA_DEV_SPEC_1 SNMP Trap: hpevtSysOSRecovFrmPCIErrL2
- 12162 in HPIFPTRAP.MIB.
Warning12162
The operating system has recovered from a PCI error. Probable Cause: See log with
keyword PCI_LBA_DEV_SPEC_1 for more information. SNMP Trap:
hpevtSysOSRecovFrmPCIErrL5 - 12163 in HPIFPTRAP.MIB.
Warning12163
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. SNMP Trap:
hpevtReqPwrOnDenied - 12164 in HPIFPTRAP.MIB.
Error12164
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. SNMP Trap:
hpevtBladeFrcPWon - 12165 in HPIFPTRAP.MIB.
Warning12165
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 SNMP Trap:
hpevtMPNotRecvRespEnclMangr - 12168 in HPIFPTRAP.MIB.
Warning12168
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
SNMP Trap: hpevtIntrnlSwErr7193 - 12193 in HPIFPTRAP.MIB.
Error12193
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
SNMP Trap: hpevtIntrnlSwErr7194 - 12194 in HPIFPTRAP.MIB.
Error12194
98 Management Agents Event Tables