SNMPWALK nets different result from SNMPGET

Friends,

Maybe I have a syntax or procedural problem here.. or maybe something else? I SNMPWALK starting with a specific OID. I find the OID I want to use so I use that with an SNMPGET and it comes up with a different result. For example:

> snmpwalk -v 3 -l authPriv -u SNMPUSERID -a SHA -A 'SNMPauthPass' -x AES -X 'SNMPprivPass' -O n 10.1.1.1 1.3.6.1.4.1.9.9.812 | grep "\.24 " .1.3.6.1.4.1.9.9.812.1.2.1.2.1025.24 = INTEGER: 2 .1.3.6.1.4.1.9.9.812.1.2.1.3.2025.24 = Gauge32: 5000 .1.3.6.1.4.1.9.9.812.1.2.1.4.3025.24 = Gauge32: 166585818 .1.3.6.1.4.1.9.9.812.1.2.1.5.4025.24 = Gauge32: 0 .1.3.6.1.4.1.9.9.812.1.2.1.6.5025.24 = Gauge32: 0 

I want to use .1.3.6.1.4.1.9.9.812.1.2.1.4.3025.24, which doing a walk shows a counter of 166585818. So then I GET that value:

> snmpget -v 3 -l authPriv -u SNMPUSERID -a SHA -A 'SNMPauthPass' -x AES -X 'SNMPprivPass' -O n 10.1.1.1 .1.3.6.1.4.1.9.9.812.1.2.1.4.3025.24 .1.3.6.1.4.1.9.9.812.1.2.1.4.3025.24 = Gauge32: 0 

This boggles me. If I run the walk again it shows the count again, so I know its not a number that resets upon reading. Also, it is a counter so it should increment and not ever reduce to zero unless it wraps at 32-bit.

Any idea why my SNMPWALK is different from my SNMPGET?

Device in question is a Cisco ASR 9000.

aTdHvAaNnKcSe!

​

EDIT: snmpwalk and snmpget are version 5.7.2