×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

snmpget always returning 'Unknown Object Identifier"

snmpget always returning 'Unknown Object Identifier"

snmpget always returning 'Unknown Object Identifier"

(OP)
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

Replies continue below

Recommended for you

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login


Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close