-e MEM=<gb value>works on the AIO and Mysql containers.
#pat_enabled value is a boolean: # false (the default) - MD5 of (connection source address, collector hash) # # true - MD5 of one of the following: # # If INIT_BGP_ID (type=65531) is present: # (bgp_router_id, collector_hash) # # If INIT doesn't include the BGP_ID, then: # (name, collector_hash) # # If INIT doesn't include either bgp_id or name, then it uses: # (connection source address, collector hash) pat_enabled: false
Hey guys! I have SNAS and PNDA both deployed in Openstack, and I'm not quite sure how I should get them working together. I read up on the 'integrating openBMP' steps in the docs on http://pnda.io/guide , but that just left me confused. Anyone ever get this up and running? Appreciate any steps you can provide to point me in the right direction. Both services are up and running with no errors, but I don't know how to link them. PNDA is an Openstack Pico deployment.
Thanks for your help!
PostgreSQL with TimescaleDB, RPKI, and IRR integration is available now via openbmp/postgres container
The openbmp/collector and openbmp/kafka containers should be used wtih the openbmp/postgres containers to
provide an end-to-end BGP monitoring and analytics.
Grafana is the preferred visualization tool. Grafana enables collabration with dashboards and plugins without requiring
much development experience. We encourge everyone to contribute new or updated dashboards and plugins via
github pull requests. You can start using Grafana today with openbmp/postgres container by following the
OpenBMP Grafana instructions.
At this time there is full support for IPv4, IPv6 unicast and labeled unicast address families.
Soon to come will be L3VPN, Link-State, and EVPN.
Please Join the chat on Gitter
to collaborate with others interactively.
@lollo93_gitlab , you mean you are reading the "bmp_raw" topic? The message structure is documented Message Bus API. Jump to the bottom of that doc, or search for BMP RAW Data.
The message has two parts... First part is the header and the second part is the RAW binary BMP message (actual BMP message, headers and all). The two parts are split by a double newline
\n\n.. BMP (and BGP) route monitor messages do not convey the router that the message came from. You'll need to parse the HEADER field
R_HASH_ID for that. The
R_HASH_ID links the the hash id in the openbmp.parsed.routers topic.