SNMP Enterprise Specific Trap (.11020)

Event ID 1182 Foundation Agent: A Change in the health status of the server has occurred.

cpqHoMibHealthStatusArrayChangeTrap – 11020 in CPQHOST.MIB

RESOLUTION

Multiple event ID 1182 messages do not affect the operation or functionality of the server and can be safely ignored.

A future release of the HP Insight Management Agents will prevent the same messages from being logged multiple times. Although it is unlikely, if the messages cause the Windows Event Log to fill up, the HP Insight Management Agents can be downgraded from version 9.10 to version 9.0 until the updated/future Insight Management Agents are released.

This advisory will be updated when additional information becomes available.

Source

SNMP Enterprise Specific Trap (.3038)

NT Event ID: 1204 (Hex)0x843504b4 (cpqstmsg.dll)
Log Severity: Warning (2)
Event Title: Drive Array Accelerator Status Change.
Log Message: The array accelerator board attached to the array controller in %4 has a new status of %2.
SNMP Trap: cpqDa6AccelStatusChange – 3038 in CPQIDA.MIB
Symptom: Accelerator Board Status Change. This trap indicates that the agent has detected a change in the status of an array accelerator cache board. The current status is represented by the variable cpqDaAccelStatus.
User Action: If the accelerator board status is permDisabled(5), you may need to replace the accelerator board.
Supporting SNMP Trap Data:
• sysName
• cpqHoTrapFlags
• cpqDaCntlrHwLocation
• cpqDaCntlrModel
• cpqDaAccelCntlrIndex
• cpqDaAccelSerialNumber
• cpqDaAccelTotalMemory
• cpqDaAccelStatus
• cpqDaAccelErrCode
Supporting SNMP Trap Description: “Status is now [cpqDaAccelStatus].”

This trap may be accompanied by trap 3040:

Event ID 1206
Drive Array Accelerator Battery Failed. The array accelerator board attached to the array controller in Slot 3 is reporting a battery failure.
[SNMP TRAP: 3040 in CPQIDA.MIB]

SNMP Enterprise Specific Trap (.18013)

NT Event ID: 1292 (Hex)0x4435050C (cpqnimsg.dll)
Log Severity: Information (1)
Log Message: Redundancy has been increased by the NIC in slot %1, port %2. Number of functional NICs in the team: %3.
SNMP Trap: cpqNic3RedundancyIncreased – 18013 in CPQNIC.MIB
Symptom: This trap is sent any time a previously failed physical adapter in a connected logical adapter group returns to the OK condition. This trap is not sent when a logical adapter group has connectivity restored from a Failed condition. The cpqNicConnectivityRestored trap is sent instead. This can be caused by replacing of a faulty cable or connecting a cable that was disconnected.
User Action: None required.

Supporting SNMP Trap Data:
• sysName
• cpqHoTrapFlags
• cpqNicIfPhysAdapterSlot
• cpqNicIfPhysAdapterPort
• cpqSiServerSystemId
• cpqNicIfPhysAdapterStatus
• cpqSePciSlotBoardName
• cpqNicIfPhysAdapterPartNumber
• ipAdEntAddr
• cpqNicIfLogMapIPV6Address
• cpqNicIfLogMapAdapterOKCount
Supporting SNMP Trap Description: “Redundancy increased by adapter in slot [cpqNicIfPhysAdapterSlot], port [cpqNicIfPhysAdapterPort].”

Reference

Enterprise Specific Trap (.9001) Uptime: x days, [Time], .iso.3.6.1.2.1.1.5.0 = STRING: “[Server Name]”, .iso.3.6.1.4.1.232.11.2.11.1 = INTEGER: 0

This SNMP trap was being triggered every now and again. Like many SNMP messages, there’s not always anything useful within them to help explain what actually happened.
Here’s an example:
Description: [IP Address]: Enterprise Specific Trap (.9001) Uptime: x days, [Time], .iso.3.6.1.2.1.1.5.0 = STRING: “[Server Name]”, .iso.3.6.1.4.1.232.11.2.11.1 = INTEGER: 0

In my case, a scheduled reboot caused the iLO on an HP BL460c Blade to trigger the SNMP alarm, which HP call “Server Reset Detected”.

Source