Hi guys , I would like to ask you if you have ever had to do a little tunning of the fprobe sensor. Im running fprobe on a interface with 2.2gbps max traffic but in the nfsen graphs there is 1.6gbps max. My feeling is than fprobe is missing some data. I have seen flags to run fprobe that can change its behaviour/performance but I not sure how to beging testing them.
Currently Im runnign: [root@mdz]# /sbin/fprobe -i eth13 -fip -n7 172.24.3.12:9995 -a 172.24.3.7 Also Im not sure about the -fip flag (Im using like this since it is working on another machine). Some of the flags I would try: -s <seconds> How often scan for expired flows [5] -g <seconds> Fragmented flow lifetime [30] -d <seconds> Idle flow lifetime (inactive timer) [60] -e <seconds> Active flow lifetime (active timer) [300] -n <version> NetFlow version for use (1, 5 or 7) [5] -x <id>[:<id>] Workaround for SNMP interfaces indexes [0] -b <flows> Memory bulk size (1..4294967295) [10000] -m <kilobytes> Memory limit (0=no limit) [0] -q <flows> Pending queue length [100] -B <kilobytes> Kernel capture buffer size [0] -r <priority> Real-time priority (0=disabled, 1..99) [0] -t <B:N> Produce <N> nanosecond delay after each <B> bytes sent [0:0] -S <bytes> Snaplen [256] -K <bytes> Link layer header size Any ideas ? Thanks in advance. Leandro. ------------------------------------------------------------------------------ Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development environment. Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140 _______________________________________________ Nfsen-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
