Replies: 3 comments 2 replies
-
L3VPN traditionally used AS:XX RD to prevent route duplication on every PE-router. That doesn't matter so much in the EVPN world as it seems no route duplication is taking place. It makes no sense to compare two MAC addresses to see which one is better -- if you have two of them, you have a problem. I could add a nerd knob that would influence L3VPN RD format, but if someone thinks they need that they could always write a plugin ;) OTOH, using the workaround creates RDs incompatible with other implementations anyway (so we'd get route duplication no matter what), so just give up, create RD locally from {{ loopback }}:{{v.vrfidx}} or something similar and document it in caveats. |
Beta Was this translation helpful? Give feedback.
-
That's been solved with the EVPN module rewrite |
Beta Was this translation helpful? Give feedback.
-
Fighting again with Dell's implementations ;)
Right now in netlab we are using two different RD encoding, one for VRF and one for L2VNI.
Can we uniform this to use Encoding Type 1 everywhere? https://www.rfc-editor.org/rfc/rfc4364#section-4.2
Dell OS10 is expecting this, for L3VNI RD:
The workaround I am using right now is:
Beta Was this translation helpful? Give feedback.
All reactions