Hey Cedric, On Fri, May 12, 2006 at 12:19:44PM +0200, Cédric Delaunay wrote:
> aggregate[in]: src_host,dst_host > aggregate[out]: src_host,dst_host I would correct the above few lines in: aggregate[in]: dst_host aggregate[out]: src_host This is very likely to stop the error message you are receiving (which means the memory table has reached its upper bound - play with imt_mem_pools_size, imt_mem_pools_number configuration directives to enlarge/tune it, if required). Furthermore, it's a more safe setting, as you should not be interested by the remote peers your local boxes connect to, isn't it ? For some more bits about this argument, divert your eyes to Q5/Q6 points of FAQS. > I first tried to wiew with pmacct the network use. > pmacct -N x.x.0.0 -c src_net -p /tmp/out.pipe gives me "0". > But it works fine for a computer : > pmacct -N x.x.131.29 -c dst_host -p /tmp/in.pipe returns 944470 bytes If you wish to have stats for your subnet, then you need to instruct a couple more memory plugins: the client tool is unable to perform any sub-aggregation of data. Perhaps you wish to adjust your configuration as follows: === nfacctd.conf === ... ! plugins: memory[in_host], memory[out_host], memory[in_net], memory[out_net] ! aggregate[in_host]: dst_host aggregate_filter[in_host]: dst net x.x.0.0/16 imt_path[in_host]: /tmp/in_host.pipe ! aggregate[out_host]: src_host aggregate_filter[out_host]: src net x.x.0.0/16 imt_path[out_host]: /tmp/out_host.pipe ! aggregate[in_net]: dst_net aggregate_filter[in_net]: dst net x.x.0.0/16 imt_path[in_net]: /tmp/in_net.pipe networks_file[in_net]: /path/to/networks.lst ! aggregate[out_net]: src_net aggregate_filter[out_net]: src net x.x.0.0/16 imt_path[out_net]: /tmp/out_net.pipe networks_file[out_net]: /path/to/networks.lst ! ... === === networks.lst === x.y.z.a/24 x.y.z.b/24 x.y.z.c/24 x.y.z.d/23 ... === This way, in_host/out_host will hold per-host traffic data; in_net/out_net will hold per-subnet traffic data. Pay few extra bytes for an overral resource savy solution (often sub/re-aggregations are really crunchy). > My problem is now that i need informations about many sub-networks and > machines (dns, dhcp ...). Is there a way to script graphs creation (from a > conf file or oter) ? AFAIK, there isn't anything pre-cooked. Don't know whether on the Cacti side there is anything generic to load configuration in batches. It *should* be easy stuff in the case Cacti saves profiles the SQL/XML way (which could be the case). Perhaps having some useful pointer about this, i may help .. Cheers, Paolo _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
