Hi Suresh and thanks for your help,

 

I tried doing exactly what you advised; however I only see the rest of
the system mibs - out of the 7, I see 6. I see them properly. I can
change them - everything works fine.

Only the sysUpTime is giving me trouble :-)

 

Any other thoughts?

 

Thanks in advance, 

 

-Tanya

 

 

From: [email protected]
[mailto:[email protected]] 
Sent: Wednesday, December 31, 2008 08:59
To: Tanya Brudner; [email protected]
Subject: RE: sysUpTime returns an error

 

Hi Tanya,

 

It looks like SNMPD is trying to return the value of "sysUpTimeInstance"
defined by DISMAN-EVENT-MIB. Can you please try giving the request on
sysUpTime defined by RFC1213-MIB.? For example, run the following
command.

 

export MIBDIRS=/usr/share/snmp/mibs

snmpwalk -v2c -c public localhost -m
/usr/share/snmp/mibs/RFC1213-MIB.txt system

 

Please make sure that the file "/usr/share/snmp/mibs/RFC1213-MIB.txt"
exists on your system.

 

Regards,

Suresh.

 

________________________________

From: Tanya Brudner [mailto:[email protected]] 
Sent: Wednesday, December 31, 2008 1:53 AM
To: [email protected]
Subject: sysUpTime returns an error

Hi and thanks for all your help,

 

I am new to SNMP, so I thank you for your patience :-)

 

I have a problem with Get-request on a single mib: SysUpTime. 

On a snmpget -v3 ..... system.sysUpTime.0, it returns
""DISMAN-EVENT-MIB::sysUpTimeInstance = No such Object available on this
agent at this OID"

 

The rest of the system subtree (and rest of the mibs, actually) return
the correct values. 

 

If I run snmptranslate -IR sysUpTime, I get the correct answer.

 

What is this "confusion" and what is it caused by? 

 

Thanks in advance, and Happy New Year,

 

-Tanya

 

------------------------------------------------------------------------------
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to