summaryrefslogtreecommitdiff
path: root/doc/user/snmptrap.rst
diff options
context:
space:
mode:
authorFrancois Dumontet <francois.dumontet@6wind.com>2023-09-05 14:16:20 +0200
committerFrancois Dumontet <francois.dumontet@6wind.com>2023-10-24 17:16:47 +0200
commit7552dba274605ca8327869e3648a195c4a890879 (patch)
treede0abb9c6112a27916e775eb2cf563fb13364083 /doc/user/snmptrap.rst
parente6de67f1e5b2658067fa834be575bcdb20a6dd89 (diff)
doc: [no] bgp snmp traps <rfc4273|bgp4-mibv2>
update traps documentation Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
Diffstat (limited to 'doc/user/snmptrap.rst')
-rw-r--r--doc/user/snmptrap.rst20
1 files changed, 18 insertions, 2 deletions
diff --git a/doc/user/snmptrap.rst b/doc/user/snmptrap.rst
index 7e306b743d..df534e28bd 100644
--- a/doc/user/snmptrap.rst
+++ b/doc/user/snmptrap.rst
@@ -4,8 +4,9 @@ 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`.
-The BGP4 mib will send traps on peer up/down events. These should be visible in
-your snmp logs with a message similar to:
+BGP handles both :rfc:`4273` and [Draft-IETF-idr-bgp4-mibv2-11]_ MIBs.
+The BGP4 MIBs will send traps on peer up/down events. These should be
+visible in your snmp logs with a message similar to:
::
@@ -199,3 +200,18 @@ a siren, have your display flash, etc., be creative ;).
# mail the notification
echo "$MAIL" | mail -s "$SUBJECT" $EMAILADDR
+
+.. _traps-mib-selection:
+
+Traps Mib Selection in BGP
+--------------------------
+
+Both :rfc:`4273` and [Draft-IETF-idr-bgp4-mibv2-11]_ MIBs define traps for
+dealing with up/down events and state transition. The user has the
+possibility to select the MIB he wants to receive traps from:
+
+.. clicmd:: bgp snmp traps <rfc4273|bgp4-mibv2>
+
+By default, only rfc4273 traps are enabled and sent.
+
+.. [Draft-IETF-idr-bgp4-mibv2-11] <https://tools.ietf.org/id/draft-ietf-idr-bgp4-mibv2-11.txt>