p_prefix": "a.b.c.d/27",
> "rd": "0:ASN:911790015",
> "label": "49061"
> }
> {
> "seq": 3,
> "timestamp": "2020-05-19 07:15:00",
> "peer_ip_src": " w.x.y.z ",
>
;: "a.b.c.d/27",
"rd": "0:ASN:911790015",
"label": "49061"
}
{
"seq": 3,
"timestamp": "2020-05-19 07:15:00",
"peer_ip_src": " w.x.y.z ",
"ip_prefix": "a.b.c.d/27",
&
b.c.d) corresponding to ip_prefix = a.b.c.d ?
>
> Wilfrid
>
>
> -Original Message-
> From: Grassot, Wilfrid
> Sent: Monday, 18 May 2020 17:05
> To: Paolo Lucente ; pmacct-discussion@pmacct.net
> Subject: RE: [pmacct-discussion] BGP correlation not working w
m: Grassot, Wilfrid
Sent: Monday, 18 May 2020 17:05
To: Paolo Lucente ; pmacct-discussion@pmacct.net
Subject: RE: [pmacct-discussion] BGP correlation not working with nfacctd,
all BGP set to 0
Hi Paolo,
Thank you for your answer.
My bad in the description of the issue:
w.x.y.z is indeed the ipv4 addr
-discussion@pmacct.net; Grassot, Wilfrid
Subject: Re: [pmacct-discussion] BGP correlation not working with nfacctd,
all BGP set to 0
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
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 alw
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 t
