SNMP Object ID Format for SNMPv1 Generic Traps

NNMi requires that SNMPv1 traps have object IDs. The object IDs are created according to the specifications in Request for Comments (RFC) document 2576: Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework.

When using SNMPv1 format, you can specify either generic or vendor specific traps. SNMPv1 generic traps are standard traps that are commonly used across vendors. The SNMPv1 enterprise specific traps are those traps that are generated by a particular vendor's device. The vendor is also known as the enterprise. Both include a vendor name as part of the set of information stored with each trap.

Note  

  • The value you enter for an SNMP Object ID (OID) must be unique.
  • When checking whether an SNMP Trap Incident Configuration exists, NNMi’s TrapFilter uses only implicit matching when checking generic SNMPv1 traps OIDs. See About the Trap Service Stages for more information about TrapFilter.
  • The wildcard character is not valid for an SNMPv1 generic trap because these traps do not begin with .1.3.6.1.4.

The six SNMPv1 generic traps have the following SNMP object identifiers that are recognized by SNMPv2c:

1.3.6.1.6.3.1.1.5.1 (coldStart)

1.3.6.1.6.3.1.1.5.2 (warmStart)

1.3.6.1.6.3.1.1.5.3 (linkDown)

1.3.6.1.6.3.1.1.5.4 (linkUp)

1.3.6.1.6.3.1.1.5.5 (authenticationFailure)

1.3.6.1.6.3.1.1.5.6 (egpNeighborLoss)

To configure an SNMP object identifier (SNMP OID) for a generic SNMPv1 trap, specify the SNMP object ID as described in RFC 2576. You also need to include the object identifier for the vendor name (<VendorEnterprise>) as shown below:

<SNMPv2c generic trap OID>.<VendorEnterprise>

The <vendorEnterprise> is the object identifier for the vendor that is included with the varbind trap information.

For example, the SNMP object identifier for Cisco warmStart trap would be:

.1.3.6.1.6.3.1.1.5.2.1.3.6.1.4.1.9

Note Cisco's Vendor enterprise object identifier in this example is .1.3.6.1.4.1.9