I just wanted to confirm for the list that the RR client wasn't configured and this was the culprit.
Thanks, Steve On Sat, Feb 6, 2016 at 3:14 PM, Paolo Lucente <[email protected]> wrote: > Hi Steve, > > Is it possible nfacctd is not configured as RR client on the routers and > hance it is getting only partial routes? > > Cheers, > Paolo > > On Fri, Feb 05, 2016 at 01:36:49PM -0700, Steve Dodd wrote: > > I?m having an issue where a large number of flows aren?t populating with > > src_as/dst_as information. Here?s my conf file: > > > > daemonize: true > > !debug: true > > logfile: /var/log/nfacctd.log > > aggregate[in]: src_host, src_as > > aggregate[out]: dst_host, dst_as > > plugins: memory[in], memory[out] > > nfacctd_port: 2055 > > bgp_daemon: true > > bgp_daemon_ip: 199.167.38.86 > > bgp_daemon_port: 179 > > bgp_daemon_max_peers: 20 > > nfacctd_as_new: bgp > > > > I have verified that the IP addresses supplying the netflow export are > the > > same as the BGP peering session, which was indicated might be an issue > in a > > previous thread. Does anyone have any pointers or suggestions? > > > > Thanks, > > Steve > > > > > > > _______________________________________________ > > 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
