[OVSDB-199] Externalgateway Mac address keeps on try to resolve,after cleared the GW on Openstack externalNetwork Created: 01/Sep/15  Updated: 19/Oct/17  Resolved: 12/Jan/16

Status: Resolved
Project: ovsdb
Component/s: openstack.net-virt
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Vasanthan Balasubramaniyan Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Issue Links:
Duplicate
duplicates OVSDB-242 GatewayMacResolverService continues t... Resolved
External issue ID: 4228

 Description   

Build#: Lithium-SR1 Build
Openstack: stable/kilo

local.conf snip
=======
enable_plugin networking-odl https://github.com/stackforge/networking-odl stable/kilo
Q_PLUGIN=ml2
ENABLE_TENANT_TUNNELS=True
Q_ML2_TENANT_NETWORK_TYPE=vxlan
PUBLIC_INTERFACE=em3
ODL_LOCAL_IP=20.1.1.3
disable_service q-l3
Q_L3_ENABLED=True
ODL_L3=True

ODL custom.properites
================
ovsdb.l3.fwd.enabled=yes
ovsdb.l3gateway.mac=00:00:5E:00:02:01 (tested with both enable/disabled option)

Environment
============
Openstack controller & compute node connected with ODL as external mode.

Problem:
==========
When External Network Gateway has been cleared from openstack side,ODL logs keeps on throwning errors as
====================SNIP======================
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.

==================SNIP==============================

Steps to Reproduce:
==================
1.Create the external network with subnet 5.1.1.0/24
2.On Tenant network,create Router and assign the External Network as Gateway.You can see ODL log with discovery of Gateway
3.Clear the Network Gateway from Router (step-2 created router).
4.ODL log keeps thrown the gateway cannot be resolved

 Comments   
Comment by Ravi Shankar S [ 01/Sep/15 ]

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.

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.

In many cases the br-ex is connected to the ODL controller. This seems to be the core issue.

Pre-request for the external network usecase:

1. br-ex should have openflow connection with the ODL controller.

2. The br -ex should have the below 2 rules,
nvo@compute-2:~/devstack$ sudo ovs-ofctl -O OpenFlow13 dump-flows br-ex
OFPST_FLOW reply (OF1.3) (xid=0x2):
cookie=0x0, duration=1787.584s, table=0, n_packets=29, n_bytes=4624, priority=0 actions=NORMAL
cookie=0x0, duration=1787.583s, table=0, n_packets=346, n_bytes=39098, dl_type=0x88cc actions=CONTROLLER:65535
nvo@compute-2:~/devstack$

3. The br-int and br-ex should be connected to a patch port.

4. The br-ex should be connected to a physical eth interface.

Comment by Vasanthan Balasubramaniyan [ 02/Sep/15 ]

br-ex connected with controller,still this issue is reproducible

Comment by Ravi Shankar S [ 02/Sep/15 ]

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.

Also disable DHCP in the external network creation.

Generated at Wed Feb 07 20:35:46 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.