SNMPv2 trap-group category migration to SNMPv3

SNMPv2 trap-group category translation to SNMPv3 OIDs. Below is the snippet of the SNMPv2 config for reference:

root@router# show snmp

community jtac;

trap-group TEST {

  categories {             

    authentication;

    chassis;

    link;

    remote-operations;

    routing;

    startup;

    rmon-alarm;

    configuration;

  }

  targets {

    1.1.1.1;

  }

The standard Junos OS SNMP OIDs hold good for SNMPv3. However, there is no one-to-one translation of Category to OID.

For instance:

The chassis category is divided into jnxChassisTraps [1.3.6.1.4.1.2636.4.1] and jnxChassisOKTraps [1.3.6.1.4.1.2636.4.2] & is a subtree of parent OID jnxTraps

The link category is divided into linkDown [1.3.6.1.6.3.1.1.5.3] and linkup [1.3.6.1.6.3.1.1.5.4] OIDs, and is a subtree of parent OID snmpTraps & so on….

Check out the below table for Category to OID mapping. Refer to the SNMP Traps Supported by Junos OS for individual trap details: 

Ways to Implement:

1. Create a notify-filter/view with “oid .1 include” [a root MIB] to poll all available OIDs and filter out unwanted OIDs with the exclude command
2. Represent the subtree of the MIB object hierarchy either by a sequence of dotted integers or by its subtree name
3. Use the wildcard character asterisk in the object identifier (OID) to specify object identifiers that match a particular pattern

Check out SNMPv3 traps for more info and SNMP MIB Explorer for MIB OIDs hierarchy.