We needed the following to see all of the flow data (we use sampling as well):
int x/x ip flow ingress ip route-cache flow mls netflow sampling Peter Kranz Founder/CEO - Unwired Ltd www.UnwiredLtd.com Desk: 510-868-1614 x100 Mobile: 510-207-0000 [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Andreas Bourges Sent: Monday, July 06, 2009 7:39 AM To: [email protected] Subject: Re: [c-nsp] Netflow Collector shows minimal bandwidth from 6509 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, On Monday 06 July 2009 16:01:42 Justin Krejci wrote: > > > interface GigabitEthernet5/1 > > ip flow ingress > > ip flow egress ...ip flow egress will only catch the software-processed flows. So you will need to modify your netflow setup to enable ip flow ingress on all layer3 interfaces to catch all output traffic for gig5/1. which doesn't explain why you're still missing 50% of your ingress flows ?! Regards, Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkpSDH0ACgkQRrny/uOBVy43UACgoOdfbyaS8X8Td34Twi5OUJID RAEAnjZiiCWqdDBiNXavjk5DTkLBr+ei =9gLx -----END PGP SIGNATURE----- _______________________________________________ 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/
