Thanks for the response and especially the link. If I'm reading that thread correctly, it seems that the sampling_rate option in nfacct will only work if I use a non-template based flow export like Netflow v5.
I'll double check with the router folks on Monday but my understanding so far is that they can only export IPFIX to one destination with the version of Junos we've got running. Thanks again, -Paul > On Feb 21, 2016, at 4:03 PM, Paolo Lucente <[email protected]> wrote: > > > Hi Paul, > > Your understanding is correct; please note that by doing so you > will achieve flow sampling at the collector (as opposed to packet > sampling at the router). Although slightly different, please read > a few thoughts on flow sampling in this recent thread: > > https://www.mail-archive.com/[email protected]/msg02974.html > > If possible, i would recommend to export twice from the routers, > one export with a 1:1 sampler for your colleagues, the other with > the sampler matching your needs for you. > > Cheers, > Paolo > > On Sat, Feb 20, 2016 at 03:35:43AM +0000, Paul Lockaby wrote: >> Hello everyone, >> >> The folks that maintain the routers want to start exporting IPFIX at a 1:1 >> ratio so they can feed it into their network monitoring system. I, on the >> other hand, can't process 1:1 quickly enough to aggregate billing >> information in a timely manner. I *think* the "sampling_rate" option will >> allow nfacctd to sample the incoming data and write CSV files that are >> sampling of what is coming in, if I'm reading the docs correctly. But I want >> to make sure that it does by asking around to see. Am I reading the docs >> correctly? >> >> Thank you, >> -Paul >> _______________________________________________ >> 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
