Dave,
I'm not sure why you think that 1.3.6.1.2.1.1.2.0 is not supported. This is SNMPv2-MIB::sysObjectID.0 which is a standard part of the agent in all but the most unusual configurations.
Indeed, my configuration is an unusual one in which this OID is not supported. I was just wondering whether these two replies match, when requesting the same OID.
SNMP v1 reply
-------------
UDP
Simple Network Management Protocol
version:1
community:public
PDU type:RESPONSE
Request Id:0x8
Error Status: NO ERROR
Error Index:1
Object Identifier 1:.1.3.6.1.2.1.1.2.0(SNMPv2-MIB::sysObjectID.0)
value:NULL
SNMP v2c reply
-------------
UDP
Simple Network Management Protocol
version:2c
community:public
PDU type:RESPONSE
Request Id:0x45e7
Error Status: NO ERROR
Error Index:0
Object Identifier 1:.1.3.6.1.2.1.1.2.0(SNMPv2-MIB::sysObjectID.0)
value:NOSUCHOBJECT: no such object
I suggest you upgrade and try again.Sure enough, I'm in the process of upgrading to 5.1.2.
Thanks,
Haris
----------------------------------------------------------------------------
I'm using the net-snmp 5.0.2 for my agent implementation.
Please note that the 5.0.2 release was a fairly early version following
some extensive revisions to the agent internal implementation. There
have been a significant number of improvements since, and you are
strongly advised to upgrade - either to the latest in the 5.0.x line
(5.0.9), or the most recent 5.1.2 release.
But my agent retuns "noError" for errorStatus, and 1 for the errorIndex, and the value is NULL, when requesting for 1.3.6.1.2.1.1.2.0 (which ofcourse is not supported by the agent). See the dump for details.
I'm not sure why you think that 1.3.6.1.2.1.1.2.0 is not supported.
This is SNMPv2-MIB::sysObjectID.0 which is a standard part of the agent
in all but the most unusual configurations.
The agent behaves perfectly for snmpv2 though, with errorStatus=="noError", and the value=="noSuchName".
I do hope not.
With SNMPv2, the agent should be returning either 'noSuchInstance' or
'noSuchObject' exceptions. The error 'noSuchName' is not valid in SNMPv2
requests (i.e. SNMPv2c or SNMPv3).
And it's not an exception either, so should be reported as the errorStatus
rather than as a value.
I've just checked with the current 5.0.x agent, and it seems to work
as expected. I suggest you upgrade and try again.
Dave
PS: Please only send one copy of a query - sending it twice is unnecessary
------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ 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
