Re: [pmacct-discussion] Centralizing data from multiple nfacct collectors

2017-01-05 Thread Alex
I have a running setup with remote sites having pmacct + mysql which aggregates the data nightly and pushes them to a central hub as json files. Alex On January 5, 2017 5:42:45 PM GMT+02:00, Yann Belin wrote: >Thanks all! I spent a couple of hours trough RabbitMQ

Re: [pmacct-discussion] Centralizing data from multiple nfacct collectors

2017-01-05 Thread Karl O. Pinc
On Thu, 5 Jan 2017 10:57:01 +0100 Yann Belin wrote: > Not strictly a pmacct/nfacct question, but I was wondering if anyone > ever built a similar setup. Not strictly a pmacct/nfacct response, but thought I'd comment anyway. ;-) > A central side would then gather > data

Re: [pmacct-discussion] pmacct / sflow / bgp

2017-01-05 Thread Paolo Lucente
Hi Cedric, 43874 is the IANA-assigned enterprise number of pmacct. You have that as part of your sFlow packets since tag or tag2 are part of your config directive aggregate. Tags is pmacct-specific information and hence it's encoded with the pmacct enterprise number. I believe you have two ways

Re: [pmacct-discussion] Unable to specify "bgp_ip=::1" in bgp_agent_map

2017-01-05 Thread Paolo Lucente
Hi Charlie, Thanks for following-up. I've also updated the docs with your example as this or similar cases popped up a few times during last year: https://github.com/pmacct/pmacct/commit/b3a5dd564983119eba7a481ad571a9d462922897 Cheers, Paolo On Thu, Jan 05, 2017 at 10:24:10AM +, Charlie

Re: [pmacct-discussion] Centralizing data from multiple nfacct collectors

2017-01-05 Thread Paolo Lucente
+1 on this. On Thu, Jan 05, 2017 at 10:10:40AM +, Charlie Smurthwaite wrote: > On 05/01/17 09:57, Yann Belin wrote: > >the collectors have to store > >(temporarily) their data locally. A central side would then gather > >data from the different locations, and store the that data in a DBMS >

Re: [pmacct-discussion] Unable to specify "bgp_ip=::1" in bgp_agent_map

2017-01-05 Thread Charlie Smurthwaite
Hi, Just to confirm, the following configuration works perfectly, using separate router IDs for each protocol, and identifying them by router id in the agent map: bgp_ip=4.0.0.1 ip=0.0.0.0/0 filter='ip or (vlan and ip)' bgp_ip=6.0.0.1 ip=0.0.0.0/0 filter='ip6 or (vlan and ip6)' Now

Re: [pmacct-discussion] Centralizing data from multiple nfacct collectors

2017-01-05 Thread Charlie Smurthwaite
On 05/01/17 09:57, Yann Belin wrote: the collectors have to store (temporarily) their data locally. A central side would then gather data from the different locations, and store the that data in a DBMS (currently thinking of MySQL, but I'm not married to it). Have you considered using a