I find it strange that my mininet version is 2.1 where my ovs version 1.10,
in any case i will grab the latest vm! :)
Thank you very much for your helpful and detailed responses.
On Fri, May 15, 2015 at 5:23 PM, Peter Phaal wrote:
> I believe the ifIndex was added as an ovs-vsctl list option in
I believe the ifIndex was added as an ovs-vsctl list option in OVS 2.0+ (which
is included in the latest Mininet VM). Mininet 2.0 is useful for performance
studies since it it lets you set link speeds and queueing policies.
As far as sFlow is concerned OVS is a single switch, irrespective of the
Thank you very much! That's exactly what i am searching for. However when i
try the above command i get this:
*ovs-vsctl: Interface does not contain a column whose name matches
"ifindex"*
i tried something more general, and as the above command stated no such
column:
*
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
Hello all,
I am currently trying to use sflow in an SDN environment (mininet).
I have successfully set up the sflow agent in the ovs bridge that is
created by mininet.
My main problem is this that the rules installed by my openflow controller
specify some ports (e.g. port 1, port 2).
However the
