Re: [ovs-discuss] Support for in/out interfaces in IPFIX

2016-09-21 Thread Peter Phaal
sFlow-RT is a programmable external flow cache that handles the packet parsing. It can be programmed to export IPFIX records. http://blog.sflow.com/2016/05/sflow-to-ipfix.html # start the flow cache docker run -p 6343:6343/udp -p 8008:8008 -p 4

Re: [ovs-discuss] Multiple sFlow instances in Open vSwitch

2016-09-20 Thread Peter Phaal
> On Sep 20, 2016, at 11:18 AM, Ben Pfaff 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 OVS? >> I configured an instance below: >> >> *ovs-vsctl -- --id=@sflow create sflow agent=eth0 target=\"19

[ovs-discuss] Flow analytics with Mininet

2016-05-20 Thread Peter Phaal
Enabling sFlow using ovs-vsctl can be tricky. The following article describes simple Mininet --custom sflow.py script that automatically enables sFlow on all switches and exports the metadata needed to relate the sFlow measurements to the topology: http://blog.sflow.com/2016/05/mininet-flow-ana

Re: [ovs-discuss] Collecting data with sFlow

2016-04-19 Thread Peter Phaal
What configuration commands did you use? Did you enable sFlow on each of the bridges? The following Cookbook describes how to configure sFlow: http://openvswitch.org/support/config-cookbooks/sflow/ The polling and sampling settings in your

Re: [ovs-discuss] Ben pfaff Presentation

2015-11-24 Thread Peter Phaal
Ben gave a talk that covered similar material to the Bay Area Network Virtualization Group that was videotaped: https://www.youtube.com/watch?v=T8ssmkK8s0c > On Nov 24, 2015, at 8:18 AM, Ben Pfaff wrote: > > On Tue, Nov 24, 2015 at 07:12:52PM +053

Re: [ovs-discuss] Ports in sflow samples from OVS

2015-05-15 Thread Peter Phaal
tual switches (s1 , > s2) > I again add the sflow agents. I want to sort the samples based on which > switch they are received from. > I am thinking agentSubId & sourceId fields are the ones i must focus on. > However again, is there anyway to map > the sflow sample to the

Re: [ovs-discuss] Ports in sflow samples from OVS

2015-05-14 Thread Peter Phaal
You can use ovs-vsctl to dump the naming information for the ports and extract the mapping between the SNMP ifIndex that sFlow uses to identify ports and the OpenFlow port number / name that the controller uses to identify ports: mininet@mininet-vm:~$ sudo ovs-vsctl --format json --columns name

Re: [ovs-discuss] Sflow packet samples in Openstack environment on OVS bridge

2015-04-22 Thread Peter Phaal
p device to qemu to > launch VM. > > In compute node > VM-->tap-->Linux Bridge --veth pair-->br-int(sflow enabled)-veth pair->br-tun > > > Actually We can not use br-ex to enable flow because sflow sample contain GRE > header. > > > Than

Re: [ovs-discuss] ECMP configuration on openvswitch

2015-04-19 Thread Peter Phaal
n from > switch? I presumed that the default rule for sending packets to controller is > only for data packet and not control packets. Kindly correct me if i am wrong. > > OpenDayLight version used is Hydrogen. > > Thanks, > Lavanya > > On Wed, Mar 18, 2015 at

Re: [ovs-discuss] ECMP configuration on openvswitch

2015-03-18 Thread Peter Phaal
ity=100 idle_timeout=0 hard_timeout=0 actions=goto_table:1 ']) > > Thanks, > Lavanya > > > On Sun, Mar 15, 2015 at 9:17 AM, Peter Phaal <mailto:peter.ph...@inmon.com>> wrote: > The leafandspine.py script described in the following article provides an > e

Re: [ovs-discuss] ECMP configuration on openvswitch

2015-03-15 Thread Peter Phaal
this approach to work. There are efforts to support hybrid openflow in OpenDaylight http://blog.sflow.com/2014/09/hp-proposes-hybrid-openflow-discussion.html Peter Phaal InMon Corp. > On Mar 14, 2015, at 11:42 PM, Lavanya M.K wrote: > > Hi All, > > I want to have static ECM

