Hi! First of all, use snmpbulkwalk as much as you can on SNMP v2c or v3 devices, it is much faster than snmpwalk.
root@fw01:~# head -150 walk.txt | cut -d' ' -f1 | xargs snmpget -d -r 0 -v 2c -c public 10.67.11.254 Too many object identifiers specified. Only 128 allowed in one request. OK, 128 is allowed by snmpget. root@fw01:~# head -104 walk.txt | cut -d' ' -f1 | xargs snmpget -v 2c -c public 10.67.11.254 Error in packet Reason: (tooBig) Response message would have been too large. That's my Extreme Summit 400 switch saying tooBig. head -103 is OK and yields 103 replies. Up to head -128 is OK for the 400 even if the reply is tooBig (which probaly is entirely correct). At least it responds the way it should. Now for my Trapeze/Juniper MX-200 controller (yes, I actually do have a wireless cluster at home :) ): root@fw01:~# head -127 walk.txt | cut -d' ' -f1 | xargs snmpget -v 2c -c public 10.10.20.11 Error in packet Reason: (tooBig) Response message would have been too large. root@fw01:~# head -128 walk.txt | cut -d' ' -f1 | xargs snmpget -v 2c -c public 10.10.20.11 Timeout: No Response from 10.10.20.11. root@fw01:~# head -129 walk.txt | cut -d' ' -f1 | xargs snmpget -v 2c -c public 10.10.20.11 Too many object identifiers specified. Only 128 allowed in one request. Apparently, Trapeze fails to respond to a request with 128 OIDs in it, and snmpwalk refuses 129. 127 is rejected based on tooBig. The 128 case should probably be considered a difference in interpretation of a limit I guess. Extreme BD10k and X450/460 allows 128 but returns tooBig. Motorola BSR 1000 (DOCSIS CMTS) allows 126 but not 127 OIDs. Motorola BSR 2000 allows 123 but not 124 OIDs. Casa C2200 CMTS allows 128 OIDs. Cisco 2821 router allows 111 but not 112. Of course, Cisco just has to ruin everything with their non-standard way of things with a few line breaks in the sysDescr response (never seen it in a non-cisco device), but after filtering that out, it worked OK. Why the difference? Ask the vendors. I'd say difference in implementation, intended or unintended, not really a bug or anything. /Fredrik > Good morning, > We have some SNMP devices that do not respond to queries where the number of OIDs is over a certain limit. That is, they do respond to queries with N OIDs in the request, but return no response to queries with N+1 and more OIDs. ... ------------------------------------------------------------------------------ DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk _______________________________________________ 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
