summaryrefslogtreecommitdiff
path: root/docs/source/examples/v3arch/asyncore/agent/ntforg/evaluating-notification-type.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/source/examples/v3arch/asyncore/agent/ntforg/evaluating-notification-type.rst')
-rw-r--r--docs/source/examples/v3arch/asyncore/agent/ntforg/evaluating-notification-type.rst26
1 files changed, 26 insertions, 0 deletions
diff --git a/docs/source/examples/v3arch/asyncore/agent/ntforg/evaluating-notification-type.rst b/docs/source/examples/v3arch/asyncore/agent/ntforg/evaluating-notification-type.rst
new file mode 100644
index 0000000..6ec5acc
--- /dev/null
+++ b/docs/source/examples/v3arch/asyncore/agent/ntforg/evaluating-notification-type.rst
@@ -0,0 +1,26 @@
+.. 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/trap-v2c-with-objects.py
+ :start-after: """
+ :end-before: """#
+
+.. literalinclude:: /../../examples/v3arch/asyncore/agent/ntforg/trap-v2c-with-objects.py
+ :start-after: """#
+ :language: python
+
+:download:`Download</../../examples/v3arch/asyncore/agent/ntforg/trap-v2c-with-objects.py>` script.
+
+