Sounds good. When I consolidate netflow exporters to a single netflow interface, I typically configure a cluster / community (I think they're called clusters now) to ... define / aggregate the traffic therein. Such that:
Router A = 192.168.0.0 exports to 2055 Router B = 192.168.1.0 exports to 2055 ... Router F = 192.168.5.0 exports to 2055 Within ntop GUI, preferences: Cluster.RouterA=192.168.0.0/24 Cluster.RouterB=192.168.1.0/24 ... Cluster.RouterF=192.168.5.0/24 Make sense? If not, it will when you start playing with it and see how ntop sorts traffic and stuff. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jim Rice Sent: Tuesday, March 22, 2011 4:32 PM To: [email protected]; [email protected] Subject: Re: [Ntop] Basic configuration for multiple netflow data Thanks Gary, Makes more sense now. I think I will set up one instance with the border and core routers, each configured with their own network interface. (There's a dozen or so.) Then a second instance for the remainder, combining a few of the less busy routers. I can still drill down to individual customers if need be. _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop <font size="1"> <div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in'> </div> "This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system." </font> _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