Re: [ovs-discuss] OVS NetFlow export - is there passive timeout?

2014-11-06 Thread Peter Phaal
Martin, One way to understand the difference between sFlow and NetFlow monitoring is to view them as different stages in the measurement pipeline. With NetFlow the flow cache exists on the switch and with sFlow the flow cache is external. With an external flow cache, you can choose your own fl

Re: [ovs-discuss] Detecting Elephant flow.

2014-07-28 Thread Peter Phaal
One way to detect Elephant flows on OVS is to enable sFlow on OVS. The following article provides an example of Elephant flow detection and marking using OVS / Mininet: http://blog.sflow.com/2014/04/mininet-integrated-hybrid-openflow.html There have been some experiments described using patched

Re: [ovs-discuss] Using OVS+Host sFlow to monitor network traffic

2013-12-01 Thread Peter Phaal
Your sampling rate is 1-in-64 packets. A few pings aren’t likely to register. You should try larger flows with ping -f or iperf. The following article uses iperf to demonstrate how sFlow is used to detect large flows: http://blog.sflow.com/2013/06/large-flow-detection.html The article also sho

Re: [ovs-discuss] Using OVS+Host sFlow to monitor network traffic

2013-12-01 Thread Peter Phaal
The Host sFlow agent ships with the sflowovsd daemon that automatically configures sFlow on Open vSwitch to match the Host sFlow settings (i.e. picking up sampling rates, polling intervals, sFlow collectors, ports etc). Just run the following command and you should start receiving sFlow from al

Re: [ovs-discuss] hot topic for my thesis

2013-11-25 Thread Peter Phaal
Installing Mininet on your laptop is a great way to experiment with OVS / SDN: http://mininet.org/ The Frenetic project (a collaboration between Princeton and Cornell) is a very interesting approach to building controllers. http://www.frenetic-lang.org/ The following article describes some exp

Re: [ovs-discuss] sFlow versus NetFlow

2013-06-19 Thread Peter Phaal
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

Re: [ovs-discuss] sFlow config of ovs in mininet

2013-05-30 Thread Peter Phaal
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

Re: [ovs-discuss] SR-IOV and storage over OVS

2013-04-05 Thread Peter Phaal
I can't speak to the performance impact of running storage traffic over OVS. We have storage running over OVS in our small XenServer pool and haven't seen any ill effects, but that isn't much of a test. However, the sFlow instrumentation in OVS gives useful visibility into storage activity, fo

Re: [ovs-discuss] NetFlow in openvswitch

2013-02-04 Thread Peter Phaal
What are your requirements for NetFlow version 9? If you are need visibility into non-IPv4 traffic (mac addresses, IPv6 addresses, FCoE, AoE etc) then you might want to look at OVS sFlow: http://blog.sflow.com/2011/10/comparing-sflow-and-netflow-in-vswitch.html If you are interested in using f

Re: [ovs-discuss] Not seeing any data in the sFlow trend

2012-11-07 Thread Peter Phaal
I don't know anything about mininet or how it uses OVS, but it sounds like there are issues with the sFlow packets that are being generated. A good starting place for diagnosing the problem would be to use sflowtool to print the contents of the sFlow datagrams: http://blog.sflow.com/2011/12/sfl

Re: [ovs-discuss] monitoring traffic VM using sflow

2012-10-24 Thread Peter Phaal
The sFlow reported utilization numbers should be accurate for the physical NICs. There is no well defined link capacity for a vNIC and so the utilization numbers are meaningless (I believe the Open vSwitch sFlow implementation reports a nominal 100Mbits/s capacity for vNICs). When examining v

Re: [ovs-discuss] Topology discovery in ovs

2012-06-04 Thread Peter Phaal
Hi All, The original question was about L2 topology discovery. One of the differences between sFlow and NetFlow is that sFlow operates at layer 2 (reporting layer 2 interfaces and MAC addresses) and NetFlow typically operates at layer 3 (reporting router (VLAN) interfaces and IP addresses). Con

Re: [ovs-discuss] [BUG] multi-/broadcast counter, sFlow

