Hi there, Has anyone noticed a "connection flapping" behaviour for the br-int bridge (used between openstack and opendaylight's netvirt module) when openvswitch is restarted? I've provided some details below.
Scenario: - Opendaylight 3-node cluster running distribution-karaf-0.5.0-Boron with the odl-ovsdb-openstack feature installed - A standalone OVS node running OVS version 2.4.0 - Step 1) set-manager of OVS node to all 3-nodes in the cluster - Step 2) confirm that br-int is created automatically by the Opendaylight's NetVirt module) and all pipeline flows are pushed to the OVS node - Step 3) on the OVS node, run systemctl stop openvswitch - Step 4) on the OVS node, run systemctl start openvswitch Here is what ovs-vswitchd.log shows at step 4): 2016-10-26T19:16:24.910Z|00004|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connecting... 2016-10-26T19:16:24.910Z|00005|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connected 2016-10-26T19:16:24.912Z|00006|ofproto_dpif|INFO|system@ovs-system: Datapath supports recirculation 2016-10-26T19:16:24.912Z|00007|ofproto_dpif|INFO|system@ovs-system: MPLS label stack length probed as 0 2016-10-26T19:16:24.912Z|00008|ofproto_dpif|INFO|system@ovs-system: datapath does not support masked set action feature. 2016-10-26T19:16:24.912Z|00009|ofproto_dpif|INFO|system@ovs-system: Datapath does not support unique flow ids 2016-10-26T19:16:24.916Z|00010|bridge|INFO|bridge br-int: added interface br-int on port 65534 2016-10-26T19:16:24.916Z|00011|bridge|INFO|bridge br-int: using datapath ID 0000bc8838168d41 2016-10-26T19:16:24.916Z|00012|connmgr|INFO|br-int: added service controller "punix:/var/run/openvswitch/br-int.mgmt" 2016-10-26T19:16:24.916Z|00013|connmgr|INFO|br-int: added primary controller "tcp:192.168.254.35:6653" 2016-10-26T19:16:24.917Z|00014|rconn|INFO|br-int<->tcp:192.168.254.35:6653: connecting... 2016-10-26T19:16:24.917Z|00015|connmgr|INFO|br-int: added primary controller "tcp:192.168.254.33:6653" 2016-10-26T19:16:24.917Z|00016|rconn|INFO|br-int<->tcp:192.168.254.33:6653: connecting... 2016-10-26T19:16:24.917Z|00017|connmgr|INFO|br-int: added primary controller "tcp:192.168.254.34:6653" 2016-10-26T19:16:24.917Z|00018|rconn|INFO|br-int<->tcp:192.168.254.34:6653: connecting... 2016-10-26T19:16:24.924Z|00019|rconn|INFO|br-int<->tcp:192.168.254.33:6653: connected 2016-10-26T19:16:24.924Z|00020|rconn|INFO|br-int<->tcp:192.168.254.34:6653: connected 2016-10-26T19:16:24.925Z|00021|bridge|INFO|ovs-vswitchd (Open vSwitch) 2.4.0 2016-10-26T19:16:24.927Z|00022|rconn|INFO|br-int<->tcp:192.168.254.35:6653: connected 2016-10-26T19:16:24.929Z|00001|ofproto_dpif_upcall(handler5)|INFO|received packet on unassociated datapath port 0 2016-10-26T19:16:25.430Z|00001|dpif(revalidator4)|WARN|system@ovs-system: failed to flow_get (Invalid argument) ufid:b1d72bef-1acb-4755-850a-2aeb4fb75ad2 <empty>, packets:0, bytes:0, used:never 2016-10-26T19:16:25.430Z|00002|ofproto_dpif_upcall(revalidator4)|WARN|Failed to acquire udpif_key corresponding to unexpected flow (Invalid argument): ufid:b1d72bef-1acb-4755-850a-2aeb4fb75ad2 2016-10-26T19:16:26.312Z|00023|bridge|INFO|bridge br-int: using datapath ID 0000b88fc560944b 2016-10-26T19:16:26.313Z|00024|rconn|INFO|br-int<->tcp:192.168.254.35:6653: disconnecting 2016-10-26T19:16:26.313Z|00025|rconn|INFO|br-int<->tcp:192.168.254.33:6653: disconnecting 2016-10-26T19:16:26.313Z|00026|rconn|INFO|br-int<->tcp:192.168.254.34:6653: disconnecting 2016-10-26T19:16:26.952Z|00028|rconn|INFO|br-int<->tcp:192.168.254.35:6653: connecting... 2016-10-26T19:16:26.952Z|00029|rconn|INFO|br-int<->tcp:192.168.254.33:6653: connecting... 2016-10-26T19:16:26.952Z|00030|rconn|INFO|br-int<->tcp:192.168.254.34:6653: connecting... 2016-10-26T19:16:26.958Z|00031|rconn|INFO|br-int<->tcp:192.168.254.35:6653: connected 2016-10-26T19:16:26.958Z|00032|rconn|INFO|br-int<->tcp:192.168.254.33:6653: connected 2016-10-26T19:16:26.958Z|00033|rconn|INFO|br-int<->tcp:192.168.254.34:6653: connected 2016-10-26T19:16:34.926Z|00034|memory|INFO|35400 kB peak resident set size after 10.0 seconds It seems like the bridge has an initial dpid 0000bc8838168d41 that connects to opendaylight and then it changes to dpid 0000b88fc560944b and disconnects and reconnects to opendaylight. Can anyone provide insight on the errors: 2016-10-26T19:16:24.929Z|00001|ofproto_dpif_upcall(handler5)|INFO|received packet on unassociated datapath port 0 2016-10-26T19:16:25.430Z|00001|dpif(revalidator4)|WARN|system@ovs-system: failed to flow_get (Invalid argument) ufid:b1d72bef-1acb-4755-850a-2aeb4fb75ad2 <empty>, packets:0, bytes:0, used:never 2016-10-26T19:16:25.430Z|00002|ofproto_dpif_upcall(revalidator4)|WARN|Failed to acquire udpif_key corresponding to unexpected flow (Invalid argument): ufid:b1d72bef-1acb-4755-850a-2aeb4fb75ad2 Do the errors above cause the bridge to get a new dpid, which then causes the disconnect and reconnect to opendaylight? Thanks, Bertrand ::DISCLAIMER:: ---------------------------------------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ---------------------------------------------------------------------------------------------------------------------------------------------------- _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
