MX IRB stitched mac removed in dual MX scenario
Bug #1637001 reported by
amit surana
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Juniper Openstack | Status tracked in Trunk | |||||
| R3.1 |
Won't Fix
|
Medium
|
Manish Singh | |||
| R3.2 |
Won't Fix
|
Medium
|
Manish Singh | |||
| Trunk |
New
|
Medium
|
Manish Singh | |||
Bug Description
Fix made via https:/
Because the IP prefix (received in evpn) is getting installed in inet.0 table with properties of the subnet route, stitched MAC for IRB IP (configure on MX) is removed if there is ECMP route for subnet prefix (both MXs would send subnet route).
Same also happens on TSN (for gw IP/vrrp mac).
Revision history for this message
| Hari Prasad Killi (haripk) wrote | #1 |
To post a comment you must log in.
Thanks Amit, that was our expectation.
We have no solution for this mac fix yet.
Regards,
Manish
From: Amit Surana <email address hidden>
Date: Wednesday, April 12, 2017 at 12:28 AM
To: Manish Singh <email address hidden>, Hari Prasad Killi <email address hidden>
Subject: Re: https:/
The issue is the following:
Consider a case where the DC has 2 GWs. A VN is extended to both the GWs. In this case, an IRB will be created on both GWs, each with its own IP and MAC address.
The moment the VN is extended to the 2nd GW, the stitched MAC is removed from inet.0 table of the VN for both IRBs. Connectivity is fine, but VMs don't see IRBs real mac (they see vrrp mac instead). As such VM to IRB, the packet is routed. IRB to VM is always routed by MX.
The root cause seems to be that with dual MX the nh for the IRB IPs are changed to point to the subnet route nh; since both MX are sending subnet routes, this is in ecmp, and so stitched MACs are removed.
thanks
amit.