Re: [ovs-dev] br-int bridge dpid changes when openvswitch is restarted
3a82062120"],["uuid","7d404ba9-d2aa-4306-bdcb-e6bc088654fb"],["uuid","fc85f0a8-d97f-49a1-86e6-13a76bdf840a"]]],"status":["map",[]],"ipfix":["set",[]],"other_config":["map",[["disable-in-band","true"],["hwaddr","90:2e:72:41:fc:da"]]],"datapath_id":"a8ceb1b8d124","mirrors":["set",[]],"mcast_snooping_enable":false,"datapath_version":"","sflow":["set",[]],"protocols":"OpenFlow13"},"old":{"other_config":["map",[["disable-in-band","true"],["hwaddr","a8:ce:b1:b8:d1:24"]]]]
2016-10-28T23:21:02.037Z|00122|poll_loop|DBG|wakeup due to [POLLIN] on fd 17
(/var/run/openvswitch/db.sock<->) at lib/stream-fd.c:155
2016-10-28T23:21:02.037Z|00123|jsonrpc|DBG|unix: received request,
method="transact",
params=["Open_vSwitch",{"lock":"ovs_vswitchd","op":"assert"},{"where":[["_uuid","==",["uuid","15e50dab-60d7-4544-8051-fdf2141ef433"]]],"table":"Bridge","op":"update","row":{"datapath_id":"902e7241fcda"}}],
id=5
2016-10-28T23:21:02.038Z|00124|jsonrpc|DBG|unix: send notification,
method="update",
params=[null,{"Bridge":{"15e50dab-60d7-4544-8051-fdf2141ef433":{"new":{"name":"br-int","flood_vlans":["set",[]],"auto_attach":["set",[]],"ports":["uuid","d20ae748-927e-4c06-bf6f-0616e1127464"],"stp_enable":false,"fail_mode":"secure","rstp_enable":false,"rstp_status":["map",[]],"flow_tables":["map",[]],"netflow":["set",[]],"datapath_type":"","controller":["set",[["uuid","0e2fe15c-fda6-446d-9950-9e3a82062120"],["uuid","7d404ba9-d2aa-4306-bdcb-e6bc088654fb"],["uuid","fc85f0a8-d97f-49a1-86e6-13a76bdf840a"]]],"status":["map",[]],"ipfix":["set",[]],"other_config":["map",[["disable-in-band","true"],["hwaddr","90:2e:72:41:fc:da"]]],"datapath_id":"902e7241fcda","mirrors":["set",[]],"mcast_snooping_enable":false,"datapath_version":"","sflow":["set",[]],"protocols":"OpenFlow13"},"old":{"datapath_id":"a8ceb1b8d124"]
2016-10-28T23:21:02.039Z|00125|jsonrpc|DBG|unix: send reply,
result=[{},{"count":1}], id=5
2016-10-28T23:21:02.039Z|00126|jsonrpc|DBG|tcp:192.168.254.35:6640: send
notification, method="update",
params=["f8af9856-b198-4c86-83cd-541511fa62bc",{"Bridge":{"15e50dab-60d7-4544-8051-fdf2141ef433":{"new":{"name":"br-int","flood_vlans":["set",[]],"auto_attach":["set",[]],"ports":["uuid","d20ae748-927e-4c06-bf6f-0616e1127464"],"stp_enable":false,"fail_mode":"secure","rstp_enable":false,"_uuid":["uuid","15e50dab-60d7-4544-8051-fdf2141ef433"],"rstp_status":["map",[]],"flow_tables":["map",[]],"netflow":["set",[]],"datapath_type":"","controller":["set",[["uuid","0e2fe15c-fda6-446d-9950-9e3a82062120"],["uuid","7d404ba9-d2aa-4306-bdcb-e6bc088654fb"],["uuid","fc85f0a8-d97f-49a1-86e6-13a76bdf840a"]]],"other_config":["map",[["disable-in-band","true"],["hwaddr","90:2e:72:41:fc:da"]]],"status":["map",[]],"ipfix":["set",[]],"external_ids":["map",[["opendaylight-iid","/network-topology:network-topology/network-topology:topology[network-topology:topology-id='ovsdb:1']/network-topology:node[network-topology:node-id='ovsdb://uuid/b429858f-b476-44be-94ac-e9ea61265a11/bridge/br-int']"]]],"datapath_id":"902e7241fcda","mirrors":["set",[]],"mcast_snooping_enable":false,"datapath_version":"","sflow":["set",[]],"protocols":"OpenFlow13"},"old":{"datapath_id":"a8ceb1b8d124"]
2016-10-28T23:21:02.04
Re: [ovs-dev] br-int bridge dpid changes when openvswitch is restarted
On Thu, Oct 27, 2016 at 11:51:42PM +, Bertrand Low wrote: > 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|4|reconnect|INFO|unix:/var/run/openvswitch/db.sock: > connecting... > 2016-10-26T19:16:24.910Z|5|reconnect|INFO|unix:/var/run/openvswitch/db.sock: > connected > 2016-10-26T19:16:24.912Z|6|ofproto_dpif|INFO|system@ovs-system: Datapath > supports recirculation > 2016-10-26T19:16:24.912Z|7|ofproto_dpif|INFO|system@ovs-system: MPLS > label stack length probed as 0 > 2016-10-26T19:16:24.912Z|8|ofproto_dpif|INFO|system@ovs-system: datapath > does not support masked set action feature. > 2016-10-26T19:16:24.912Z|9|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 > bc8838168d41 > 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|1|ofproto_dpif_upcall(handler5)|INFO|received > packet on unassociated datapath port 0 > 2016-10-26T19:16:25.430Z|1|dpif(revalidator4)|WARN|system@ovs-system: > failed to flow_get (Invalid argument) > ufid:b1d72bef-1acb-4755-850a-2aeb4fb75ad2 , packets:0, bytes:0, > used:never > 2016-10-26T19:16:25.430Z|2|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 > b88fc560944b > 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 bc8838168d41 that connects > to opendaylight and then it changes to dpid b88fc560944b and disconnects > and reconnects to opendaylight. > > Can anyone provide insight on the errors: > 2016-10-26T19:16:24.929Z|1|ofproto_dpif_upcall(handler5)|INFO|received > packet on unassociated datapath port 0 > 2016-10-26T19:16:25.430Z|1|dpif(revalidator4)|WARN|system@ovs-system: > failed to flow_get (Invalid argument) > ufid:b1d72bef-1acb-4755-850a-2aeb4fb75ad2 , packets:0, bytes:0, > used:never > 20
