Paolo Lucente <[email protected]> wrote
Thu, 17 Jan 2013 20:10:46 +0000:

| > For info, SRC_AS and DST_AS are both 0 for all entries when
| > nfacctd_as_new is set to 'bgp', which I guess indicates that nfacctd
| > realises that its BGP info is bad or nonexistent. (Setting
| > nfacctd_as_new to 'fallback' gives good result, presumably based on
| > netflow data.)
| 
| Correct. Essentially i grasp all BGP-related primitives (src_as, dst_as
| and as_path) on which you are aggregating are being left empty, "^$" being
| an internal pmacct representation for empty, when sourcing data from BGP.
| Is the IP address being used to export NetFlow the same of either the BGP
| router-ID or the BGP source-address? If not, that explains: the correlation
| is not made possible automagically - you might opt for a bgp_agent_map map;
| if all is good that side of the things then you should inspect what is
| actually sent to pmacct via BGP - with the bgp_daemon_msglog described
| above. Give it a try and let's take it from there.

Thanks.

Well, "something happened" and now I see _some_ entries with a proper
AS_PATH. (That's great, except I don't know what has changed. Sorry.)

The missing paths are probably because we're lacking the mapping for
other flow sources -- the BGP feed comes from a router acting as an RR
while the netflow feeds come from several routers (including the one
nfacctd is peering with).

FWIW, while playing around with mappings I managed to provoke segfaults
in the memory plugin:

  nfacctd[21723]: segfault at 9d49018 ip 0809aed2 sp bff11730 error 4 in 
nfacctd[8048000+a3000]

It's strictly related to invocations of `pmacct -s'. Haven't had the
chance to hunt it down yet (gdb and threaded programs, how does it work?;))
but let me know if you're interested in more details on this. We're running
recent CVS.

I'll get back on the mapping issue if I fail to figure out how to make
it work properly. Next week.

-- 
Linus

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

Reply via email to