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
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
|
.. include:: /includes/_links.rst
Quick Start
===========
.. toctree::
:maxdepth: 2
Once you decide to test out PySNMP library on your Linux/Windows/macOS
system, you should start to prepare a test field folder and configure the
Python environment.
Set Up Test Field Folder
------------------------
First, it is recommended that you use `pyenv`_ to manage different Python
versions on this machine. If you are using Windows, you can use `pyenv-win`_.
Next, we assume you are now on macOS/Linux, and the following commands
initialize a folder for us,
.. code-block:: bash
$ cd ~
$ mkdir test-field
$ cd test-field
$ pyenv local 3.12
$ pip install pipenv
$ pipenv install pysnmp
$ pipenv run pip list
Here we created a virtual environment using ``pipenv`` for this folder, and
installed ``pysnmp`` so that you can move on with the following
sections.
The final command should print out the dependencies and you should be able to
see ``pysnmp`` version 6.0+ there.
.. note::
If you haven't installed Python 3.12 with ``pyenv``, you should execute
``pyenv install 3.12``.
To delete the virtual environment for this folder, you can use
.. code-block:: bash
$ pipenv --rm
It is common that you use another virtual environment tool, such as venv,
poetry, or conda. Just make sure you use the equivalent commands to set up the
virtual environment for testing.
It is highly recommended that you use a Python virtual environment, as it
makes dependency management and troubleshooting much easier.
Fetch SNMP Variable
-------------------
Next, let's write some test script and play with PySNMP manager side operations.
#. Create a Python script in the test field folder, such as ``v1-get.py``.
#. Cut and paste the following contents below into this file,
.. literalinclude:: /../../examples/hlapi/v3arch/asyncio/manager/cmdgen/v1-get.py
:start-after: """ #
:language: python
:download:`Download</../../examples/hlapi/v3arch/asyncio/manager/cmdgen/v1-get.py>` script.
#. Execute this script. If everything works as it should you will get the following on your
console:
.. code-block:: bash
$ pipenv run python v1-get.py
...
SNMPv2-MIB::sysDescr."0" = SunOS zeus.pysnmp.com 4.1.3_U1 1 sun4m
>>>
Here you can see SNMP v1 GET operation can be easily done with the
:py:class:`~pysnmp.hlapi.v3arch.asyncio.slim` class. Other operations in SNMP v1
and v2c can be done in similar manner. To execute SNMP v3 operations,
however, requires more complex code.
The test agent we use is hosted at `demo.pysnmp.com`_.
Send SNMP TRAP
--------------
Similarly we can perform agent side operations with PySNMP.
#. Create a script file ``default-v1-trap.py``.
#. Cut and paste the following contents below into this file,
.. literalinclude:: /../../examples/hlapi/v3arch/asyncio/agent/ntforg/default-v1-trap.py
:start-after: """ #
:language: python
:download:`Download</../../examples/hlapi/v3arch/asyncio/agent/ntforg/default-v1-trap.py>` script.
#. Execute this script.
.. code-block:: bash
$ pipenv run python default-v1-trap.py
Because this sends out an SNMP v1 TRAP message, we know that no response
will be received.
The notification receiver the receives this message is hosted at
`demo.pysnmp.com`_.
Next Steps
----------
Now that you have successfully finished initial tests of PySNMP, you can
move on to :doc:`/docs/pysnmp-hlapi-tutorial` to learn more API of this
package, or play with more complex examples in the :doc:`/examples/index`
section.
And whenever you want to refer to the SNMP protocol itself, you can visit
the `PySNMP Homepage`_.
Related Resources
-----------------
- `Support Options`_
- :doc:`/docs/pysnmp-hlapi-tutorial`
- :doc:`/docs/api-reference`
- :doc:`/examples/index`
- :doc:`/troubleshooting`
|
