summaryrefslogtreecommitdiff
path: root/docs/source/examples/v3arch/asyncore/agent/ntforg/evaluating-notification-type.rst
blob: 72a3469fbf15036cbdc0aa5a87252e59987a4d53 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
.. toctree::
   :maxdepth: 2

Evaluating NOTIFICATION-TYPE
----------------------------

SNMP SMI defines notifications as a TRAP or INFORM PDU containing
the indication of type (snmpTrapOID) and a set of MIB variables
(Managed Objects Instances) fetched from Agent's MIB at the moment
of notification.

Consequently, sending specific NOTIFICATION-TYPE implies including certain
set of OIDs into PDU. PySNMP offers this facility through NotificationType
class.

.. include:: /../../examples/v3arch/asyncore/agent/ntforg/v2c-trap-via-notification-type.py
   :start-after: """
   :end-before: """#

.. literalinclude:: /../../examples/v3arch/asyncore/agent/ntforg/v2c-trap-via-notification-type.py
   :start-after: """#
   :language: python

:download:`Download</../../examples/v3arch/asyncore/agent/ntforg/v2c-trap-via-notification-type.py>` script.


See also: :doc:`library reference </docs/contents>`.