mirrors/kube-router
1
0
Fork 0
mirror of https://github.com/cloudnativelabs/kube-router.git synced 2025-10-09 17:01:30 +02:00
Code Issues Packages Projects Releases Wiki Activity
kube-router/vendor/github.com/osrg/gobgp/docs/sources/bmp.md
Murali Reddy 04a5cc033a base line version tested with kube 1.5.6, 1.6
2017-04-17 10:33:09 +05:30

1.8 KiB
Raw Blame History

BGP Monitoring Protocol

GoBGP supports BGP Monitoring Protocol (RFC 7854), which provides a convenient interface for obtaining route views.

Prerequisites

Assume you finished Getting Started.

Contents

Configuration

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

Flows can be post-policy, pre-policy, or both. Pre-policy flows are the default.

Enable post-policy support as follows:

[[bmp-servers]]
  [bmp-servers.config]
    address = "127.0.0.1"
    port=11019
    route-monitoring-policy = "post-policy"

Enable both pre-policy and post-policy support as follows:

[[bmp-servers]]
  [bmp-servers.config]
    address = "127.0.0.1"
    port=11019
    route-monitoring-policy = "both"

Verification

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

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"}