summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorOndrej Zajicek <santiago@crfreenet.org>2023-04-21 04:47:55 +0200
committerOndrej Zajicek <santiago@crfreenet.org>2023-04-21 04:47:55 +0200
commit52450bc96dcedbc30cbb2e282c6706ad9e5e5774 (patch)
treee12244a788d6a26c52b3e5785c677b8d82b6a1c9 /doc
parentd61505b039bf0aa6697e28b2a4e07907c89ba1fb (diff)
parentf3b599afe5bde0c7f232421743041b305bb8afa7 (diff)
Merge branch 'bmp'
Diffstat (limited to 'doc')
-rw-r--r--doc/bird.sgml29
1 files changed, 29 insertions, 0 deletions
diff --git a/doc/bird.sgml b/doc/bird.sgml
index 557140b8..39eae4cd 100644
--- a/doc/bird.sgml
+++ b/doc/bird.sgml
@@ -3268,6 +3268,35 @@ protocol bgp {
</code>
+<sect>BMP
+<label id="bmp">
+
+<p>The BGP Monitoring Protocol is used for monitoring BGP sessions and obtaining
+routing table data. The current implementation in BIRD is a preliminary release
+with a limited feature set, it will be subject to significant changes in the
+future. It is not ready for production usage and therefore it is not compiled
+by default and have to be enabled during installation by the configure option
+<tt/--with-protocols=/.
+
+<p>The implementation is limited to monitor protocol state changes and routes
+in <ref id="bgp-import-table" name="BGP import tables"> (not regular routing
+tables), therefore import table must be enabled in BGP protocols. All BGP
+protocols are monitored automatically.
+
+<sect1>Example
+<label id="bmp-exam">
+
+<p><code>
+protocol bmp {
+ # The monitoring station to connect to
+ station address ip 198.51.100.10 port 1790;
+
+ # required option
+ monitoring rib in pre_policy;
+}
+</code>
+
+
<sect>Device
<label id="device">