Hi Steve,
As Tim was mentioning you can use 'sampling_rate' with a fixed sample
rate (not 'sample_rate'); this will make pmacct sample for you. In case
you are sampling outside pmacct, you can supply this info via, say,
pmacctd_ext_sampling_rate so that nfprobe will include such value in
the
If the probe is doing sampling, you can have pmacct re-normalize sampling
via either a static sampling value, or via the flow/ipfix information that
tells it how it was sampled..
sample_rate:
sample_map:
(s|n|p|u)facctd_renormalize:true
If you're using a tap that samples traffic, you can tell
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
1 on 1 ratio is a crisis to database in busy data center. You'll need to define
a level of granularity . And yes sampling_rate is for that purpose.
Sent from my ASUS
原始郵件
寄件者：Paul Lockaby
傳送日期：Sat, 20 Feb 2016 11:46:02 +0800
收件者：pmacct-discussion@pmacct.net
Hi Steve,
Your config looks good. I suggest to check the NetFlow v9 export at
your router. One popular issue is that the options packet to specify
the sampling rate are not exported. Besides, especially on slightly
older software releases (i here refer particularly to IOS and JunOS,
feel to
