There are tools in here: http://caia.swin.edu.au/urp/bgp/tools.html
which you might find useful, and work (or at least worked) with Quagga
dump files. In particular the MDFMT and the Path Exploration Analyzer.
The PEA might give you some ideas on how to use libbgpdump for analysis,
while the MDFMT is based on pybgpdump
(http://jon.oberheide.org/projects/pybgpdump/) which is very nice for a
quick analysis of MRT dumps.
Hope you haven't already discarded them :-)
Mat
Am 27.11.2012 17:33, schrieb Robert Raszuk:
Thx Larry !
Any pointer to best MRT opensource tools repository for parsing the
messages and maybe even performing some analysis on them (in
particular related to BGP) ?
Rgs,
R.
On Tue, Nov 27, 2012 at 5:28 PM, Larry Blunk <[email protected]> wrote:
On 11/27/2012 11:17 AM, Robert Raszuk wrote:
Hello,
Does anyone (in particular cc-ed authors) recall what is the status,
planned update, planned progress to RFC of this document:
http://tools.ietf.org/id/draft-ietf-grow-mrt-04.txt
Thx,
R.
It's an RFC now --
http://tools.ietf.org/html/rfc6396
Unfortunately, section 4.3.4 does not match the
current Quagga/libbgpdump implementations. The RFC
says to omit the AFI/SAFI/NLRI fields in the MP_REACH_NLRI
attribute (since that info is already in the MRT
RIB Entry Header), but the current implementations
simply copy the attribute as-is in the RIB Entry
field.
Regards,
Larry Blunk
_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow
_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow
