OVS 2.0 didn't implement that feature.
On Wed, Jun 22, 2016 at 08:55:40PM +0000, Rajasekaran, Monica wrote: > I enabled for Openflow 1.3 as per the command mentioned. Now, that warning on > type 16 is gone. > > But, it constantly keeps printing the following to the screen after > connecting to the controller: > > 2016-06-23T04:32:30Z|00025|connmgr|INFO|OF_Desktop<->tcp:167.254.209.13:6633: > sending OFPBRC_BAD_TYPE error reply to OFPST_GROUP_FEATURES request message > > Thanks, > Monica > > > -----Original Message----- > From: Ben Pfaff [mailto:b...@ovn.org] > Sent: Wednesday, June 22, 2016 3:52 PM > To: Rajasekaran, Monica <monica.rajaseka...@us.fujitsu.com> > Cc: discuss@openvswitch.org > Subject: Re: [ovs-discuss] changing path for startup > > The FAQ lists protocol support by Open vSwitch version: > > ### Q: What versions of OpenFlow does Open vSwitch support? > > A: The following table lists the versions of OpenFlow supported by > each version of Open vSwitch: > > Open vSwitch OF1.0 OF1.1 OF1.2 OF1.3 OF1.4 OF1.5 OF1.6 > ###============ ===== ===== ===== ===== ===== ===== ===== > 1.9 and earlier yes --- --- --- --- --- --- > 1.10 yes --- [*] [*] --- --- --- > 1.11 yes --- [*] [*] --- --- --- > 2.0 yes [*] [*] [*] --- --- --- > 2.1 yes [*] [*] [*] --- --- --- > 2.2 yes [*] [*] [*] [%] [*] --- > 2.3 yes yes yes yes [*] [*] --- > 2.4 yes yes yes yes [*] [*] --- > 2.5 yes yes yes yes [*] [*] [*] > > [*] Supported, with one or more missing features. > [%] Experimental, unsafe implementation. > > Open vSwitch 2.3 enables OpenFlow 1.0, 1.1, 1.2, and 1.3 by default > in ovs-vswitchd. In Open vSwitch 1.10 through 2.2, OpenFlow 1.1, > 1.2, and 1.3 must be enabled manually in ovs-vswitchd. > > Some versions of OpenFlow are supported with missing features and > therefore not enabled by default: OpenFlow 1.4 and 1.5, in Open > vSwitch 2.3 and later, as well as OpenFlow 1.6 in Open vSwitch 2.5 > and later. Also, the OpenFlow 1.6 specification is still under > development and thus subject to change. > > In any case, the user may override the default: > > - To enable OpenFlow 1.0, 1.1, 1.2, and 1.3 on bridge br0: > > ovs-vsctl set bridge br0 > protocols=OpenFlow10,OpenFlow11,OpenFlow12,OpenFlow13 > > - To enable OpenFlow 1.0, 1.1, 1.2, 1.3, 1.4, and 1.5 on bridge br0: > > ovs-vsctl set bridge br0 > protocols=OpenFlow10,OpenFlow11,OpenFlow12,OpenFlow13,OpenFlow14,OpenFlow15 > > - To enable only OpenFlow 1.0 on bridge br0: > > ovs-vsctl set bridge br0 protocols=OpenFlow10 > > All current versions of ovs-ofctl enable only OpenFlow 1.0 by > default. Use the -O option to enable support for later versions of > OpenFlow in ovs-ofctl. For example: > > ovs-ofctl -O OpenFlow13 dump-flows br0 > > (Open vSwitch 2.2 had an experimental implementation of OpenFlow > 1.4 that could cause crashes. We don't recommend enabling it.) > > [OPENFLOW-1.1+.md] in the Open vSwitch source tree tracks support for > OpenFlow 1.1 and later features. When support for OpenFlow 1.4 and > 1.5 is solidly implemented, Open vSwitch will enable those version > by default. > > > On Wed, Jun 22, 2016 at 08:16:53PM +0000, Rajasekaran, Monica wrote: > > Okay, the ovs I had before this was 2.5.0. Which was pretty much perfect. > > > > The one I have now on standalone hardware with Yocto is openvswitch-2.0.0 > > (Due to some reason). Does this version not talk Openflow 1.3? > > > > Should I enable openflow13 for my bridge explicitly like this ? : > > > > ovs-vsctl set bridge br0 protocols=openflow10,openflow12,openflow13 > > > > Thanks, > > Monica > > > > > > -----Original Message----- > > From: Ben Pfaff [mailto:b...@ovn.org] > > Sent: Wednesday, June 22, 2016 3:07 PM > > To: Rajasekaran, Monica <monica.rajaseka...@us.fujitsu.com> > > Cc: discuss@openvswitch.org > > Subject: Re: [ovs-discuss] changing path for startup > > > > Type 16, stat 12 is undefined in OpenFlow 1.0 (version 1). In > > OpenFlow > > 1.3 it is OFPST_TABLE_FEATURES_REQUEST. Maybe the controller is trying to > > make that request in version 1.0; it's not going to work there. > > > > Just a guess though. > > > > On Wed, Jun 22, 2016 at 06:49:03PM +0000, Rajasekaran, Monica wrote: > > > Thanks Ben! > > > > > > Do you know what might cause this message ? Type 16 is for statistics > > > right ? > > > > > > 2016-06-23T00:41:55Z|00025|ofp_msgs|WARN|unknown OpenFlow message > > > (version 1, type 16, stat 12) > > > > > > It happens after my OVS is connected to the controller. Also sends out a > > > bad response after this. > > > > > > Thanks, > > > Monica > > > > > > > > > -----Original Message----- > > > From: Ben Pfaff [mailto:b...@ovn.org] > > > Sent: Wednesday, June 22, 2016 12:42 PM > > > To: Rajasekaran, Monica <monica.rajaseka...@us.fujitsu.com> > > > Cc: discuss@openvswitch.org > > > Subject: Re: [ovs-discuss] changing path for startup > > > > > > On Wed, Jun 22, 2016 at 04:17:38PM +0000, Rajasekaran, Monica wrote: > > > > Hi, > > > > > > > > I built ovs along with Yocto, have it running inside my target hardware. > > > > > > > > When I start ovs by starting ovsdb server, vsctl and vswitchd, it gives > > > > me the following error messages: > > > > > > > > When I start ovsdb server, > > > > > > > > 2016-06-22T23:54:25Z|00001|fatal_signal|WARN|could not unlink > > > > "/usr/local/var/run/openvswitch/db.sock" (No such file or > > > > directory) > > > > 2016-06-22T23:54:25Z|00002|stream_unix|ERR|/usr/local/var/run/open > > > > vs > > > > witch/db.sock: binding failed: No such file or directory > > > > 2016-06-22T23:54:25Z|00003|ovsdb_jsonrpc_server|ERR|punix:/usr/loc > > > > al > > > > /var/run/openvswitch/db.sock: listen failed: No such file or > > > > directory > > > > > > > > When I start vsctl, > > > > > > > > 2016-06-22T23:54:50Z|00003|reconnect|WARN|unix:/var/run/openvswitc > > > > h/ > > > > db.sock: connection attempt failed (No such file or directory) > > > > ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection > > > > failed (No such file or directory) > > > > > > > > When I start vswitchd, > > > > > > > > 2016-06-22T23:55:14Z|00003|reconnect|WARN|unix:/var/run/openvswitc > > > > h/ > > > > db.sock: connection attempt failed (No such file or directory) > > > > > > > > The problem is that it is looking for db.sock and the pid files at > > > > "/usr/local/var/run/openvswitch" but actually it should be looking into > > > > "/var/run/openvswitch" in Yocto. How do I change this ?? Or will > > > > creating a symlink work? > > > > > > INSTALL.md says: > > > > > > By default all files are installed under /usr/local. Open vSwitch > > > also > > > expects to find its database in /usr/local/etc/openvswitch by default. > > > If you want to install all files into, e.g., /usr and /var instead of > > > /usr/local and /usr/local/var and expect to use /etc/openvswitch as > > > the default > > > database directory, add options as shown here: > > > > > > `% ./configure --prefix=/usr --localstatedir=/var > > > --sysconfdir=/etc` _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
