I would think you'd just peer every collector to every device in a full
mesh, unless i'm missing something obvious. Having peering sessions going
up and down constantly between the network devices and one of n collectors
behind a load balancer does not seem feasible.
On Tue, Sep 5, 2017 at 10:46 A
Right…..routers export flow to the VIP, as well as “think” they are BGPing with
the VIP. The LB then has a static rule that forwards both BGP/flow to the
correct collector. The goal being that if the collector IP changes for some
reason, I don’t have to go touch the router configs.
> On Sep 5
I'm not sure I follow - do you mean setting up BGP peering of the
collectors to your source devices using the collector VIP as the neighbor
address?
On Sep 5, 2017 10:11 AM, "Paul Mabey" wrote:
> Has anyone had success is pushing BGP sessions through an LB along with
> netflow? Interested in the
Has anyone had success is pushing BGP sessions through an LB along with
netflow? Interested in the solution below but would like to have BGP aligned
with netflow as well.
> On Sep 4, 2017, at 9:48 AM, Aaron Finney wrote:
>
> Great to hear, nice work!
>
> Aaron
>
> On Sep 4, 2017 1:55 AM, "
> I see now. Can you try with 'nfacctd_time_new: true' It will cause
> time-binning to use arrival time of the flow to the collector (that
> time should be reasonably close to flow end time and stamp_updated).
Exactly that is what I switched to and it does its job. :)
Since I don't use it for rea