Having two vns with same vxlan id and correcting does not fix it
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.20 |
Fix Committed
|
Medium
|
Praveen | |||
Trunk |
Fix Committed
|
Medium
|
Praveen |
Bug Description
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://
VxLanResp
vxlan_list more
vxlan_id nh
400
nh
type
vrf
ref_count
2
valid
true
policy
disabled
vrf
default-
nh_index
43
vxlan_flag
true
flood_unknown_
false
500
nh
type
vrf
ref_count
2
valid
true
policy
disabled
vrf
default-
nh_index
43
vxlan_flag
true
flood_unknown_
false
root@nodeg11:
Discards 1
Cloned Original 204287
Invalid NH 19
Invalid Mcast Source 1779 <<<<<<
Duplicated 559
Changed in juniperopenstack: | |
assignee: | Praveen (praveen-karadakal) → Manish Singh (manishs) |
Changed in juniperopenstack: | |
assignee: | Manish Singh (manishs) → Praveen (praveen-karadakal) |
gcore of contrail- vrouter- agent on nodeg11 will be in http:// 10.204. 216.50/ Docs/bugs/ 1462799