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.
Reviewed: https:/ /review. opencontrail. org/11865 github. org/Juniper/ contrail- controller/ commit/ d44fe9a71850555 a2dedbc4c74996b d7b889e1d3
Committed: http://
Submitter: Zuul
Branch: master
commit d44fe9a71850555 a2dedbc4c74996b d7b889e1d3
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: Iadee455d6ae884 08346630645e262 7eb303faaf3