Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

snmpget always returning 'Unknown Object Identifier"

Status
Not open for further replies.

EricFowler

Programmer
Jan 16, 2014
1
US
I am always getting Unknown OID when my client interrogates my server.

When I get on the server and interrogate localhost, I see a large and healthy looking list of OIDs 'n' stuff. The list *does* include the values I am seeking from the client.

I am a somewhat experienced Linux hand but an SNMP newbie. The SNMP client is a pretty minimal ucLinux embedded machine.

Here is some spew produced by my thrashing around:
~ # snmpget -v1 -cpublic -mALL 192.168.3.41 sysName.0
No log handling enabled - using stderr logging
sysName.0: Unknown Object Identifier (sysName.0)
~ # snmpget -mALL -v1 -cpublic 192.168.3.41 sysName.0
No log handling enabled - using stderr logging
sysName.0: Unknown Object Identifier (sysName.0)
~ # snmpget -mALL -v1 -cpublic 192.168.3.41 system
No log handling enabled - using stderr logging
system: Unknown Object Identifier (system)
~ # snmpget -v 1 -c public 192.168.3.41 system.sysUpTime.0
No log handling enabled - using stderr logging
system.sysUpTime.0: Unknown Object Identifier (system.sysUpTime.0)
~ # snmpget -v 1 -c public 192.168.3.41 sysUpTime.0
No log handling enabled - using stderr logging
sysUpTime.0: Unknown Object Identifier (sysUpTime.0)
~ # snmpget -m ALL -v 1 -c public 192.168.3.41 sysUpTime.0
No log handling enabled - using stderr logging
sysUpTime.0: Unknown Object Identifier (sysUpTime.0)
~ # snmpget -m ALL -v1 -c public 192.168.3.41 sysUpTime.0
No log handling enabled - using stderr logging
sysUpTime.0: Unknown Object Identifier (sysUpTime.0)
~ # snmpget -m ALL -v1 -c public 192.168.3.41 RFC1213-MIB:sysUpTime.0
No log handling enabled - using stderr logging
RFC1213-MIB:sysUpTime.0: Unknown Object Identifier (RFC1213-MIB:sysUpTime.0)
~ # snmpget -m ALL -v1 -c public 192.168.3.41 RFC1213-MIBx:sysUpTime.0
No log handling enabled - using stderr logging
RFC1213-MIBx:sysUpTime.0: Unknown Object Identifier (RFC1213-MIBx:sysUpTime.0)
~ # snmpget -m ALL -v1 -c public 192.168.3.41 RFC1213-MIB:sysUpTime.0
No log handling enabled - using stderr logging
RFC1213-MIB:sysUpTime.0: Unknown Object Identifier (RFC1213-MIB:sysUpTime.0)
~ # snmpget -m ALL -v1 -c public 192.168.3.41 RFC1213-MIB:sysUpTimeInstance.0
No log handling enabled - using stderr logging
RFC1213-MIB:sysUpTimeInstance.0: Unknown Object Identifier (RFC1213-MIB:sysUpTim eInstance.0)
~ # snmpget -m ALL -v1 -c public 192.168.3.41 SNMPv2-MIB::sysName.0
No log handling enabled - using stderr logging
SNMPv2-MIB::sysName.0: Unknown Object Identifier (SNMPv2-MIB::sysName.0)


On the host:
[eric@localhost linux-cortexm-1.12.0]$ snmpget -v1 -cpublic -mALL localhost sysName.0
SNMPv2-MIB::sysName.0 = STRING: localhost.localdomain
[eric@localhost linux-cortexm-1.12.0]$ snmpget -v1 -cpublic -mALL localhost sysUpTime.0
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (353814) 0:58:58.14

So that is OK. It also works using the IP addr, not localhost:

[eric@localhost linux-cortexm-1.12.0]$ snmpget -v1 -cpublic -mALL 192.168.3.41 sysUpTime.0
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (377014) 1:02:50.14



The machines can ping each other OK. All other internetty stuff is fine. They are on the same subnet and same router. Both machines can see the outside world, e.g. pinging google works.
Any clues appreciated.


Eric

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top