Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

EVPN

  • Weighted ECMP for EVPN-MPLS Type 5 routes (MX301, MX304, MX10004, and MX10008)—Use weighted equal-cost multipath (WECMP) for EVPN-MPLS Type 5 routes by advertising generalized weights from gateway counts with the EVPN Link Bandwidth extended community. This advertisement distributes traffic across next hops and prevents congestion when leaf capacities differ. To configure an export policy, use set policy-options policy-statement policy-name then aggregate-weight [multiplier one through 32] and set routing-instances instance-name protocols evpn ip-prefix-routes export policy-name. Use show evpn ip-prefix-database extensive to verify weights, balance factors, and feature state. If weights are missing or inconsistent from the Type 5 route of any leaf device, the border leaf device generates a debug log and follows regular ECMP forwarding to the leaf devices.

    [See policy-statement.]

  • EVPN-VXLAN Type-5 support over IPv6 underlay with MAC-VRFs (MX304 and MX960)—You can deploy EVPN-VXLAN over an IPv6 underlay and advertise EVPN Type-5 IP-prefix routes to extend L3 connectivity. Use MAC-VRF instances to provide L2 services while distributing L3 prefixes end-to-end across an IPv6-only fabric, improving scalability and aligning the network with dual-stack or IPv6-centric designs. To integrate L2 and L3 services, configure IPv6 underlay routing, create EVPN MAC-VRF instances, and enable Type-5 route advertisement. This capability applies to MAC-VRF instances only. Additionally, you can configure IPv6 transport to enable VXLAN EVPN Type-5 route advertisement and SRv6 stitching for seamless interworking between EVPN-VXLAN fabrics and SRv6 transport domains. This capability allows you to build IPv6-only data-center and WAN fabrics that deliver scalable Layer-2 services using MAC-VRF instances and flexible Layer-3 service extension through Type-5 routes.

    [See EVPN-VXLAN with an IPv6 Underlay.]