Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

EVPN

  • [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.]

  • Support for control plane transparency for EVPN-VPWS (E-LINE), EVPN-MPLS (E-LAN) and layer2 switching (PTX10001-36MR, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 22.4R1, we support Layer 2 Control Protocol (L2CP) transparency as defined by the Metro Ethernet Forum (MEF). MEF defines the rules devices use to transparently forward L2CP frames by using the reserved MAC addresses dedicated to L2CPs. MEF specifies that L2CP frames can be either peered, passed, or discarded. Juniper forwards (passes) L2CP frames that are received at the user network interface of the ingress PE Junos device unless the protocol has been configured on the local physical/logical interface. When you configure the protocol on the interface, the Packet Forwarding Engine further processes the packet (peers). If you wish the device to drop (discard) the frame, you must explicitly configure a filter to drop (discard) the frames that match the destination MAC address.

    [See Layer 2 Control Protocol Transparency for EVPN.]

  • Support for Nonstop Routing for EVPN MPLS (PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 22.4R1, you can configure nonstop active routing (NSR) for the EVPN-MPLS service. The device mirrors bridge domain and routing information on the backup Routing Engine so this information is available to the backup Routing Engine upon switchover.

    Support doesn't include GRES or VLAN-aware service.

    [See EVPN User Guide.]