summaryrefslogtreecommitdiffstats
path: root/doc/user/snmptrap.rst
diff options
context:
space:
mode:
authorQuentin Young <qlyoung@cumulusnetworks.com>2018-01-29 22:38:07 +0100
committerQuentin Young <qlyoung@cumulusnetworks.com>2018-01-29 22:38:07 +0100
commitc1a54c054d434b9e50467db30665cfb688e16a2e (patch)
tree6734f37671fe5f7dfed4b68afb21d0f2d6a66514 /doc/user/snmptrap.rst
parentdoc: cleanup multiple (diff)
downloadfrr-c1a54c054d434b9e50467db30665cfb688e16a2e.tar.xz
frr-c1a54c054d434b9e50467db30665cfb688e16a2e.zip
doc: manually finish conversion
Signed-off-by: Quentin Young <qlyoung@cumulusnetworks.com>
Diffstat (limited to 'doc/user/snmptrap.rst')
-rw-r--r--doc/user/snmptrap.rst30
1 files changed, 15 insertions, 15 deletions
diff --git a/doc/user/snmptrap.rst b/doc/user/snmptrap.rst
index 28cc5fcec..9d6b12e0b 100644
--- a/doc/user/snmptrap.rst
+++ b/doc/user/snmptrap.rst
@@ -1,18 +1,18 @@
Handling SNMP Traps
===================
-To handle snmp traps make sure your snmp setup of frr works
-correctly as described in the frr documentation in :ref:`SNMP_Support`.
+To handle snmp traps make sure your snmp setup of frr works correctly as
+described in the frr documentation in :ref:`SNMP_Support`.
-The BGP4 mib will send traps on peer up/down events. These should be
-visible in your snmp logs with a message similar to:
+The BGP4 mib will send traps on peer up/down events. These should be visible in
+your snmp logs with a message similar to:
::
snmpd[13733]: Got trap from peer on fd 14
-To react on these traps they should be handled by a trapsink. Configure
-your trapsink by adding the following lines to :file:`/etc/snmpd/snmpd.conf`:
+To react on these traps they should be handled by a trapsink. Configure your
+trapsink by adding the following lines to :file:`/etc/snmpd/snmpd.conf`:
::
@@ -20,9 +20,9 @@ your trapsink by adding the following lines to :file:`/etc/snmpd/snmpd.conf`:
trapsink localhost
-This will send all traps to an snmptrapd running on localhost. You can
-of course also use a dedicated management station to catch traps.
-Configure the snmptrapd daemon by adding the following line to
+This will send all traps to an snmptrapd running on localhost. You can of
+course also use a dedicated management station to catch traps. Configure the
+snmptrapd daemon by adding the following line to
:file:`/etc/snmpd/snmptrapd.conf`:
::
@@ -32,15 +32,15 @@ Configure the snmptrapd daemon by adding the following line to
This will use the bash script :file:`/etc/snmp/snmptrap_handle.sh` to handle
the BGP4 traps. To add traps for other protocol daemons, lookup their
-appropriate OID from their mib. (For additional information about which
-traps are supported by your mib, lookup the mib on
+appropriate OID from their mib. (For additional information about which traps
+are supported by your mib, lookup the mib on
`http://www.oidview.com/mibs/detail.html <http://www.oidview.com/mibs/detail.html>`_).
-Make sure snmptrapd is started.
+Make sure *snmptrapd* is started.
-The snmptrap_handle.sh script I personally use for handling BGP4 traps
-is below. You can of course do all sorts of things when handling traps,
-like sound a siren, have your display flash, etc., be creative ;).
+The snmptrap_handle.sh script I personally use for handling BGP4 traps is
+below. You can of course do all sorts of things when handling traps, like sound
+a siren, have your display flash, etc., be creative ;).
::