Dave, I am using 5.3.1, the implementation agent/mibgroup/notification-log-mib is provided in 5.3.1. Since transport is NULL, COLUMN_NLMLOGENGINETADDRESS and COLUMN_NLMLOGENGINETDOMAIN are NULL. However, COLUMN_NLMLOGNOTIFICATIONID is not NULL, but getnext would skip it because of the two NULL objects before it. This is the problem I am reporting.
The following is the "snmpgetnext 10.1 nlmLogEngineID.0.1" debug message, notice it jumped from base oid:NOTIFICATION-LOG-MIB::nlmLogTable to base oid:NOTIFICATION-LOG-MIB::nlmLogVariableTable helper:table:req: Got request for handler table: base oid:NOTIFICATION-LOG-MIB::nlmLogTable helper:table:col: have at least a column (4) helper:table: have 2 bytes of index helper:table: looking for 2 indexes helper:table: got 1 (incomplete=0) helper:table: got 1 (incomplete=0) helper:table:results: found 2 indexes helper:table:results: column: 4, indexes: 2 index: type=4(04), value="" index: type= 66(42), value=Gauge32: 1 helper:table:req: Got request for handler table: base oid:NOTIFICATION-LOG-MIB::nlmLogVariableTable helper:table: no column/index in request helper:table: looking for 3 indexes helper:table: oid indexes not complete: NOTIFICATION-LOG-MIB::nlmLogVariableTable helper:table:results: found 0 indexes helper:table:results: column: 2, indexes: 0 index: type=4(04), value="" index: type= 66(42), value=Gauge32: 0 index: type=66(42), value=Gauge32: 0 helper:table:req: Got request for handler table: base oid:NOTIFICATION-LOG-MIB::nlmLogTabl e helper:table:col: have at least a column (4) helper:table: have 2 bytes of index helper:table: looking for 2 indexes helper:table: got 1 (incomplete=0) helper:table: got 1 (incomplete=0) helper:table:results: found 2 indexes helper:table:results: column: 4, indexes: 2 index: type=4(04), value="" index: type= 66(42), value=Gauge32: 1 Thanks Emi -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Shield Sent: Thursday, September 06, 2007 4:01 AM To: Emi Yanagi Cc: [email protected] Subject: Re: When there is "no instance" object in a table, snmpgetnext skip the rest of the objects in the table and search for the next table On 05/09/07, Emi Yanagi <[EMAIL PROTECTED]> wrote: > I am reporting a bug in snmpgetnext. [snip] > Any idea how to improve snmpgetnext in this case? It's not a bug in snmpgetnext. It's an error in snmpd agent. How have you implemented this particular table? What version of the agent are you using? Dave ------------------------------------------------------------------------- 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
