-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to advertise EVPN type 3 (multicast) routes when using a route-map #13792
Comments
Can you get logs with detailed route-map debugs enabled?
|
Yes, I enabled debugging:
But type 2 routes (mac-ip) are advertised:
|
Can you try disabling route-map optimization for that route-map and seeing if that helps? Also, can you provide the full output of |
For context, the symptoms here look like something I fixed here: #12839 I want to confirm that your issue is specific to the route-map optimization + whether the version you're running has the fix. |
Show version: |
Disabling route map optimization solves the issue. |
Sorry for the slow reply - life got very busy very quickly. This looks like the same issue that I resolved in the aforementioned PR, and the fix is not in your build. However, the fix was backported to the I expect the fix will be included in 8.5.3 or in the next major release (9.0 iirc). Until then, disabling route-map optimization on route-maps used for the EVPN address-family should suffice as a workaround. |
Hm, in stable/frr-8.5.2, I had no problems with optimizations disabled. In stable/frr-9.0, the problem recurred, disabling optimization does not solve the problem.
|
Backport based on comment #18669 (comment) Why I did it Fix the below FRR issues FRRouting/frr#14419 FRRouting/frr#13792
This is already fixed, closing. |
Describe the bug
When using any route map, EVPN type 3 (multicast) routes are not advertised.
To Reproduce
This route is not advertised to any peer. As a result, any multicast and broadcast traffic is not routed.
If I turn off the route map, the problem with route advertising goes away:
This route advertised.
Expected behavior
Screenshots
Versions
Additional context
The text was updated successfully, but these errors were encountered: