Hi again.

I'd like to use pmaccts on gateway to send netflow information to other machine. On the other machine I install as-stats to read netflow and make it visable by the web side.

I know, that as-stats use the SNMP interface ID to identity the peers (file knownlinks in as-stats). But I don't know how to choose and send the SNMP interface ID by pmacct (nfprobe), of course differet ID sould by send by one instance pmacct (eth0) and differet ID by second instance of pmacct (eth1). Could you give me the way where and how to do it?

I have two interfaces on gateway and two peers with bgp sessions. I have already install pmacct successfuly working with bgp_daemon on the same gateway. The SRC_AS and DST_AS is visible by pmacct -s on the gateway.

Becouse I have two interfaces on gateway I configure and run two instance of pmacct with peering bgp session with 127.0.0.1 and 127.0.0.2 localhost. The pmacct -s look's like both pmaccts (on eth0 and other instance on eth1) works ok, becouse the SRC_AS, DST_AS, SRC_IP, DST_IP and other is true value.

But now, I have trouble to send netflow by nfprobe and read it by as-stats. It seems, that some data is going into the as-stats (the rrd file is created), but on the web side there is no traffic. I think the rrd file have no traffic information.

as-stats use the SNMP interface ID to identity the peers, but I don't know how to choose and send the SNMP interface ID by pmacct (nfprobe). I will be grateful for any advice.


Configuration of one pmacctd (eth0) is:
[ .. ]
daemonize: true
imt_path: /tmp/collect.pipe-eth0
pidfile: /var/run/pmacctd.pid
logfile: /usr/local/pmacct/current/nfacctd-eth0.log
syslog: daemon
interface: eth0
aggregate: src_host, dst_host, src_port, dst_port, src_as, dst_as, proto, tos
plugins: nfprobe, memory
nfprobe_receiver: 192.168.35.35:2000
nfprobe_source_ip: YY.YY.YY.YY
nfprobe_version: 9
nfprobe_engine: 0:2
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
bgp_daemon_msglog: false
plugin_pipe_size: 2000000
plugin_buffer_size: 1000
imt_mem_pools_number: 0
[ .. ]


Configuration of second instance of pmacctd (eth1) is very similar:
[ .. ]
daemonize: true
imt_path: /tmp/collect.pipe-eth1
pidfile: /var/run/pmacctd.pid
logfile: /usr/local/pmacct/current/nfacctd-eth1.log
syslog: daemon
interface: eth1
aggregate: src_host, dst_host, src_port, dst_port, src_as, dst_as, proto, tos
plugins: nfprobe, memory
nfprobe_receiver: 192.168.35.35:2000
nfprobe_source_ip: YY.YY.YY.YY
nfprobe_version: 9
nfprobe_engine: 0:3
pmacctd_as: bgp
bgp_daemon: true
bgp_daemon_ip: 127.0.0.2
bgp_agent_map: /usr/local/pmacct/current/etc/agent_to_peer.map
bgp_daemon_port: 17917
bgp_daemon_msglog: false
plugin_pipe_size: 2000000
plugin_buffer_size: 1000
imt_mem_pools_number: 0
[ .. ]


The agent_to_peer.map file is:
id=91.242.174.1 ip=127.0.0.1


The "knownlinks" as-stats file is:
# Router IP    SNMP ifindex  tag    description  color
YY.YY.YY.YY    2             GTS    GTS          5EA631
YY.YY.YY.YY    3             NETIA  NETIA        E45605


Thank's for any advice.


--
Mark.

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

Reply via email to