Re: [pmacct-discussion] BGP correlation not working with nfacctd, all BGP set to 0

2020-05-19 Thread Paolo Lucente
Hi Wilfrid, "we already capture all the flows matching the different rd because of our netflow setup.". Although i may appreciate if you could elaborate more on your netflow setup (it makes the exercise less a treasure hunt for me), I am sure you do: can you paste me the content of one of your

Re: [pmacct-discussion] BGP correlation not working with nfacctd, all BGP set to 0

2020-05-19 Thread Grassot, Wilfrid
Hi Paolo, Unless I misunderstand the flow_to_rd_map, but this one would not help in our case. Indeed we already capture all the flows matching the different rd because of our netflow setup. nfacctd already receives only flows from the specific RDs involved in the monitored L3VPN . My concern is

Re: [pmacct-discussion] BGP correlation not working with nfacctd, all BGP set to 0

2020-05-19 Thread Paolo Lucente
Hi Wilfrid, This is very possibly point #1 of my previous email. The need for a flow_to_rd_map to associate flows to the right RD. You can find some examples here on how to compose it: https://github.com/pmacct/pmacct/blob/1.7.5/examples/flow_to_rd.map.example Paolo On Tue, May 19, 2020 at

Re: [pmacct-discussion] BGP correlation not working with nfacctd, all BGP set to 0

2020-05-19 Thread Grassot, Wilfrid
Hi Paolo, Could the issue be that correlation does not work because for each "ip_prefix" there is not one, but two or three routes collected by pmbgpd ? Indeed because of redundancies, each prefixes are received by several different routers in our network and by design each of the routers use

Re: [pmacct-discussion] BGP correlation not working with nfacctd, all BGP set to 0

2020-05-18 Thread Grassot, Wilfrid
Hi Paolo, Thank you for your answer. My bad in the description of the issue: w.x.y.z is indeed the ipv4 address of the router loop0 which is also its router-id. Currently our setup is to iBGP peer with the router (router-id w.x.y.z) at the address-family vpnv4. We already filter out using

Re: [pmacct-discussion] BGP correlation not working with nfacctd, all BGP set to 0

2020-05-18 Thread Paolo Lucente
Hi Wilfrid, Thanks for getting in touch. A couple of notes: 1) if you are sending vpnv4 routes - and if that is a requirement - then you will need a flow_to_rd_map to map flows to the right VPN (maybe basing on the input interface at the ingress router? just an idea); 2) Confederations

[pmacct-discussion] BGP correlation not working with nfacctd, all BGP set to 0

2020-05-17 Thread Grassot, Wilfrid
Good afternoon I cannot have my netflow augmented with bgp data (src_as, dst_as, peer_dst_ip.) all of the BGP data stay 0 or are empty An output of the csv file is: 0,0,63.218.164.15,,62.140.128.166,220.206.187.242,2123,2123,udp,1,40 Where 0,0 are the missing src_as, dst_as and , , is