>>>>> Eddie Corns writes:
Eddie> The snippets I posted before that I used for testing the speed
Eddie> of explicit polling were, if you recall, a) restricted to
Eddie> ifTable entries and b) buggy because of forgetting about the
Eddie> non-contiguity of the indexes. So I put together a little test
Eddie> script for doing more generic polls. It does multiple tables
Eddie> on multiple machines. It looks like this:
[...]
I like the code snippets and the numbers that you are posting.
Using getnext instead of get is IMHO the right decision. In 3.0.0,
there is an asynchronous walk command. Using this asynchronous walk
has some benefits over a pure Tcl solution which calls getnexts. The
most important is that the walk command uses getbulks internally. So
if you are talking to SNMPv2c or SNMPv3 agents, you will see a real
speedup without any extra Tcl code.
The 3.0.0 walk implementation may need some enhancements so that you
have better control where it stops and that you can have non-repeaters.
/js
-- Juergen Schoenwaelder Technical University Braunschweig <schoenw@ibr.cs.tu-bs.de> Dept. Operating Systems & Computer Networks Phone: +49 531 391 3289 Bueltenweg 74/75, 38106 Braunschweig, Germany Fax: +49 531 391 5936 <URL:http://www.ibr.cs.tu-bs.de/~schoenw/>-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.
This archive was generated by hypermail 2b29 : Mon Jan 08 2001 - 15:27:38 MET