Thanks for the suggestion on sampling and polling interval.
And the mininet dashboard looks great, will definitely try in a couple of
Thanks a lot.
On Tue, Sep 20, 2016 at 11:39 PM, Peter Phaal <peter.ph...@inmon.com> wrote:
> It looks like you are using Mininet. You might find following real-time
> dashboard useful for visualizing the sFlow data:
> You were originally sampling at 1-in-1. This will impact performance and
> limit the size of network you can build and monitor with Mininet. Backing
> off to 1-in-10 greatly reduces the monitoring overhead. In production OVS
> deployments sampling rates of 1-in-1000 are more reasonable.
> A polling interval of 1 second tends to be inaccurate since the switch
> port counters are only updated every second. Backing off to a 10 second
> polling interval will give less noisy results and also reduce overhead.
> On Sep 20, 2016, at 12:23 PM, Syed Faraz Ali <farazal...@gmail.com> wrote:
> Thanks a lot.
> Just tested and both sFlow collectors are receiving the traffic.
> On Tue, Sep 20, 2016 at 9:06 PM, Peter Phaal <peter.ph...@inmon.com>
>> > On Sep 20, 2016, at 11:18 AM, Ben Pfaff <b...@ovn.org> wrote:
>> > On Tue, Sep 20, 2016 at 08:06:19PM +0200, Syed Faraz Ali wrote:
>> >> Is there a way to configure multiple sFlow instances running on the
>> >> I configured an instance below:
>> >> *ovs-vsctl -- --id=@sflow create sflow agent=eth0 target=\"
>> >> <http://192.168.1.1:6343>\" header=128 sampling=1 polling=1 -- set
>> >> s1 sflow=@sflow*
>> >> However, the instance gets overwritten if i configure another instance
>> >> (though with a different IP and port).
>> >> Multiple sFlow instances are not supported by OVS?
>> > Each bridge can have one sFlow instance.
>> You can send sFlow from the single instance to multiple destinations:
>> sudo ovs-vsctl -- --id=@sflow create sflow agent=eth0 target=[\"
>> 10.0.0.70:6343\",\”10.0.0.72:6343\"] header=128 sampling=10 polling=10
>> -- set bridge s1 sflow=@sflow
discuss mailing list