I am reporting a bug in snmpgetnext. Here is how to reproduce the
problem with nlmLogTable.
NlmLogEntry ::= SEQUENCE {
nlmLogIndex Unsigned32,
nlmLogTime TimeStamp,
nlmLogDateAndTime DateAndTime,
nlmLogEngineID SnmpEngineID,
nlmLogEngineTAddress TAddress,
nlmLogEngineTDomain TDomain,
nlmLogContextEngineID SnmpEngineID,
nlmLogContextName SnmpAdminString,
nlmLogNotificationID OBJECT IDENTIFIER
}
$ snmpget 10.1 nlmLogTime.0.3
NOTIFICATION-LOG-MIB::nlmLogTime."".3 = Timeticks: (15125) 0:02:31.25
$ snmpgetnext 10.1 nlmLogTime.0.3
NOTIFICATION-LOG-MIB::nlmLogDateAndTime."".3 = STRING:
2007-9-5,15:9:29.0,+0:0
$ snmpgetnext 10.1 nlmLogDateAndTime.0.3
NOTIFICATION-LOG-MIB::nlmLogEngineID."".3 = ""
$ snmpget 10.1 nlmLogEngineTAddress.0.3
NOTIFICATION-LOG-MIB::nlmLogEngineTAddress."".3 = No Such Instance
currently exists at this OID
$ snmpget 10.1 nlmLogNotificationID.0.3
NOTIFICATION-LOG-MIB::nlmLogNotificationID."".3 = OID: IF-MIB::linkDown
Now since nlmLogEngineTAddress has no instance, although the last object
nlmLogNotificationID in nlmLogTable exists, snmpgetnext of
nlmLogEngineID will return nlmLogVariableID of the next table
nlmLogVariableTable instead of nlmLogNotificationID in the current table
nlmLogTable.
$ snmpgetnext 10.1 nlmLogEngineID.0.3
NOTIFICATION-LOG-MIB::nlmLogVariableID."".3.1 = OID:
SNMPv2-MIB::sysUpTime.0
Any idea how to improve snmpgetnext in this case?
Emi Yanagi
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
