You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When resolving a numeric OID to a name, a search of loaded MIBs is performed, in the reverse order in which MIBs have been loaded. This works, but requires the load order to be carefully considered by the tnm4j user.
A nice improvement would be to search all loaded MIBs and return the object name that matches with the smallest suffix of remaining unresolved OID string. If all needed MIBs are loaded, the unresolved part will always be the instance sub-identifier (assuming the OID is an object instance identifier).
For example, if SNMPv2-MIB is loaded and RFC1155-SMI is loaded, in the current implementation an OID-to-name lookup for 1.3.6.1.6.3.1.1.4.1.0 could return two possible values, depending on the order in which the Mib instance is loaded:
snmpTrapOID.0
internet.6.3.1.1.4.1.0
In this case result 1 is better, because the suffix remaining after the name is shorter than in result 2; it is a better match, and less likely to surprise tnm4j users.
The text was updated successfully, but these errors were encountered:
When resolving a numeric OID to a name, a search of loaded MIBs is performed, in the reverse order in which MIBs have been loaded. This works, but requires the load order to be carefully considered by the tnm4j user.
A nice improvement would be to search all loaded MIBs and return the object name that matches with the smallest suffix of remaining unresolved OID string. If all needed MIBs are loaded, the unresolved part will always be the instance sub-identifier (assuming the OID is an object instance identifier).
For example, if SNMPv2-MIB is loaded and RFC1155-SMI is loaded, in the current implementation an OID-to-name lookup for 1.3.6.1.6.3.1.1.4.1.0 could return two possible values, depending on the order in which the
Mib
instance is loaded:In this case result 1 is better, because the suffix remaining after the name is shorter than in result 2; it is a better match, and less likely to surprise tnm4j users.
The text was updated successfully, but these errors were encountered: