Template:FAQ:Applications 19

This is due to the way that traps are converted between SNMPv1 and SNMPv2 formats. The algorithm used for converting from an SNMPv1 enterprise-specific trap number, to an SNMPv2 trap OID results in a penultimate '0' subidentifier, before the trap number itself. The definition of the trap objects in the UCD-SNMP-MIB file does not include this subidentifier.

In due course, the intention is to define a new set of MIB objects, under the 'net-snmp' enterprise tree. This will include new trap OIDs, which will be designed such that this problem does not arise in the future.