[c-nsp] 6500 Netflow

Gert Doering gert at greenie.muc.de
Thu Apr 17 14:02:57 EDT 2008


Hi,

On Thu, Apr 17, 2008 at 10:54:15AM -0700, virendra rode // wrote:
> hmm, so does that mean enabling netflow on the main interface and not
> sub-interface(s) won't collect netflow and /or populate netflow table
> for the sub-interface?

Please note that this thread was explicitely talking about 6500/7600
hardware...

> doing a quick test on my lab router 2800 running 12.4(10c) 

... and that's almost the "most different" thing Cisco builds these days
regarding router architecture.

> shows netflow
> collector gathering data from sub-interface w/ "ip route-cache flow"
> enabled on the main interface or am I confusing myself?
> 
> sh ip cache flow shows traffic being sourced from sub-interface.

Don't use "ip route-cache flow" (which is a "early stone age" command, 
and can only be set on the main interface, and automatically enables 
flow accounting for all sub-interfaces).  

Use "ip flow ingress", which is per-subif.

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert at greenie.muc.de
fax: +49-89-35655025                        gert at net.informatik.tu-muenchen.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 304 bytes
Desc: not available
Url : https://puck.nether.net/pipermail/cisco-nsp/attachments/20080417/2a7d3ba7/attachment-0001.bin 


More information about the cisco-nsp mailing list