[OVSDB-203] VM Floating IP Address unable to reach the External GW when L3 routing enabled. Created: 08/Sep/15  Updated: 01/Feb/16  Resolved: 01/Feb/16

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

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

Operating System: All
Platform: All

Attachments: Text File ExternalRouter.txt    
External issue ID: 4280

 Description   

Build#: Lithium-SR1 Build
Openstack: stable/kilo
ODL config (on etc/custom.properties)
===========
ovsdb.of.version=1.3
ovsdb.l3.fwd.enabled=yes

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

Openstack setup
=================
eth0 => Mgmt Network eth1=> Data Network eth3 => External Network

Scenario:
=========
1.Create Network 32.1.1.0/24 and External Network as 5.1.1.0/24
2.Create Router and assign GW as 5.1.1.0/24 as external network and associate 32.1.1.0/24
3.Spawned VM1 on Compute Node1 IP address as 31.1.1.3 and Floating IP Address as 5.1.1.2
4.VM1 unable to ping the External Network GateWay 5.1.1.1

Note:
1.br-ex properly mapped with eth3
2.tcpdumps of Switch Gateway proven ping packets reaching the switch vice-versa
3.ufw firewall service was disabled.
4.OF Flow entries exist in br-int interface

==Attached the respective openstack ovs-switch information

 Comments   
Comment by Vasanthan Balasubramaniyan [ 08/Sep/15 ]

Attachment ExternalRouter.txt has been added with description: External Router br-int OF Flow Entries.

Comment by Vasanthan Balasubramaniyan [ 01/Feb/16 ]

Re-tested on Beryliyum-RC1 Build and its worked expected way.Hence closing this issue.

Comment by Vasanthan Balasubramaniyan [ 01/Feb/16 ]

Re-tested on Beryliyum-RC1 Build and its worked expected way.Hence closing this issue.

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