Thank you very much for pointing this out Ondrej This seems to mostly satisfy the requirement of getting the routes from the BIRD server ( until BMP comes into play ) We are using MRT following the instructions in here https://bird.network.cz/?get_doc&v=20&f=bird-6.html#ss6.7 One question, though, is if MRT supports dumping of both RIB and FIB? From the document, it looks like it only dumps the routes that are received by the router and not the routes after the BIRD router server has applied policy to them. Is that a correct understanding or are we missing something in terms of how to specify options for MRT dump?
Bests Ali -----Original Message----- From: Ondrej Zajicek <santi...@crfreenet.org> Sent: Thursday, June 24, 2021 5:05 AM To: Ali Monfared <alireza....@microsoft.com> Cc: bird-users@network.cz Subject: [EXTERNAL] Re: Question Regarding Extracting BGP RIB and FIB data from BIRD On Mon, Jun 21, 2021 at 07:49:41PM +0000, Ali Monfared wrote: > Hello BIRD team, > > We have recently started to use BIRD in an internal project as a router > server which is expected to perform most of the regular operations that our > BGP routers do. > On that note, we are looking for best practices to extract the RIB and FIB > BGP routes from the BIRD server. > We have noticed that most of the BGP attributes for any route that is > sent to the BIRD server is available inside the logs of the BIRD > server but was wondering if there are better ways or best practices > that you would suggest if we want to have a way to extract each BGP > route that is received in the BIRD server ( so that we can later send > it to internal databases for further analysis ) Hello Probably the best way with current code is to configure mrt dump feature to either dump received/sent BGP routes, or periodic dumps of routing table (or both) in interoperable MRT format. Soon, we plan to have BMP (BGP Monitoring Protocol) support, but the code for that is not yet production quality. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santi...@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
