Hi.
I am running a pmacctd with netflow export on Linux box. Traffic on
interface where pmacctd is configured to capture is about 500Mbit/s.
After a while pmacct stops exporting netflow data, and CPU utilisation
of two pmacct processes drops to zero.
I would like to report that as a bug and
Hi.
I'd like to use pmacct as netflow collector to get information about
src_as, dst_as and after to use it to know in/out traffic sorted by ASN
(example with as-stats).
I'm trying to get work pmacctd with quagga bgp router. I found in
official examples how to do it on:
On Thu, May 2, 2013 at 4:37 PM, Paolo Lucente pa...@pmacct.net wrote:
If both processes drop to zero CPU utilization then it looks like the
issue might be in what is feeding pmacct. Although pmacctd protects from
interface flaps (ie. if the interface drops, it tries to re-bind) can
you check
It's interesting...
when I telnet localhost 2605 to quagga-bgp and wrote the command from
CLI neighbor 127.0.0.1 remote-as 65530 I got the answer:
% Can not configure the local system as neighbor
but... when I wrote the configuration in /etc/quagga/bgpd.conf and
restart quagga
On 05/02/2013 04:50:16 AM, Timur Irmatov wrote:
Hi.
I am running a pmacctd with netflow export on Linux box. Traffic on
interface where pmacctd is configured to capture is about 500Mbit/s.
After a while pmacct stops exporting netflow data, and CPU
utilisation
of two pmacct processes drops
Hi Timur,
On Thu, May 02, 2013 at 05:06:27PM +0500, Timur Irmatov wrote:
No, links are stable. There is no link down/up events in kernel log.
Both processes just hang. I tried attaching to them via strace, one of
them was stuck in futex call, another one shows up as in
restart_syscall.
OK,
Hi Paolo.
I compile the lastest pmacct. I configure quagga, and the peer session
is active:
[...]
show ip bgp sum
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
127.0.0.1 4 YY 35 234430000 00:13:55 0
...
and of course correct information
Hi Paolo.
I found the mistake in my configuration myself. The reason of that the
0 appears was, that the agent_to_peer.map was wrong mapping.
The correct mapping is:
id= ip=127.0.0.1
Thanks for your previous instructions. Now I can collect the traffic
using netflow.
--
