summaryrefslogtreecommitdiffstats
path: root/docs/sections/services/snmptrap/installation.rst
blob: 3fbb4cde93ff3118d05f3a30ab63de671829f5ca (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
28
29
30
31
32
33
34
35
36
37
38
39
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0

Installation
============

**SNMPTRAP** is delivered as a docker container.  The host or VM that
will run this container must have the docker application loaded and
available to the userID that will be running the SNMPTRAP container.

The instructions below will download and run the latest SNMPTRAP
container from the NEXUS repository.

Environment
-----------

An environment suitable for running docker containers is recommended.
If that is not available, SNMPTRAP source can be downloaded and run
in a VM or on baremetal.  

If running from a docker container, it is assumed that the config
binding service has been installed and is successfully instantiating
container configurations as needed.

Also required is a working DMAAP/MR message router environment.  SNMPTRAP
publishes traps to DMAAP/MR as JSON messages, and expect the host
resources and publishing credentials to be included in the CONFIG
BINDING SERVICE config.

Steps
-----

The following command will download the latest snmptrap container
from nexus and launch it in the container named "snmptrap":

.. code-block:: bash

    docker run --detach -t --rm -p 162:6162/udp -P --name=snmptrap nexus3.onap.org:10001/onap/org.onap.dcaegen2.collectors.snmptrap ./bin/snmptrapd.sh start