3.1.1-B32: Retain flood flag in case of ECMP NH for subnet route
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.0.3.x |
New
|
Critical
|
Manish Singh | |||
R3.1 |
Fix Committed
|
High
|
Manish Singh | |||
R3.2 |
Fix Committed
|
High
|
Manish Singh | |||
Trunk |
Fix Committed
|
High
|
Manish Singh |
Bug Description
Contrail - 3.1.1 - Build 32
Manish is aware of this issue.
We have noticed that with dual MX, VM is not able to resolve ARP for BMS. This causes the communication between BMS to VM.
BMS's MAC table had the MAC address of Virtual Machine. The packets from BMS was successfully reaching the tap of VM. However, the return traffic was not going through.
Dual MX:
root@contrail6:~# rt --dump 1 --family inet | grep 192.168.168.0
192.168.168.0/32 24 PT - 27 -
Single MX:
root@contrail6:~# rt --dump 1 --family inet | grep 192.168.168.0
192.168.168.0/32 24 LTF 16 22 -
Reason: The agent introspect did not have the BMS IP. In the absence of IP, we look at the subnet route. In case of dual MX, subnet route is sent by both MX. This causes NH to be ECMP. The moment we see ECMP NH, we do a L3 routing and we don't flood the packet. We proxy it with vRouter MAC.
Please retain the "F" flag even with ECMP next-hop.
Greetings,
Sandeep.
Review in progress for https:/ /review. opencontrail. org/25097
Submitter: Manish Singh (<email address hidden>)