Jonathan, Yes starting to make sense. I just starting using the 6509's so trying to get used to them. I am not sure what the manangemnt interfaces are as they are not labled in the configuration file, but I understand what you are saying.
-----Original Message----- From: Jonathan Lassoff [mailto:[email protected]] Sent: Monday, March 08, 2010 1:15 PM To: Travis Formoso Cc: Drew Weaver; flow-tools Subject: RE: [Flow-tools] Setting up NetFlow on 6509 Excerpts from Travis Formoso's message of Mon Mar 08 10:05:56 -0800 2010: > Drew, > > Right (I have to use ip route-cache because the ip flow ingress > command does not work, might be our version,) however I still would > need to the export command to let it know where to send the data to. > > Once I do the export on the two different vlans (will be more) it > comes in the netflow program I am using as 2 different sources. Use a single "ip flow-export destination ..." line. This should send all the flows in the table, not just ones for a certain interface -- I believe. For example, if I had VLANs 10 and 11 as customer interfaces, and Gi5/1 as a management interface. interface Gi5/1 ip address 10.0.0.1 255.255.255.0 no shutdown ! interface Vlan10 ip address 192.168.10.1 255.255.255.0 ip route-cache flow no shutdown ! interface Vlan11 ip address 192.168.11.1 255.255.255.0 ip route-cache flow no shutdown ! mls nde sender version 5 mls flow ip interface-full mls nde interface ip flow-export source Gi5/1 ip flow-export destination 10.0.0.2 2055 With a configuration like this, I believe 10.0.0.2 should receive flow information for hosts on both Vlan10 and Vlan11 on UDP port 2055. Does this help? Cheers, jonathan P.S. In regards to your license limitation, I've had luck using the flow-fanout utility to multiplex multiple netflow exporters into what will appear to be a single stream. You would have to be using an application that relies on the netflow content to differentiate users and applications, since you wont be able to easily tell which router the export is coming from. _______________________________________________ Flow-tools mailing list [email protected] http://mailman.splintered.net/mailman/listinfo/flow-tools
