Hi Yossi, Sure, the divide and conquer approach is valid. I'm suggesting this idea essentially every time i present pmacct around. See, for example, page #33 of the following PDF: http://www.pmacct.net/ripe61-planning-v1.pdf
On a side note, the parameter on which the collector should be scaled upon in terms of NetFlow is the arrival packet rate, ie. in Mbps, rather than the amount of routers exporting NetFlow data. Such metric should be readily available if NetFlow is already leveraged in a backbone. Alternatively the empirical approach, ie. trialling the software on some spare hardware, is typically rewarding without lots of efforts. Cheers, Paolo On Wed, Jan 25, 2012 at 12:53:38AM -0800, yossi ozani wrote: > Hi... > > I recently installed netflow(nfacctd) for receiving netflow packets from my > router - and it works great!! thanks to Paolo which advice to disabling > 'iptables' firewall ;) > I was wondering if I would have huge network devices(routers) which sends > netflow packets, late say: 50 routers. > Is it advisably good idea to use several netflow deamons(nfacctd) to reduce > overload??? .e.g: 2 deamons each listen to 25 routers > > Best Regards > Yossi > _______________________________________________ > pmacct-discussion mailing list > http://www.pmacct.net/#mailinglists _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