2012-04-24 Thread Peter Phaal
Chris, The sFlow standard indicates unknown values as follows: The following values should be used for fields that are unknown (unless otherwise indicated in the structure definitions). - Unknown integer value. Use a value of 0 to indicate that a value is unknown. - U

Re: [ovs-discuss] Does OVS monitors incoming traffic onto the VMs?

2012-02-08 Thread Peter Phaal
Hi Marcos, OVS supports sFlow and NetFlow for traffic monitoring. The following article describes how to configure sFlow and NetFlow and provides a comparison using free real-time traffic monitoring tools: http://blog.sflow.com/2011/10/comparing-sflow-and-netflow-in-vswitch.html Peter On Feb

Re: [ovs-discuss] Open vSwitch 1.1.1 Available

2011-06-15 Thread Peter Phaal
On Wed, Jun 15, 2011 at 1:15 PM, Ben Pfaff wrote: > On Tue, Jun 14, 2011 at 08:03:38AM -0700, Peter Phaal wrote: >> The porting guide shows an "ofproto provider" block in the first diagram, >> which I take to be the ofproto plugin? This block is dropped in the second

Re: [ovs-discuss] Open vSwitch 1.1.1 Available

2011-06-14 Thread Peter Phaal
On Jun 13, 2011, at 11:51 PM, Justin Pettit wrote: > >> I guess I am not clear where in the ofproto -> ofproto-dpif -> dpif -> dpif >> provider -> datapath stack the decision to use exact_match or keep wildcards >> is made. It seems like it would be a good idea to try and push that decision >

Re: [ovs-discuss] Open vSwitch 1.1.1 Available

2011-06-10 Thread Peter Phaal
ow greater code re-use. I am also curious as to how you see the functional split with SR-IOV network adapters and Open vSwitch on hypervisors. Peter > > --Justin > > > On Jun 10, 2011, at 9:47 AM, Peter Phaal wrote: > >> On Sun, May 29, 2011 at 11:35 PM, Justin Pet

Re: [ovs-discuss] Open vSwitch 1.1.1 Available

2011-06-10 Thread Peter Phaal
On Sun, May 29, 2011 at 11:35 PM, Justin Pettit wrote: > > We have seen an interest from vendors in bringing Open vSwitch's features to > hardware switches.  To that end, our current "master" branch will be the > basis of a 1.2.x series of releases. The focus of which is a new datapath > abstra

Re: [ovs-discuss] Some questions on ovs

2011-01-07 Thread Peter Phaal
On Jan 7, 2011, at 10:31 AM, Daniel Tiron wrote: > Yes, I have to get the packets into the userspace. But I have to do this > anyway because I need to process the data with a monitoring tool called > vermont [1]. > > [1] http://vermont.berlios.de/ > In addition to span port monitoring, there a

Re: [ovs-discuss] Question about configuration ovs-ctl and routing

2010-12-20 Thread Peter Phaal
It sounds like you are simply interested in obtaining traffic accounting data from different services running on a host. If you aren't using virtual machines, then it isn't clear why you would need a vswitch. There are a number of traffic accounting options for Linux servers based on netfilter

Re: [ovs-discuss] about monitoring openvswitch traffic

2010-11-12 Thread Peter Phaal
The easiest way to link the ifIndex numbers reported by sFlow in the Open vSwitch (OVS) with virtual machine host names is to run the Host sFlow agent on Dom0. As well as simplifying the configuration of sFlow on OVS, the Host sFlow agent uses the xenstat library to report on virtual machine per

[ovs-discuss] Open vSwitch performance monitoring

2010-10-09 Thread Peter Phaal
Hi, The Host sFlow agent is the easiest way to manage Open vSwitch sFlow configuration, as well as providing performance monitoring of the hypervisor and virtual machines. http://host-sflow.sourceforge.net/ The following examples use sFlowTrend to demonstrate the visibility that Host sFlow/Ope

Re: [ovs-discuss] Re : Re : Re : OvS 1.0.0 Compile error on fedora 13

2010-05-21 Thread Peter Phaal
Another factor to consider as you look at your networking options is visibility into network traffic. The Open vSwitch includes embedded traffic monitoring and would give you visibility into all traffic between VMs and from VMs to the outside world: http://blog.sflow.com/2010/05/configuring-ope