Chris Welti <[email protected]> wrote:

>ingress and egress on the same interface is a configuration officially 
>supported by Cisco for the Sup2T. Escpecially for the Sup2T-XL/DFC4-XL 
>which has separate netflow tables for ingress and egress, there should 
>be no overflow issues due to this.

I've not read anywhere or been told that ingress & egress is now officially 
supported on Sup2T, & would be grateful for any pointers you can share, thanks! 
 

>just as a side note, while 'match' is fine for input ifindex, output 
>ifindex should NOT be used as a match field in a netflow record for 
>ingress netflow.

Concur 100%.  The key ifindex should match the flow tabulation directionality. 

---------------------------------------
Roland Dobbins <[email protected]>
_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to