Now I remember why I can't use this (sorry it's been a while since I've examined this)
The appliance we are sending our flows to can only handle maybe 1% of our actual flows (sampled) (and only from 2 out of 10 of our interfaces) I would like to send all of the flow data to another system for analysis. So basically I would need to send all of the flow data to a middle-man, and then have it configured to somehow know what to send where. -Drew From: Ben Hicks [mailto:[EMAIL PROTECTED] Sent: Thursday, July 03, 2008 7:22 AM To: Drew Weaver; [email protected] Subject: RE: [c-nsp] 'multiplexing" netflow? Why not just have multiple export statements. Taken from - http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/12s_mdnf.html#wp1021114 export destination 10.0.101.254 9991 export destination 10.0.101.254 1999 Many thanks, Ben -----Original Message----- From: [EMAIL PROTECTED] on behalf of Drew Weaver Sent: Thu 03/07/2008 12:18 To: [email protected] Subject: [c-nsp] 'multiplexing" netflow? Hi there, we have equipment at our edge that requires us to export our netflow to it in order for it to function but we would also like our NetFlow stats to be exported somewhere else for analysis. Does anyone know of a product that you can export your netflow to that will then in turn export it to multiple destinations (that works well and is easy to use/reliable) ? -Drew _______________________________________________ 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/
