GoBGP supports BGP Monitoring Protocol (RFC 7854), which provides a convenient interface for obtaining route views.
Assume you finished Getting Started.
Add [bmp-servers]
session to enable BMP.
[global.config]
as = 64512
router-id = "192.168.255.1"
[[bmp-servers]]
[bmp-servers.config]
address = "127.0.0.1"
port=11019
The supported route monitoring policy types are:
- pre-policy (Default)
- post-policy
- both (Obsoleted)
- local-rib
- all
Enable post-policy support as follows:
[[bmp-servers]]
[bmp-servers.config]
address = "127.0.0.1"
port=11019
route-monitoring-policy = "post-policy"
Enable all policies support as follows:
[[bmp-servers]]
[bmp-servers.config]
address = "127.0.0.1"
port=11019
route-monitoring-policy = "all"
To enable BMP stats reports, specify the interval seconds to send statistics messages. The default value is 0 and no statistics messages are sent. Please note the range of this interval is 15 though 65535 seconds.
[[bmp-servers]]
[bmp-servers.config]
address = "127.0.0.1"
port=11019
statistics-timeout = 3600
To enable route mirroring feature, specify true
for route-mirroring-enabled
option.
Please note this option is mainly for debugging purpose.
[[bmp-servers]]
[bmp-servers.config]
address = "127.0.0.1"
port=11019
route-mirroring-enabled = true
Let's check if BMP works with a bmp server. GoBGP also supports BMP server (currently, just shows received BMP messages in the json format).
$ go get github.com/osrg/gobgp/gobmpd
$ gobmpd
...(snip)...
Once the BMP server accepts a connection from gobgpd, then you see below on the BMP server side.
INFO[0013] Accepted a new connection from 127.0.0.1:33685
{"Header":{"Version":3,"Length":6,"Type":4},"PeerHeader":{"PeerType":0,"IsPostPolicy":false,"PeerDistinguisher":0,"PeerAddress":"","PeerAS":0,"PeerBGPID":"","Timestamp":0},"Body":{"Info":null}}
You also see below on the BGP server side:
{"level":"info","msg":"bmp server is connected, 127.0.0.1:11019","time":"2015-09-15T10:29:03+09:00"}