So for a little more clarification on this, I would want to monitor say ingress on my transit links and then ingress on say my input links from my server farm ports and capture the data that way instead of monitoring ingress and egress on the same transit only interfaces? So in other words measure inbound from the public internet and then inbound from the internal sites and customer pools?
Do I more or less have it? On May 21, 2014, at 9:58 PM, Roland Dobbins <[email protected]> wrote: > > On May 22, 2014, at 8:40 AM, CiscoNSP List <[email protected]> wrote: > >> Can anyone please explain why? > > Another problem with egress NetFlow is that you won't get stats on traffic > which is being dropped by ACLs, uRPF, et. al. > > You should always use ingress NetFlow unless you have a specific topological > issue which precludes its use. > > ---------------------------------------------------------------------- > Roland Dobbins <[email protected]> // <http://www.arbornetworks.com> > > Equo ne credite, Teucri. > > -- Laocoön > > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
