[OVSDB-208] Restack/new compute node VM doesn’t communicated north-south traffic Created: 23/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: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 4346

 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 will communicate with External Network GateWay 5.1.1.1
5.Stack the new compute node and spawn VM2 assign ip address 31.1.1.4 and floating IP address 5.1.1.3
6.VM2 unable to communicated with External Network (i.e North-South).However VM1 and VM2 manage to communicate using local network (i.e 31.1.1.3 to 31.1.1.4)

Observation:
=========
OF-Flow entries of Router Interface missing on restack/new compute node br-int interface.

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

The restack of new node works for N-S traffic, if the compute is a host machine.

The restack does not work for N-S traffic, if the compute node is a VM (Vmware VM). This is because the VM process only broadcast packets. We have verified that the ARP is resolved from the gateway to VM (we tried to ping a broadcast ping).
Only the unicast packet is dropped or does not reach the VM's ethx interface. This is because the hypervisor layer drops the unicast packet, since the resolved floating IP MAC is not associated with any interface in VM. This MAC is assigned by the openstack/ODL and it is not part of any interface.

This is not a ODL issue and it seems to be a hypervisor issue. So, please close this PR.

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