I managed to get this updated now. It looks ok now with numbers but i had
to remove the upscale flag. With upscale flag it only shows a few kilobytes
instead of gigabits, so kind of reversed ;) But numbers seem to match
actual traffic now
On Wed, Mar 7, 2018 at 11:16 AM, Enrico Kern wrote:
> no
no yet, will do later today. Thanks for the reminder. Wasnt aware new
packages are already up
On Wed, Mar 7, 2018 at 10:46 AM, Simone Mainardi wrote:
> Enrico, I was wondering if you had the chance to try new packages. You can
> just run an upgrade of your package manager to get the latest versi
Enrico, I was wondering if you had the chance to try new packages. You can just
run an upgrade of your package manager to get the latest version...
Thanks
Simone
> On 19 Feb 2018, at 20:10, Enrico Kern wrote:
>
> Sure. Tell me when new packages are out and i give it a go.
>
> Am 19.02.2018 1
Sure. Tell me when new packages are out and i give it a go.
Am 19.02.2018 19:39 schrieb "Simone Mainardi" :
Enrico,
We have made some fixes. Can you please hold a couple of hours (a new build
is in progress) and test again? If you still experience issues, please
consider sending us an sFlow capt
Enrico,
We have made some fixes. Can you please hold a couple of hours (a new build is
in progress) and test again? If you still experience issues, please consider
sending us an sFlow capture or access to the machine.
Thanks,
Simone
> On 8 Feb 2018, at 12:30, Enrico Kern wrote:
>
> Hey,
>
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
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
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
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
ah that did the trick. Thank you
On Thu, Jun 8, 2017 at 11:48 AM, Simone Mainardi wrote:
> Enrico,
>
> If I remember correctly, your Arista switches are sending sFlow. So please
> try to add nProbe option* --upscale-traffic* that will adjust the traffic
> on the basis of sFlow sampling rates.
>
Enrico,
If I remember correctly, your Arista switches are sending sFlow. So please
try to add nProbe option* --upscale-traffic* that will adjust the traffic
on the basis of sFlow sampling rates.
Simone
On Thu, Jun 8, 2017 at 10:52 AM, Enrico Kern
wrote:
> Hi all,
>
> yesterday i upgraded our n
Hi all,
yesterday i upgraded our ntop and nprobe from 2.5 to 3.1. Now it shows
absolute wrong traffic numbers. As example we have machines constantly
doing 4 to 10 gbit/s and all it shows now for all hosts is 2 kbit/s up to 1
Mbit/s thats all.
We use normal nprobe where our arista switches send d
12 matches
Mail list logo