goBMP is an implementation of Open BMP (RFC 7854) protocol’s collector in go language. Collected BGP information can be published to kafka topics, stored in the file in JSON format or printed to stdout.

goBMP is suitable to run as a standalone binary as well as a containerized workload, provided deployment yaml allows running it as a deployment in Kubernetes.

goBMP receives BGP updates as a part of Open BMP messages, goBMP parses them and generates records depending on BGP Update NLRI and AFI/SAFI.

List of currently supported NLRI and AFI/SAFI:

IPv4 Unicast	1/1
IPv4 Labeled Unicast	1/4
IPv6 Unicast	2/1
IPv6 Labeled Unicast	2/4
VPNv4 unicast	1/128
VPnv6 unicast	2/128
Link-state	16388/71
L2VPN (VPLS)	25/65
L2VPN (EVPN)	25/70
SR Policy for v4	1/73
SR Policy for v6	2/73

goBMP also supports a number of drafts for under development protocols and extensions, such as BGP LS extensions for SRv6 support, Flex Algo, Application Specific attributes etc.

For the complete list of supported extensions and drafts follow this link: Support RFCs and Drafts.

The structure of the each record which is published to kafka, nats, stored in the message file or printed to standard output, is defined in the package message file types.go

Building goBMP

git clone https://github.com/sbezverk/gobmp

cd   gobmp

make gobmp

The statically linked linux binary will be stored in ./bin sub folder.

Running goBMP

As a binary

./bin/gobmp {list of parameters}

goBMP parameters:

--destination-port={port} (default 5050)

When goBMP works in an intercept mode, it receives incoming BMP messages on the source port, makes a copy of BMP message and then transmits the message to the processing listening on a destination port.

--dump={file|console}

Dump processed BMP messages into a file or to the standard output.

--intercept={true|false}

When intercept set "true", all incomming BMP messages will be processed and a copy of a message will be sent to TCP port specified by destination-port.

--kafka-server=”kafka server:port”

Kafka server TCP/IP address

--msg-file={message file path and location} (default "/tmp/messages.json")

Full path and file name to store messages when "dump=file"

--source-port={source-port} (default 5000)

Port to listen for incoming BMP messages (default 5000)

--v=(1-7)

Log level, please use --v=6 for debugging. Level 6 prints in hexadecimal format the incoming message.

As a kubernetes deployment

goBMP can be ran as a kubernetes workload. The deployment yaml file is located in ./deployment folder. goBMP deployment exposes 2 ports, first port (by default 5000) is used for incoming BMP sessions, second port (56767) is used for performance monitoring, goBMP exposes standard golang pprof endpoints.

kubectl create -f ./deployment/gobmp-standalone.yaml

To check the status of a deployment and services

kubectl get pod

Expected output for gobmp pod

NAME                                READY   STATUS    RESTARTS   AGE
gobmp-765db4dcd9-6nh2c              1/1     Running   0          12h

kubectl get svc 

Expected output for gobmp service

NAME               TYPE        CLUSTER-IP       EXTERNAL-IP                 PORT(S)                      AGE
gobmp              ClusterIP   10.224.249.86    192.168.80.254              5000/TCP,56767/TCP           17h

In order to establish BMP session between an external BMP speaker and goBMP application running in kubernetes, goBMP's port must be exposed externally, as in the case of the output provided above, where 192.168.80.254 is external address. The external BMP speaker will need to use 192.168.80.254:5000 to reach goBMP application.

As a Docker container

Quick start with RIS Live feed from RIPE

Start gobmp daemon :

sudo docker run --net=host sbezverk/gobmp --dump=console

Start bgp live feed from RIPE (converted to BMP) :

sudo docker run --net=host sbezverk/ris2bmp:1

Sample output :

gobmp: 06:36:26.088307 {MsgType:7 MsgHash: Msg:{"action":"add","base_attrs":{"base_attr_hash":"c447165a4239db770f610e30dc5df7a7","origin":"igp","as_path":[49697,41047,24961,33891,58453,9808,56048],"as_path_count":7,"nexthop":"80.81.195.241","is_atomic_agg":false,"community_list":"49697:2302, 49697:2500","large_community_list":"24961:1:276, 24961:2:1, 24961:2:150, 24961:2:155, 24961:2:276, 24961:3:1, 24961:4:9002, 24961:5:9002, 24961:6:1, 24961:7:33891, 24961:9:4"},"peer_hash":"75fdb22262697e4b0fcc06f7a8d1496c","peer_ip":"80.81.195.241","peer_asn":49697,"timestamp":"Sep  9 06:34:58.000000","prefix":"223.104.44.0","prefix_len":24,"is_ipv4":true,"origin_as":56048,"nexthop":"80.81.195.241","is_nexthop_ipv4":true,"is_prepolicy":false,"is_adj_rib_in":false}}

Status

goBMP is work in progress, even though a considerable number of AFI/SAFI and BGP-LS attributes are processed, there is still a lot of work for contribution. See CHANGELOG.md for latest updates to this project.