Hi, I'd say limit on IP addresses that can be accounted of is only imposed by resources available (memory) and, when using memory tables (which is your case), the imt_mem_pools_number setting (see CONFIG-KEYS for more details).
I see a couple of issues with your config: * quite large plugin_buffer_size setting; i just wonder if you had to come up to such huge buffers because of packet loss. If this is the case then OK; otherwise, if traffic rate does not justify it i would advice to scale it down, say, to 20KB or 100KB. Buffering too much has also negative impact. * If i get correctly you want to have a two tiered approach: you want to account for /24 subnets (so that you have a more compact overview of what's going on) and for /32 IP addresses so that you can drill down who is actually generating traffic within a certin /24. If this is the case, i would recommend you to re-write your config as follows: ... networks_file: /etc/pmacct/networks.def plugins: memory[net_in], memory[net_out], memory[host_in], memory[host_out] aggregate[net_in]: dst_net aggregate[net_out]: src_net aggregate[host_in]: dst_host aggregate[host_out]: src_host imt_path[net_in]: /tmp/net_in.pipe imt_path[net_out]: /tmp/net_out.pipe imt_path[host_in]: /tmp/host_in.pipe imt_path[host_out]: /tmp/host_out.pipe ... And in the networks.def (which definition is shared among all the plugins) you put only the /24 ranges - scrap all the /32 definitions. I guess the rest should be pretty much intuitive. Cheers, Paolo On Mon, Jul 19, 2010 at 02:36:56PM +0000, Jose Joaquin Anton Herrerias wrote: > Hi everyone, > > I'm new in pmacctd and i using pmacctd with cacti for drawing > graph of the network, now I want to monitorize the traffic of all ips but are > a lot, 2040 ips and the complete range for give a overall view of the range > traffic. > > But I have a trouble, I configure the network.def with all > ips (/32) and all ranges (/24) and I have my pmacctd.conf with: > > ! > ! pmacct: In + Out > ! > debug: false > daemonize: true > interface: eth1 > plugin_buffer_size: 2048000 > plugin_pipe_size: 2048000000 > networks_file: /etc/pmacct/networks.def > plugins: memory[in], memory[out] > aggregate[in]: dst_net > aggregate[out]: src_net > imt_path[in]: /tmp/in.pipe > imt_path[out]: /tmp/out.pipe > > But the pmacct only store data over 232 ips. How I can do to > store data for all ips?? > > Best Regards. > > > Jose Joaqu?n Ant?n Herrer?as > * jan...@abserver.es<mailto:jan...@abserver.es> > ----------------------------------------------------------------------------------------------------------------------------------------- > Access Basic Server S.L. Elche Parque Industrial. C/Galileo Galilei, 12. > 03203 Elche (Alicante). > Telf. +34 96 568 29 04 / 902 380 380 Fax. +34 96 568 35 30 > > [cid:image003.jpg@01C9FE53.D30E9A20]<http://www.abserver.es/> > > Cl?usula de confidencialidad: Este mensaje se dirige exclusivamente al > destinatario consignado. Puede contener informaci?n confidencial, > de nuestra propiedad o legalmente protegida. Si usted no es el destinatario, > le informamos que cualquier acceso, divulgaci?n, copia o distribuci?n > de la informaci?n, as? como cualquier acci?n u omisi?n realizada con base a > la misma, queda prohibida y puede ser ilegal. En caso de haber > recibido este mensaje por error, le rogamos nos lo reenv?e y notifique > inmediatamente, borrando toda copia de su sistema. Gracias. > _____________________________________________________________________________________________ > ? Antes de imprimir este mensaje, aseg?rese de que es necesario. Proteger el > medio ambiente est? en nuestra mano. > Piensa en global, act?a en local. > > _______________________________________________ > pmacct-discussion mailing list > http://www.pmacct.net/#mailinglists _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
