HP XP Racks - Manual (Page 13)

3 SNMP supported MIBs
This topic describes the standard and extension MIB specifications, the SNMP GUI, and trap
configuration.
Trap configuration
Failure report trap
An extension trap protocol data unit (PDU) includes the product number of the device that
experienced the failure, the device nickname, and a failure reference code. If you obtain the
information with GetRequest command, access the MIB by using the product number of the
device as an index. The following table shows the failure report trap.
Table 6 Failure report trap
Description Type Object identifier Name
The product number of the
device that experienced
the failure. INTEGER .1.3.6.1.4.1.116.5.11.4.2.1 eventTrapSerialNumber
The device nickname. DisplayString .1.3.6.1.4.1.116.5.11.4.2.2 eventTrapNickname
The failure reference DisplayString .1.3.6.1.4.1.116.5.11.4.2.3 eventTrapREFCODE
The area where the failure
occurred.* OBJECT IDENTIFIER .1.3.6.1.4.1.116.5.11.4.2.4 eventTrapPartsID
Failure occurrence date. DisplayString .1.3.6.1.4.1.116.5.11.4.2.5 eventTrapDate
Failure occurrence time. DisplayString .1.3.6.1.4.1.116.5.11.4.2.6 eventTrapTime
Detailed information of a
failure. DisplayString .1.3.6.1.4.1.116.5.11.4.2.7 eventTrapDescription
*The object identifier for a failure in a storage system processor would be
.1.3.6.1.4.1.116.5.11.4.1.1.6.1.2.
Supported traps
The following table lists the supported extension trap types.
Table 7 Extension trap types
Description Trap Specific Trap Code
All operations in a storage system stopped. RaidEventUserAcute 1
Operation in a component where a failure occurred stopped. RaidEventUserSerious 2
Partial failure. RaidEventUserModerate 3
Minor failure. RaidEventUserService 4
Standard MIB specifications
Supported MIBs
The following table lists the supported MIBs. If you send a GET request for an object (MIB) that is
not supported, you will receive NoSuchName as a GET RESPONSE.
Trap configuration 13