#JUNIPER ROUTE REFLECTOR SOFTWARE#

Juniper themselves haven't been much help on the design front and I'm still chasing yet another software release to fix EVPN problems (latest 18.4R1-Sx or 18.4R2-Sx seems to be the best I've found for EVPN). There are a few old draft RFCs that hint towards a EVPN option-b capability but nothing usable currently as far as I can tell. Maybe I'm missing something with Juniper. A way to stitch VXLAN and MPLS data plane tunnels together at the ASBRs and keep the control planes joined together with eBGP to maintain the route attributes which are lost if a pure data plane interconnect is used.Ĭisco seem to have a solution with their EVPN Multi-Site. What seems to be missing to implement what I wanted was a EVPN version of MPLS 元VPN option B. The core data plane learns the virtual-gateway-v4-address so it doesn't like that it exists via different ESIs and MX will drop traffic if the SMAC matches a local virtual-gateway-v4-address effectively blocking inter-site inter-vlan traffic.

It works, and feels like the least worst solution so far, but the big limitation is multi-site anycast gateways cannot be configured. I ended up creating a EVPN/VXLAN domain per DC and a EVPN/MPLS domain on the core and stitching each DC to the core using a back to back ESI-LAG (using two sets of boxes to avoid some limitations of the Juniper example using lt- interfaces on the same box). I'm curious how other people decided to crack the nut of providing inter-DC L2 with EVPN.ĭid you join the control planes between DCs with iBGP/eBGP and shared your inet.0 for VTEP reachability? Joining all the separate DC AS route reflectors together and living with inter-DC L2 ingress-replication happening at the origin leaf left me feeling a bit uneasy.

Juniper route reflector