Having two vns with same vxlan id and correcting does not fix it

[Vedamurthy Joshi]

R2.20 Build 40 Ubuntu 14.04 Juno multi-node setup
Vxlan was in Configured mode

vn1 had vxlan id 400 and a BMS on TOR1
vn3 also had vxlan id 400 and a BMS on a diff TOR TOR2

vn3 was then modified to have vxlan id 500

But in TSN, vxlan 400 continued to point to vn3
Arp traffic from vn1's BMS was then getting dropped in vrouter as 'Invalid Mcast source'

http://nodeg11:8085/Snh_VxLanReq?

VxLanResp
vxlan_list more
vxlan_id nh
400
nh
type
vrf
ref_count
2
valid
true
policy
disabled
vrf
default-domain:admin:vn3:vn3
nh_index
43
vxlan_flag
true
flood_unknown_unicast
false
500
nh
type
vrf
ref_count
2
valid
true
policy
disabled
vrf
default-domain:admin:vn3:vn3
nh_index
43
vxlan_flag
true
flood_unknown_unicast
false

root@nodeg11:/var/crashes# dropstats | grep -v " 0"

Discards 1
Cloned Original 204287

Invalid NH 19
Invalid Mcast Source 1779 <<<<<<

Duplicated 559

[Vedamurthy Joshi (vedujoshi)]

gcore of contrail-vrouter-agent on nodeg11 will be in http://10.204.216.50/Docs/bugs/1462799

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/11582
Submitter: Praveen K V (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/11582
Committed: http://github.org/Juniper/contrail-controller/commit/b860e925c8d4e0b2d3f26350adc32479b5163aa5
Submitter: Zuul
Branch: R2.20

commit b860e925c8d4e0b2d3f26350adc32479b5163aa5
Author: Praveen K V <email address hidden>
Date: Sat Jun 13 14:39:24 2015 +0530

Handle multiple-vn with same vxlan-id

Ideally, the vxlan-id is different for every vlan. However, either due
to invalid configuration or transition of vxlan-mode from "automatic" to
"configured", more than one VN can have same vxlan.

Added a ConfigTree in VxLanTable. ConfigTree contains <vxlan-id + vn> as
key. If more than one VN has same vxlan, the first entry added into the
tree becomes "active" entry. Other entries become "inactive" entries.
When first entry is deleted, the first-entry in ConfigTree after
deletion becomes new "active" entry.

Closes-Bug: #1462799

Change-Id: Iadee455d6ae88408346630645e2627eb303faaf3

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/11865
Submitter: Praveen K V (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/11865
Committed: http://github.org/Juniper/contrail-controller/commit/d44fe9a71850555a2dedbc4c74996bd7b889e1d3
Submitter: Zuul
Branch: master

commit d44fe9a71850555a2dedbc4c74996bd7b889e1d3
Author: Praveen K V <email address hidden>
Date: Sat Jun 13 14:39:24 2015 +0530

Handle multiple-vn with same vxlan-id

Ideally, the vxlan-id is different for every vlan. However, either due
to invalid configuration or transition of vxlan-mode from "automatic" to
"configured", more than one VN can have same vxlan.

Added a ConfigTree in VxLanTable. ConfigTree contains <vxlan-id + vn> as
key. If more than one VN has same vxlan, the first entry added into the
tree becomes "active" entry. Other entries become "inactive" entries.
When first entry is deleted, the first-entry in ConfigTree after
deletion becomes new "active" entry.

Closes-Bug: #1462799

Change-Id: Iadee455d6ae88408346630645e2627eb303faaf3