Re: snmp unknown object identifier

In message <vp1243$fou$1@tncsrv09.home.tnetconsulting.net>, Grant Taylor <gtaylor@tnetconsulting.net> writes

On 2/17/25 11:16, Adrian wrote:

Changing ifInOctets to something else (e.g. Time ticks) gives me the same result, but using the long number (1.3.6.1.2.1.1.3.0) works.

>
According to the OID repository, 1.3.6.1.2.1.1.3.0 is sysUpTimeInstance and doesn't seem to have anything to do with -- what I assume to be -- interface inbound octets.
>
Link - OID repository - 1.3.6.1.2.1.1.3.0 = {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) system(1) sysUpTime(3) sysUpTimeInstance(0)}
- https://oid-base.com/get/1.3.6.1.2.1.1.3.0
>
It seems as if ifInOctets is 1.3.6.1.2.1.2.2.1.10
>
Link - OID repository - 1.3.6.1.2.1.2.2.1.10 = {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) interfaces(2) ifTable(2) ifEntry(1) ifInOctets(10)}
- https://oid-base.com/get/1.3.6.1.2.1.2.2.1.10
>

As I'm not sure what ifInOctets translates to, I can't readily use the number instead.

>
Are you looking for the system's up time or the number of octets received on interfaces?
>

Thanks Grant.
I'm after both. Uptime on a daily basis, and octets in (and out, ideally on both Ethernet and WiFi) on a more regular basis.
The Uptime is easy to identify when doing a snmpwalk (so I can get the id number), but there are a number of lines that come back that could be the dataflow values.
I've just tried using snmpget on 1.3.6.1.2.1.2.2.1.10 to get ifInOctets, and I get :
No such Object available in this agent at this OID
Looking at that with snmpwalk, there are 10 sub-values (1.3.6.1.2.1.2.2.1.10.x), of which 6 are zero, and the other 4 (x = 1, 6, 7, 8) have differing values.  The first seems to be constant at 480.
Adrian
--
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.