When several objects are set in a single command, I've noticed that the snmp agent groups sets of the same object together. It then processes all requests for that object and then moves on to the next object instead of simply marching down the list of oids and handling them in the order they were sent.
Ex: snmpset a i 2 b i 3 c i 4 a i 5 b i 6 c i 7 Looking at the snmpset.c file it linearly grabs the oids and values from the command line and adds them to the pdu. The agent, however, actually goes through the modes of set in this order: a i 2 a i 5 b i 3 b i 6 c i 4 c i 7 I can see how this would work a lot of the time but in my case it doesn't. What I want to do is use a set to c as a flag of sorts. The agent will say, ok, c was set now I need to go store a,b,c to some external variable. But how the oids are currently handled, the values of 2,3,4 have already been written over by 5,6,7 by the time the c handler gets called to do its first set commit. So, is this part of the snmp convention that I'm trying to just throw out the window or is it just how net-snmp handles the requests? ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ 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
