[c-nsp] Sup2T - poor netflow performance

Dobbins, Roland rdobbins at arbor.net
Fri Oct 18 08:05:04 EDT 2013

On Oct 18, 2013, at 12:13 PM, "Rolf Hanßen" <nsp at rhanssen.de> wrote:

> ip flow monitor <monitorname> input

> ip flow monitor <monitorname> output

If you're collecting both ingress and egress NetFlow on the same interface, this could be contributing to your issues - Cisco do not recommend doing this due to overflow issues (which could lead to punting).

Sampler configuration is covered in the Flexible NetFlow Command Reference for 15.x on cisco.com. 

And again, input ifindex should be obtained via 'match', not 'collect', in order to ensure that it's a key field.

Roland Dobbins <rdobbins at arbor.net>

More information about the cisco-nsp mailing list