SNMP::Query::Asynch - Fast asynchronous execution of batches of SNMP queries
Version 0.01
use SNMP::Query::Asynch; my @varbinds = qw( ifDescr ifInOctets ifOutOctets ifAlias ifType ifName ifInErrors ifOutErrors ifSpeed ifAdminStatus ifOperStatus ); my $query = SNMP::Query::Asynch->new(); # You should create and populate @hosts to make this synposis code work. # It's an AoH, fairly simple. For example... my @hosts = create_hosts_array('snmp_hosts.csv'); foreach my $host (@hosts) { # Add a getbulk operation to the queue. $query->add_getbulk({ # Params passed to directly to SNMP::Session->new() DestHost => $host->{HOSTIP}, Community => $host->{COMMUNITY}, Version => $host->{SNMPVER}, # getbulk only supports 2 or 3. # Params concerning the type of query operation # See POD for SNMP::Session->getbulk() in this case. MaxRepeaters => 20, NonRepeaters => 0, # The varbinds to be operated on - can be a reference to anything # supported by the corresponding query operation in SNMP::Session. VarBinds => \@varbinds, }); } # Execute the queries that were added, get a reference to the results array. my $results = $query->execute({ InFlight => 50, # Simultaneous operations MasterTimeout => 60, # Seconds until unfinished operations are aborted. }); # See what the results look like. use Data::Dumper; print Dumper $results;
This module allows for a fairly simple, streamlined means of executing large numbers of SNMP operations as fast as your systems can handle. It extensively uses net-snmp's asynchronous operation interfaces and callbacks to keep as much data flowing as you need.
Perl's support of closures and anonymous subroutines provide the means for sophisticated, elegant control of query operations before and after execution. There are also facilities to install callbacks that are run after pre-set numbers (batches) of operations are completed .
These callbacks can be used to log progress, update the user, transfer results from memory to disk (or even another thread or process!) or anything you can think of! If there's some feature you desire, do not hesitate to ask me!!!
Please be aware - my primary design concern is speed and flexibility. I have certain non-scientific, subjective benchmarks I use to decide if some modification is worth-while, but so far the design of the internals of this module has lent itself to feature additions and enhancements very well.
Constructs a new query object with an empty queue.
Adds a getbulk query operation to the queue.
Executes all operations in the queue.
Shuffles the operations in the queue so they are executed in random order.
Returns the number of operations currently issued which have not yet been completed.
Please note: completed means that the operation was issued and either results data or an error condition were recieved. If the operation was interrupted before that happens, then is not counted as completed. This typically only happens when the call to execute() was interrupted by a fatal error or the query-object's master timeout was exceeded.
Returns the number of operations that have been issued during the current execute() call. If called after execute() has completed, returns the number issued during the most recent execute() call.
Each call to execute() resets this value to zero.
Returns the number of operations that have been completed during the current execute() call. If called after execute() has completed, returns the number completed during the most recent execute() call.
Returns the number of operations that have been issued during all calls to execute() since the query object was created. This value is *never* reset.
Returns the number of operations that have been completed during all calls to execute() since the query object was created. This value is *never* reset.
Returns a reference to the query object's internal results array.
NOTE: Yes, I *know* that providing access to an object's internal data is poor OO design, but it gets the job done right now. I do plan on converting the results array into it's own type of object with OO-kosher semantics, but only if that does not substantially impact overall speed.
That said, use this method with caution because in the future it will likely be changed to return something completely different than an array-ref or maybe even be removed and replaced with a different method. I may also have a moment of insanity and make the results-object tied so as to look like an array. But I doubt it unless people ask for it enough.
Nothing.
SNMP SNMP::Effective SNMP::Multi MRTG RTG YATG
Steve Scaffidi, <sscaffidi at cpan.org>
<sscaffidi at cpan.org>
Please report any bugs or feature requests to bug-snmp-query-asynch at rt.cpan.org, or through the web interface at http://rt.cpan.org/NoAuth/ReportBug.html?Queue=SNMP-Query-Asynch. I will be notified, and then you'll automatically be notified of progress on your bug as I make changes.
bug-snmp-query-asynch at rt.cpan.org
You can find documentation for this module with the perldoc command.
perldoc SNMP::Query::Asynch
You can also look for information at:
AnnoCPAN: Annotated CPAN documentation
http://annocpan.org/dist/SNMP-Query-Asynch
CPAN Ratings
http://cpanratings.perl.org/d/SNMP-Query-Asynch
RT: CPAN's request tracker
http://rt.cpan.org/NoAuth/Bugs.html?Dist=SNMP-Query-Asynch
Search CPAN
http://search.cpan.org/dist/SNMP-Query-Asynch
Copyright 2008 Steve Scaffidi, all rights reserved.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
To install SNMP::Query::Asynch, copy and paste the appropriate command in to your terminal.
cpanm
cpanm SNMP::Query::Asynch
CPAN shell
perl -MCPAN -e shell install SNMP::Query::Asynch
For more information on module installation, please visit the detailed CPAN module installation guide.