https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/OVSDB-199 ovsdb <p>Build#: Lithium-SR1 Build<br/> Openstack: stable/kilo</p> <p>local.conf snip<br/> =======<br/> enable_plugin networking-odl <a href="https://github.com/stackforge/networking-odl" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/stackforge/networking-odl</a> stable/kilo<br/> Q_PLUGIN=ml2<br/> ENABLE_TENANT_TUNNELS=True<br/> Q_ML2_TENANT_NETWORK_TYPE=vxlan<br/> PUBLIC_INTERFACE=em3<br/> ODL_LOCAL_IP=20.1.1.3<br/> disable_service q-l3<br/> Q_L3_ENABLED=True<br/> ODL_L3=True</p> <p>ODL custom.properites<br/> ================<br/> ovsdb.l3.fwd.enabled=yes<br/> ovsdb.l3gateway.mac=00:00:5E:00:02:01 (tested with both enable/disabled option)</p> <p>Environment<br/> ============<br/> Openstack controller &amp; compute node connected with ODL as external mode.</p> <p>Problem:<br/> ==========<br/> When External Network Gateway has been cleared from openstack side,ODL logs keeps on throwning errors as <br/> ====================SNIP======================<br/> 2015-09-01 17:49:01,583 | ERROR | pool-55-thread-1 | GatewayMacResolverService | 285 - org.opendaylight.ovsdb.openstack.net-virt-providers - 1.1.1.Lithium-SR1 | MAC address for gateway 5.1.1.1 can not be resolved, because external bridge 52239137539 is not connected to controller.</p> <p>==================SNIP==============================</p> <p>Steps to Reproduce:<br/> ==================<br/> 1.Create the external network with subnet 5.1.1.0/24<br/> 2.On Tenant network,create Router and assign the External Network as Gateway.You can see ODL log with discovery of Gateway<br/> 3.Clear the Network Gateway from Router (step-2 created router).<br/> 4.ODL log keeps thrown the gateway cannot be resolved</p> <p>Operating System: All<br/> Platform: All</p> OVSDB-199

Externalgateway Mac address keeps on try to resolve,after cleared the GW on Openstack externalNetwork

Bug Resolved Duplicate Unassigned Vasanthan Balasubramaniyan Tue, 1 Sep 2015 12:22:47 +0000 Thu, 19 Oct 2017 21:29:05 +0000 Tue, 12 Jan 2016 23:45:13 +0000 unspecified openstack.net-virt 0 3 <p>From the below ODl logs, it is clear that the br-ex bridge is not connected to the controller. Please connect the br-ex with the controller using set-controller commands. This issue should not be seen after the openflow connection is established between ODl and br-ex. </p> <p> 285 - org.opendaylight.ovsdb.openstack.net-virt-providers - 1.1.1.Lithium-SR1 | MAC address for gateway 5.1.1.1 can not be resolved, because external bridge 52239137539 is not connected to controller.</p> <p> In many cases the br-ex is connected to the ODL controller. This seems to be the core issue.</p> <p>Pre-request for the external network usecase:</p> <p>1. br-ex should have openflow connection with the ODL controller.</p> <p>2. The br -ex should have the below 2 rules,<br/> nvo@compute-2:~/devstack$ sudo ovs-ofctl -O OpenFlow13 dump-flows br-ex<br/> OFPST_FLOW reply (OF1.3) (xid=0x2):<br/> cookie=0x0, duration=1787.584s, table=0, n_packets=29, n_bytes=4624, priority=0 actions=NORMAL<br/> cookie=0x0, duration=1787.583s, table=0, n_packets=346, n_bytes=39098, dl_type=0x88cc actions=CONTROLLER:65535<br/> nvo@compute-2:~/devstack$</p> <p>3. The br-int and br-ex should be connected to a patch port.</p> <p>4. The br-ex should be connected to a physical eth interface.</p> <p>br-ex connected with controller,still this issue is reproducible</p> <p>I think we should assign floating IP to the VM. After assigning the floating IP only then the translation flow to move to the external network from internal, will be written to the switch.</p> <p> Also disable DHCP in the external network creation.</p> Duplicate OVSDB-242 Development External issue ID 4228 External issue URL Rank 0|i0219b: