Multiple-session, bulk I/O engine
The pysnmp.bulkrole module defines manager
and agent classes, representing SNMP manager and agent roles
in a SNMP system. These classes implement network client (manager) and server
(agent) respectively, that run multiple transport sessions against multiple
destinations over multiple BSD sockets (one socket per session).
They are intended to be used in situations where a large number of SNMP parties
need to be talked with at about the same time (a poll against multiple routers
for gathering statistics at a specific time, for example).
The pysnmp.bulkrole code is a pure network transport
facility -- it deals with abstract data items and has nothing to know about
SNMP context. In order to build a complete SNMP entity, a SNMP message
processing code should be used along. See SNMP protocol modules
(v2c, v1) for that.
The pysnmp.bulkrole module defines the only class:
- class manager([iface])
-
Returns a new instance of manager class, representing
multiple network clients, each of which may be running against its own
destination (to be defined later on).
The iface parameter, if given, specifies the interface and
port on local machine to bind() to. This argument must
follow the socket module notation. All further requests
would then be originated from the given interface/port (for example,
('127.0.0.1', 0)).
The default for iface is ('0.0.0.0', 0) what stands for binding
to a primary interface at the local machine.
- exception Error
-
Exception raised on any error in the pysnmp.bulkrole module,
as well as in its base (pysnmp.role) and derivative modules.
This exception class is a subclass of the pysnmp.role class.
See documentation on the error.General base class for
usage details.
The following exceptions are derived from this class:
- exception BadArgument
-
Bad parameters given.
Subsections
Need help? Try PySNMP mailing lists.
|