SNMP Traps
When there is a change or failure in an individual component on the DXi, a service ticket is created, which in turn generates an SNMP trap. This section presents the service ticket events that generate traps and the DXi components against which the traps are reported.
The default SNMP trap severity (Trap_Level) can be modified by the (see SNMP Trap Severity).
Service Tickets
Service tickets are always reported against the violating field replaceable units (FRUs). The reporting FRU can be either of the following:
- The violating FRU itself.
- A peer FRU that has determined the violating FRU is in a bad state.
Service tickets can report both the violating FRU and the parent of the violating FRU. For more information about service tickets, see the Service Tickets topic in your DXi Online Help or DXi User's Guide.
DXi SNMP Traps by Component
Click the links to review DXi SNMP traps by component.
Trap Message Formats
DXi-issued SNMP v2c traps are reported in a format that contains the following 4 PDU variable bindings fields (object ID (OID) / value pairs of data).
Uptime
|
OID |
|
|
Value |
DXi system uptime |
Trap Type
|
OID |
snmpTrapOID = 1.3.6.1.6.3.1.1.4.1.0 |
|
Value |
One of the following Quantum trap OIDs:
|
IP Address
|
OID |
snmpTrapAddress = 1.3.6.1.6.3.18.1.3.0 |
|
Value |
DXi Mgmt IP address |
Trap Description
|
OID |
Quantum Trap Type OID from above. |
|
Value |
OctetString: |
