From: Samuel (hdip@laposte.net)
Date: 03/26/03
Thanks a lot for your help. The sFlow agent was indeed returning incorrect
packet size :
/home/sflow# sflowtool | grep PacketSize
sampledPacketSize 144
sampledPacketSize 144
sampledPacketSize 144
sampledPacketSize 144
I'll try to upgrade our router software as soon as I can, but it's
difficult.. This is our backbone router and it's kind of critical...
Then I hope I'll be able to solve my other problems... For instance, how
nTop determine the VLANs... because it reports our VLANs incorrectly :(
And how can I have correct digits (I guess multiplying by the sampling rate
would give me a rough estimate, but is it accurate enough?)
Thanks !
Samuel.
----- Original Message -----
From: "Marc Lavine" <mlavine@foundrynet.com>
To: "Samuel" <hdip@laposte.net>
Sent: Tuesday, March 25, 2003 12:54 AM
Subject: Re: [sFlow] Questions about the sFlow plugin
> Samuel,
>
> Incidentally, you should be able to confirm my theory by directing the
sFlow samples
> to sflowtool (available here: http://www.inmon.com/sflowTools.htm), and
observing
> whether the received samples are reporting sampledPacketSize as 144.
>
> Regards,
> Marc Lavine
This archive was generated by hypermail 2.1.4 : 03/26/03 PST