[ovs-discuss] Does openvswitch-1.10.0 supports OF1.3?

[Ben Pfaff]

"Multipart" is not a message.  It is a class of messages.  "ovs-ofctl
dump-flows" is one example of a command that uses a multipart message.

No ovs-ofctl command uses queue configuration messages.

"ovs-ofctl packet-out" is documented.  Please read the documentation.

Almost every ovs-ofctl command uses barriers.

I don't think ovs-ofctl uses the other messages you mention, or has
any need to do so.

On Wed, Jul 03, 2013 at 11:59:01AM +0530, Suhas Chandramouli wrote:
>  *Multipart*  *Queue Configuration*  *Packet-Out*  *Barrier*  *Role Request*
> *Set Asynchronous Configuration*
> 
> These are the messages i am not able to see while snooping. Do we have any
> 'ovs-ofctl' commands from Openvswitch to invoke these messages. These
> messages are to be initiated by Controller. Is it?
> Please suggest.
> 
> -Suhas Chandramouli
> 
> On 24 June 2013 22:25, Ben Pfaff <blp at nicira.com> wrote:
> 
> > Please don't drop the mailing list.
> >
> > The flows you added have the same match criteria, so they are only one
> > flow, which means that the second one replaces the first one.
> >
> > You can use "ovs-ofctl monitor" to see packet-ins.  Please read the
> > ovs-ofctl manpage.
> >
> > If you want to observe everything that your controller sees, then you
> > can use "ovs-ofctl snoop".  Please read the ovs-ofctl manpage.
> >
> > On Fri, Jun 21, 2013 at 06:01:21PM +0530, Suhas Chandramouli wrote:
> > > Hi Ben
> > >
> > > How could we see all the flows in a table?
> > >
> > > I have added 2 flows to the table '0' but *ovs-ofctl -O OpenFlow13
> > > dump-flows br0 *command shows only the latest flow added.
> > >
> > > [root at localhost openvswitch-1.10.0]# *ovs-ofctl -O OpenFlow13 add-flow
> > br0
> > > in_port=0,action=normal*
> > > [root at localhost openvswitch-1.10.0]# *ovs-ofctl -O OpenFlow13
> > dump-flows br0
> > > *
> > > OFPST_FLOW reply (OF1.3) (xid=0x2):
> > >  cookie=0x0, duration=5.647s, table=0, n_packets=0, n_bytes=0, in_port=0
> > *
> > > actions=NORMAL*
> > >  cookie=0x0, duration=2141.558s, table=0, n_packets=0, n_bytes=0,
> > > send_flow_rem priority=0 actions=CONTROLLER:0
> > > [root at localhost openvswitch-1.10.0]# *ovs-ofctl -O OpenFlow13 add-flow
> > br0
> > > in_port=0,action=controller:100*
> > > [root at localhost openvswitch-1.10.0]# *ovs-ofctl -O OpenFlow13
> > dump-flows br0
> > > *
> > > OFPST_FLOW reply (OF1.3) (xid=0x2):
> > >  cookie=0x0, duration=2.112s, table=0, n_packets=0, n_bytes=0, in_port=0
> > *
> > > actions=CONTROLLER:100*
> > >  cookie=0x0, duration=2149.894s, table=0, n_packets=0, n_bytes=0,
> > > send_flow_rem priority=0 actions=CONTROLLER:0
> > >
> > >
> > > How can we see packet_in, packet_out messages in OF 1.3? Do we need a
> > > wireshark packet capture? Any command to check?
> > >
> > > Basic idea is to see all the messages in OPenFlow Protocol 1.3 i.e
> > > Controller to Switch, Asynchronous and Symmetric.
> > >
> > > -Suhas Chandramouli
> > >
> > >
> > > On 20 June 2013 22:41, Suhas Chandramouli <suhas16c at gmail.com> wrote:
> > >
> > > > Ben,
> > > >
> > > > Thanks a lot. The information was helpful.
> > > >
> > > > Suhas Chandramouli
> > > > Sent from my Windows Phone From: Ben Pfaff
> > > > Sent: 19-06-2013 22:14
> > > > To: Suhas Chandramouli
> > > > Cc: bugs at openvswitch.org
> > > > Subject: Re: [ovs-discuss] Does openvswitch-1.10.0 supports OF1.3?
> > > > On Wed, Jun 19, 2013 at 06:13:24PM +0530, Suhas Chandramouli wrote:
> > > > > These are the messages i observed. Controller supports OF1.3 and i
> > read
> > > > > openvswitch-1.10.0 also supports 1.3 but still not able to connect
> > to the
> > > > > controller.
> > > >
> > > > The FAQ says:
> > > >
> > > > Q: What versions of OpenFlow does Open vSwitch support?
> > > >
> > > > A: Open vSwitch 1.9 and earlier support only OpenFlow 1.0 (plus
> > > >    extensions that bring in many of the features from later versions
> > > >    of OpenFlow).
> > > >
> > > >    Open vSwitch versions 1.10 and later will have experimental support
> > > >    for OpenFlow 1.2 and 1.3.  On these versions of Open vSwitch, the
> > > >    following command enables OpenFlow 1.0, 1.2, and 1.3 on bridge br0:
> > > >
> > > >        ovs-vsctl set bridge br0
> > protocols=OpenFlow10,OpenFlow12,OpenFlow13
> > > >
> > > >    Support for OpenFlow 1.1 is incomplete enough that it cannot yet be
> > > >    enabled, even experimentally.
> > > >
> > > >    Support for OpenFlow 1.2 and 1.3 is still incomplete.  Work to be
> > > >    done is tracked in OPENFLOW-1.1+ in the Open vSwitch source tree
> > > >    (also via http://openvswitch.org/development/openflow-1-x-plan/).
> > > >    When support for a given OpenFlow version is solidly implemented,
> > > >    Open vSwitch will enable that version by default.
> > > >
> > >
> > >
> > >
> > > --
> > > -Regards
> > > Suhas Chandramouli
> >
> 
> 
> 
> -- 
> -Regards
> Suhas Chandramouli