Hi Peter,
I tried with sflow enabled on both port and i am able to get samples of
both direction. Thanks.
Openstack uses Linux Bridge to apply iptables security rules.Refer diagram
below
https://ask.openstack.org/en/question/58638/does-neutron-br-int-accepts-nova-instances-sending-vlan-tagged-tr
Ingress means that packets are captured as they are received on a physical or
virtual bridge ports. Patch ports are ignored.
In stand alone mode you typically define a single bridge. However, OpenStack
defines a pair of bridges (br-in and br-ex) and to get full coverage, you need
to enable sFlo
Hi Peter,
Thanks for reply.
What is the difference in vSwitch configuration in Openstack environment
and in standalone use. if i try to enable sflow on OVS-bridge having
following setup. It captures packet in both direction. I think I am not
able to understand exactly what ingress means.
In PC
Hi,
I tried to collect sflow packet on OVS switch in Openstack. But captured
paackets contain only traffic coming out from the VM i.e samples contain
Raw Packet of VM to external network direction only.following command is
used to enable
export COLLECTOR_IP=10.3.5.112
export COLLECTOR_PORT=6343
e
The whole v-switch is modeled as one sFlow data source. To drive that
packets are sampled on ingress at all ports except virtual patch ports
between bridges. You can still extract per-port stats because the ingress
and egress ports are included in the output.
Does this answer your question?
Nei
Sattibabu,
I think it is a per bridge basis configuration.
---
Motonori Shindo
2014-07-17 20:29 GMT+09:00 sattibabu akula :
> Hi,
> Please explain in openvswitch how sflow sampling is happening ?
> Is it complete switch wise[all the ports] or individual port wise ?
> If port
Hi,
Please explain in openvswitch how sflow sampling is happening ?
Is it complete switch wise[all the ports] or individual port wise ?
If port wise could you please explain how to do that ?
Thanks in advance
Regards,
Sattibabu.
___
Yes, setting the sampling-rate to 1-in-1 will give you every packet
header, along with the attendant meta-data. Useful for testing, even if
you would never use it in production.
Neil
--
Neil McKee
InMon Corp.
http://www.inmon.com
On Sun, Feb 9, 2014 at 7:54 PM, Weiyu Liu wrote:
> Hey,
Hey, all.
I am wondering if openVswitch supports sFlow unsampling. Or will setting
the sampling parameter "sampling" in the ovs-vsctl command to 1 let the
sflow agent get every packet through the monitored interface? I will really
appreciate if you can give me some suggestion.
Thanks for the reference. The paper is behind the IEEE pay wall, so I thought I
would give a quick summary.
The authors compare CPU overhead due to NetFlow and sFlow on Open vSwitch as
they vary link speeds and sampling rates. iperf is used as the traffic
generator. The paper contains graphs
On Thu, Jun 13, 2013 at 10:32:15AM -0700, Rui Vaz wrote:
> I read this article about sFlow versus NetFlow and it states that:
>
> With sFlow monitoring, the *decode*, *hash*, *flow cache* and
> *flush*functionality are not implemented on the switch.
>
> With NetFlow this operations are performed
Hi everyone,
I read this article about sFlow versus NetFlow and it states that:
With sFlow monitoring, the *decode*, *hash*, *flow cache* and
*flush*functionality are not implemented on the switch.
With NetFlow this operations are performed in the switch, moreover there's
a flowcache (which can
Hi, I have already posted same question on sflow disc. group. but it seems
that nobody know the answer.
so is it possible to somehow done mapping between ports of OvS (I'm running
freeBSD) and sflow ifIndex?
On sFlow discussion group they suggested me to go with snmget request, but
it seems to me
Thank you so much Peter. It worked and I ll definitely take a look at the
article you sent. It looks exactly what I was looking for.
Again thanks for the help.
Cheers.
Mehmet Fatih
On Thu, May 30, 2013 at 7:08 PM, Peter Phaal wrote:
> You need to give the entire command in one line, e.g.
>
>
You need to give the entire command in one line, e.g.
sudo ovs-vsctl -- --id=@sflow create sflow agent=eth0
target=\"127.0.0.1:6343\" sampling=10 polling=20 -- -- set bridge s1
sflow=@sflow
or, if you have multiple bridges:
sudo ovs-vsctl -- \
--id=@sflow create sflow agent=eth0 target=\"127
Hi,
I am trying to use sFlow on ovs created in mininet.
Following the config cookbook for sFlow in:
http://openvswitch.org/support/config-cookbooks/sflow/
Here is the bridge log for ovs:s1
_uuid
thanks, it's works... :)
2013/5/23 Ben Pfaff
> On Thu, May 23, 2013 at 01:03:25PM +0200, Marin Krznarević wrote:
> > hello I have a problem with sflow configuration, it keeps returning me
> that
> > there is no reference in db
> >
> > does anybody know where could be the problem?
>
> You used @
On Thu, May 23, 2013 at 01:03:25PM +0200, Marin Krznarević wrote:
> hello I have a problem with sflow configuration, it keeps returning me that
> there is no reference in db
>
> does anybody know where could be the problem?
You used @s in one place and @sflow in the other.
___
Try making the "@" names the same. You have one as "@sflow" and the other as
"@s".
--Justin
On May 23, 2013, at 4:03 AM, Marin Krznarević
wrote:
> hello I have a problem with sflow configuration, it keeps returning me that
> there is no reference in db
>
> does anybody know where could be
hello I have a problem with sflow configuration, it keeps returning me that
there is no reference in db
does anybody know where could be the problem?
here is the output:
ovs1# ovs-vsctl -- --id=@sflow create sflow agent=eth0 target=\"
192.168.19.129:6343\" header=128 sampling=64 polling=10 -- --
The Open vSwitch team is pleased to announce the addition of sFlow(R). sFlow
is an industry standard for monitoring high-speed switched networks. It uses
sampling to collect statistics from a device in a network. More information on
sFlow is available here:
http://sflow.org/
The Ope
There are some common pitfalls to avoid even in the low-level
sampling, so feel free to ping me if you have any doubts.
(For example, if you are queueing the samples for processing later
then make sure you use a low priority queue: separate from the queue
you use for critical events like
Terrific! Thank you very much. This will make it much easier to add
sFlow to the project. When we have an implementation working, we'll
definitely take you up on your offer to help us test it.
By the way, I've already updated the bullet point on our project page
to say "sFlow(R)" to keep
Justin,
Please accept this email as written confirmation that you may use and
adapt the source code for the InMon Virtual Probe (http://inmon.com/
products/virtual-probe/index.php) for the implementation of an sFlow
agent in the "Open vSwitch" project (http://openvswitch.org/) under
the te
24 matches
Mail list logo
