Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

EVPN

  • Routing protocols on EVPN-VXLAN overlay IRB interfaces in the default routing instance (QFX5130-32CD and QFX5220)—Starting in Junos OS Evolved Release 22.4R1, to support running routing protocols on Ethernet VPN VXLAN (EVPN-VXLAN) overlay integrated routing and bridging (IRB) interfaces in the IPv4 or IPv6 default routing instance associated with the underlay (default.inet.0 or default.inet6.0), you can set and export a policy with the install-next-hop except overlay-vxlan-interfaces policy qualifier option. The policy configuration prevents routing loops that can happen if the device uses overlay IRB routes for underlay VTEP reachability. To support this use case in releases prior to 22.4R1, you can configure the IRB interface in a routing instance of type vrf instead of in the default routing instance.

    [See install-nexthop.]

  • EVPN-VXLAN to EVPN-VXLAN seamless stitching for EVPN Type 5 routes (ACX7100-32C, PTX10004, PTX10008, PTX10016, QFX5130-32CD, and QFX5700)—Starting in Junos OS Evolved Release 22.4R1, you can configure EVPN-VXLAN to EVPN-VXLAN seamless stitching with EVPN Type 5 (IP prefix) routes between two interconnected data centers or between two points of delivery (pods) in a data center.

    In the EVPN-VXLAN fabric, border leaf or border spine devices act as interconnection gateways. You enable EVPN Type 5 routes in virtual routing and forwarding (VRF) instances on both sides of the interconnection. For each VRF instance, the server leaf devices in the first data center create VXLAN tunnels for Type 5 routes (with corresponding VXLAN network identifiers [VNIs]) toward their local gateway devices. The gateway devices map those VXLAN tunnels to an interconnection tunnel (with a new route distinguisher [RD], route target, and VNI) toward the second data center. The gateway devices in the second data center re-create the Type 5 VXLAN tunnels using their local RD.

    We support one-to-one mapping of Type 5 VRF instances across the interconnection.

  • Overlay and CE-IP ping and traceroute support for EVPN-VXLAN (ACX7100-32C, ACX710048L, PTX10001-36MR, PTX10004, PTX10016, QFX5130-32CD, and QFX5700)—Starting in Junos OS Evolved Release 22.4R1, you can perform ping and traceroute operations within an EVPN-VXLAN overlay or to a specific customer edge [CE] device IP address (CE-IP) across an EVPN-VXLAN overlay. You can use ping and traceroute and CE-IP ping and traceroute utilities to detect and isolate faults in overlay networks.

    [See Understanding Overlay ping and traceroute Packet Support.]

  • MAC limit and MAC move limit with EVPN-VXLAN (QFX5130-32CD and QFX5700)—Starting in Junos OS Evolved Release 22.4R1, we support the following Layer 2 port security features in an EVPN-VXLAN overlay network:

    • MAC limit—You can limit the number of MAC addresses learned by network (local) interfaces.

      Note:

      We don’t support MAC limits on virtual tunnel endpoint (VTEP) interfaces.

    • MAC move limit—You can limit the number of times a MAC address is moved to a different interface within 1 second. To configure this feature, you apply a limit to a VLAN. In an EVPN-VXLAN network, a VLAN’s members can include network (local) and VTEP interfaces. We support the following MAC move use cases and actions:

      • MAC moves between network interfaces—By default, the configured action is applied on the interface to which the MAC address is last moved. If you configured action priority on the interfaces, the action is applied on the interface with the lesser priority.

      • MAC moves between network and VTEP interfaces and vice-versa—The action is applied on the network interface.

        Note:

        Mac move limit action is not applied on VTEP interfaces.

        We don’t support MAC moves between any interface including VTEP interface and a network interface on which persistent MAC learning and static MAC addresses are configured.

    [See Understanding MAC Limiting and MAC Move Limiting.]