KBI 311572 SNMP Get Request Failed. Error: noSuchName 2

Version

Argent for SNMP – All Versions

Date

Thursday, 7 September 2017

Summary

When creating SNMP Rules within Argent for SNMP an OID may get a SNMP variable type COUNTER, but some OID get COUNTER64 (64bit version of the COUNTER 32bit) and cause a return error,

“SNMP Get Request failed on OID ‘1.3.6.1.2.1.31.1.1.1.10.1’. Error: noSuchName (2)”

when using SNMP Protocol version SNMPv1

SNMPv1 does not support 64-bit counters

The issue has been addressed in Argent Advanced Technology 5.1A-1707-D

Technical Background

The SNMP Protocol SNMPv1 is very old, designed when network card speeds were 10MB

As time went on and network card speeds increased, 100MB, 1,000MB etc. a new protocol specification was implemented RFC2233 (SNMPv2), this now supported SNMP variable type COUNTER 64bit to support high capacity interfaces

For example, a 10 Mbps stream of back-to-back, full-size packets causes ifInOctets (COUNTER 32bit) to wrap in just over 57 minutes

At 100 Mbps, the minimum wrap time is 5.7 minutes

For more information see

SNMP Counters: Frequently Asked Questions

https://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-protocol-snmp/26007-faq-snmpcounter.html

Resolution

Change the Argent for SNMP – Node Properties – SNMP Protocol: SNMPv2c

In future versions of Argent for SNMP when a Rule is gets a SNMP variable type COUNTER64 and fails a warning will be given in the logs stating change to protocol SNMPv2c