That's it! Thanks very much... "ip flow ingress" solved my problem...
Paul -----Original Message----- From: Jeff Fitzwater [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 16, 2008 1:16 PM To: Paul Stewart Cc: 'cisco-nsp' Subject: Re: [c-nsp] 6500 Netflow Not sure what IOS you are running, which can make a difference, but you are probably only seeing route-processor flows and not mls switched flows. There should be an interface command like "ip flow-cache" or "ip flow ingress". There are other commands that enable BRIDGED flows to be included, (port to port within switch) but don't remember what they are. Jeff Fitzwater OIT Network Systems Princeton University On Apr 16, 2008, at 12:20 PM, Paul Stewart wrote: > Hi there... > > I am trying to turn up netflow reporting on a 6500 - ran into this > before > and can't remember the solution....;) > > On the reporting server I'm not getting the correct levels of data - > almost > like it's sampling the data by default... > > Can someone tell me the missing piece here? I've searched the 6500 > docs and > don't see anything wrong.... > > Config looks like this: > > ip flow-cache timeout active 1 > mls flow ip interface-full > ip flow-export version 5 origin-as > ip flow-export destination xxx.xxx.xxx.xxx xxxx > mls rp ip > mls aging long 64 > mls aging normal 32 > mls flow ip interface-full > mls nde sender version 5 > no mls acl tcam share-global > > Thanks ... the netflow reporting system works great against the > GSR's, only > having this problem with the 6500's > > Paul > > > _______________________________________________ > 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/
