Re: [Ntop] Wrong Traffic Numbers after upgrade from 2.5 to 3.1

2018-02-08 Thread Enrico Kern
Hey, the interface status page does not show any dropped packets or blocked flows. Also --disable-sflow-upscale doesnt help then it shows 1.79 TBit/s for hosts as example. Its like back to the arista problem we had with 2.x which got patched after i provided a dump. On Thu, Feb 8, 2018 at 12:09

Re: [Ntop] Wrong Traffic Numbers after upgrade from 2.5 to 3.1

2018-02-08 Thread Simone Mainardi
Enrico, Can you please verify, under the interface stats page, if there are sFlow drops reported? If you want to try and disable upscale on the latest 3.3, you can try with --disable-sflow-upscale | Ignore sFlow sampling rate (1:1 is used) and thus Simone > On 8 Feb 2018, at 1

Re: [Ntop] Wrong Traffic Numbers after upgrade from 2.5 to 3.1

2018-02-08 Thread Enrico Kern
ok correction, even without upscale it shows wrong numbers. seems like i need to revert to an older version for now :( On Thu, Feb 8, 2018 at 11:32 AM, Enrico Kern wrote: > Same behavior now with the new upgrade from 3.1 to 3.3 ;) And im stil > using upscale-traffic :( > > nprobe --upscale-traff

Re: [Ntop] Wrong Traffic Numbers after upgrade from 2.5 to 3.1

2018-02-08 Thread Enrico Kern
Same behavior now with the new upgrade from 3.1 to 3.3 ;) And im stil using upscale-traffic :( nprobe --upscale-traffic --zmq tcp://*:5557 -i none --collector-port 6343 --verbose 2 --dump-stats -V9 it shows me riddicolous traffic numbers now from my arista switch with speeds of 70Gbit/s on single