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      234430        0    0    0  00:13:55       0
...
and of course correct information about my peers.
[...]

But... using pmacct -s there is "0" as SRC_AS and DST_AS printed:
SRC_AS  DST_AS  SRC_IP  DST_IP  SRC_PORT  DST_PORT ...
0       0       AAA     BBB     35726     41135    ...
^^      ^^
I think, that it should be number of AS??? Would you be so kind and tell me where is the mistake of my configuration?


Configuration of quagga:

router bgp YY
 bgp router-id XXXXX
 neighbor 127.0.0.1 remote-as YY
 neighbor 127.0.0.1 port 17917
 neighbor 127.0.0.1 update-source XXXXX
 ...

Configuration of pmacctd:

daemonize: true
pidfile: /var/run/pmacctd.pid
syslog: daemon
interface: eth0
aggregate: src_host, dst_host, src_port, dst_port, src_as, dst_as, proto, tos
plugins: memory
pmacctd_as: bgp
bgp_daemon: true
bgp_daemon_ip: 127.0.0.1
bgp_agent_map: /usr/local/pmacct/current/etc/agent_to_peer.map
bgp_daemon_port: 17917


In debug of pmacctd there is only BGP_KEEPALIVE received and BGP_KEEPALIVE sent entry.


Regards
--
Mark


W dniu 02.05.2013 13:28, Paolo Lucente pisze:
Hi Marek,

I've just tested against Quagga 0.99.22 and it works no problem peering
with a pmacct instance over 127.0.0.1. I'd suggest upgrading quagga but
it's strange: i did test this back in 2009-2010; 0.99.20.1 is from last
year; 0.99.22 is from 2013. Don't believe something did break temporarly.
This is the piece of config i specifically tested:

router bgp Y
  bgp router-id X.X.X.X
  neighbor 127.0.0.1 remote-as Y
  neighbor 127.0.0.1 port 17917
  neighbor 127.0.0.1 send-community
  !
  address-family ipv4
   [ .. ]
   neighbor 127.0.0.1 activate
   exit-address-family
  !
  address-family vpnv4 unicast
   [ .. ]
   neighbor 127.0.0.1 activate
   exit-address-family
  !

pmacct 0.12 is quite old now - I also suggest upgrading the package to
a more recent (supported) version.

Cheers,
Paolo

On Thu, May 02, 2013 at 12:19:29PM +0200, [email protected] wrote:
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:
        http://wiki.pmacct.net/OfficialExamples
        X. Quickstart guide to setup a NetFlow agent/probe

but when I'm trying to configure quagga it that way:
[...]
router bgp Y
  bgp router-id X.X.X.X
  neighbor 127.0.0.1 remote-as Y
  neighbor 127.0.0.1 port 17917
  neighbor 127.0.0.1 update-source X.X.X.X
[...]

where Y is my AS i get from quagga:
[...]
% Can not configure the local system as neighbor
[..]

quagga version is 0.99.20.1
pmacct version is 0.12.1

Have you any idea how to get pmacct work with quagga?


Regards
--
Mark

_______________________________________________
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists

_______________________________________________
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists


_______________________________________________
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists

Reply via email to