Dave, unfortunately I am running into this (or similar) problem again, and I have tracked into this a little deeper, and now I really think, that net-snmp is not behaving correctly.
I am seeing the NonIncreasing error set even in case NonIncreasing should not be set. When using the "bulkwalk" method on a v2 session object and using multiple OIDs to be walked, the NonIncreasing Error is set. This only happens if I use multiple OIDs to be walked. When walking only one or two OIDs at a time, this problem does not occure. But if I use 10 OIDs this problem suddenly appears. I was not able to find out the limit for how many OIDs walking works correclty and when NonIncreasing error occures. For easier reading I try to explain what happens with only two OIDs. I veryfied this behaviour with both the debug command "debug snmp packet" on the Cisco Switch where the agent resides, and by capturing the traffic using tethereal on the managers box. When walking i.e. First OID: .1.3.6.1.2.1.2.2.1.13 and second OID: .1.3.6.1.2.1.2.2.1.14 you detect the end of the first OID tree in net-snmp by finding when the result for first OID is no longer behind ....13 but behind another OID. So as soon as you find .1.3.6.1.2.1.2.2.1.14.1 for first OID, you know that the full tree behind first OID has been found. And now the problem happens. As soon as you find .1.3.6.1.2.1.2.2.1.14.1 net-snmp thinks, that .1.3.6.1.2.1.2.2.1.14.1 is a NonIncreasing response for second OID and sets the appropriate error. >From my point of view, you should "remember" the index (position) of the requested OIDs and of the response OIDs, as for position 1 no NonIncreasing errors happens, and for position 2 also no NonIncreasing error happens. Hopefully I explained this behaviour comprehensive enough - if you have further questions, don't hesitate to ask. I can also provide you with further debug information if you like to. Many thanks in advance Florian Am Dienstag, 10. April 2007 16:17 schrieb Dave Shield: > On 10/04/07, Florian Jauernig <[EMAIL PROTECTED]> wrote: > > I just wanted to give you feedback that tweaking the code in the way > > you suggested now sets the Error correctly in the SNMP session object. > > Thanks. > I've applied this change to the 5.3.x, 5.4.x and current development > branches. (And will update the 5.2.x line, as soon as we're out of the > current code freeze). > > Dave ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
