Hmm, it's a little weird that the same version of OVS is generating different hellos in each case (one for max version 1.4, the other for max version 1.5). Did you configure anything differently?
If ODL only supports OF1.3, you could always try configuring just that version, with "set bridge $NAME protocols=OpenFlow13". On Thu, Aug 09, 2018 at 05:36:22PM -0700, Ashish Varma wrote: > I tried out ODL (nitrogen SR3) with the latest OVS (2.10.90) with the > following configuration: > > sudo ovs-vsctl show > c4f25e49-0e9c-4861-bd2d-e82f20a80864 > Bridge "br20" > Controller "tcp:10.xx.xx.xx:6653" <-- ODL > is_connected: true > Port "br20" > Interface "br20" > type: internal > Bridge "br1" > Port "br1" > Interface "br1" > type: internal > Port "veth_t2" > Interface "veth_t2" > Port "veth_t0" > Interface "veth_t0" > ovs_version: "2.10.90" > > On the wire, I could see OVS sending out HELLO: > > OpenFlow 1.4 > Version: 1.4 (0x05) > Type: OFPT_HELLO (0) > Length: 8 > Transaction ID: 2 > > with no "element" field. > > ODL sends back the HELLO: > > OpenFlow 1.3 > Version: 1.3 (0x04) > Type: OFPT_HELLO (0) > Length: 16 > Transaction ID: 21 > Element > Type: OFPHET_VERSIONBITMAP (1) > Length: 8 > Bitmap: 00000012 > > No further handshake messages are sent except Version 1.3 (0x4) ECHO > generated by OVS and it's response by ODL. > The TCP connection is not torn down and it gets into a stalemate condition > with nothing else happening. > > > ---------------------- > > On the other instance with same ODL and OVS but with following > configuration: > > sudo ovs-vsctl show > c4f25e49-0e9c-4861-bd2d-e82f20a80864 > Bridge "br20" > Port "br20" > Interface "br20" > type: internal > Bridge "br1" > Controller "tcp:10.xx.xx.xx:6653" <-- ODL > is_connected: true > Port "br1" > Interface "br1" > type: internal > Port "veth_t2" > Interface "veth_t2" > Port "veth_t0" > Interface "veth_t0" > ovs_version: "2.10.90" > > OVS generates HELLO with the "element" field: > > OpenFlow 1.5 > Version: 1.5 (0x06) > Type: OFPT_HELLO (0) > Length: 16 > Transaction ID: 3 > Element > Type: OFPHET_VERSIONBITMAP (1) > Length: 8 > Bitmap: 00000072 > > In response, ODL generates FEATURES REQUEST message to which OVS responds > and the handshake and other messages seem to be exchanged normally. > ODL does not generate it's HELLO message.(but this is not a problem) > > > > > > > > > > On Wed, Aug 8, 2018 at 11:10 AM, Ben Pfaff <[email protected]> wrote: > > > On Wed, Aug 08, 2018 at 02:40:37PM +0300, Eray Guven wrote: > > > Hello > > > > > > Somehow, I cannot use last version of OvS ( 2.9.2) with controller ( > > > OpendayLight Nitrogen) . I can work with older versions of OvS easily so > > I > > > dont think source of the problem is ODL here.Yet, I need to work with > > last > > > version of OvS at this moment. I couldnt find any bug or release note > > > related wtih that. Do you have an idea what problem could be ? > > > > > > https://docs.opendaylight.org/en/stable-carbon/submodules/ > > netvirt/docs/user-guide/support.html > > > : Clearly states that OvS 2.9 supported with ODL > > > > > > No errors or no crashes. Just controller doesnt work with network. > > > > Can you identify the earliest version of OVS that has problems? > > Ideally, this would be a commit ID via "git bisect". > > _______________________________________________ > > discuss mailing list > > [email protected] > > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > > _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
