Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

EVPN

  • EVPN-MPLS E-LAN flow-aware transport (FAT) label load balancing (MX Series, EX9200, vMX) —Starting in Junos OS Release 22.4R1, you can configure provider edge (PE) devices to use FAT labels in an Ethernet VPN-MPLS (EVPN-MPLS) routing instance, according to Request for Comments (RFC) 6391. PE devices use these labels to load-balance EVPN-MPLS unicast packets across equal-cost multipaths (ECMPs) without performing deep packet inspection of the MPLS payload. This feature supports emulated LAN (ELAN) with single-homing and multi-homing active/standby and active/active topologies and supports the VLAN-based, VLAN-bundle, and VLAN-aware bundle EVPN-MPLS variants.

    Note:

    This feature does not support MX Series devices with Advanced Forwarding Toolkit (AFT) cards.
    Note:
    On MX Series devices, a configuration where the local PE has a static-flow-label and the remote PE does not have a static-flow-label, the remote PE can process packets without dropping any traffic.

    Enabling Load Balancing Using Fat Labels for EVPN Routing Instances:

    Warning:

    Configuring a flow label or deleting a flow label with the following CLI commands causes a catastrophic event for the routing instance. As a best practice, perform these CLI commands during a maintenance period to avoid network disruptions.

    • Configure the flow-label-static statement at the [edit routing-instances routing-instance-name protocols evpn] hierarchy level on PE devices to insert FAT flow labels into pseudowire packets sent to remote PE devices.

    • Configure the flow-label statement at the [edit routing-instances routing-instance-name protocols evpn] hierarchy level on PE devices to signal flow-label capability in the EVPN Layer 2 Attributes Extended Community by setting the flow-label (F) bit in the EVPN Type 3 route.

    [See flow-label and flow-label-static.]

  • EVPN-VPWS over SRv6 underlay (MX240, MX304, MX480, MX960, MX10003, MX10008, MX2010, and MX2020)—Starting in Junos OS Release 22.4R1, you can configure a single-active or an all-active multihomed Ethernet VPN–virtual private wireless service (EVPN-VPWS) network using segment routing over a Segment Routing for IPv6 (SRv6) underlay.

    [See Overview of VPWS with EVPN Signaling Mechanisms.]

  • EVPN-VXLAN to EVPN-VXLAN seamless stitching for EVPN Type 5 routes (EX4100-24T, EX4400-24MP, EX4400-24P, EX4400-48F, EX4650, MX204, MX240, QFX10002-60C, QFX10002, QFX10008, QFX10016, QFX5120-32C, QFX5120-48T, QFX5120-48Y, QFX5120-48Y-VC, and QFX5120-48YM)—Starting in Junos OS Release 22.4R1, you can configure Ethernet VPN–Virtual Extensible LAN (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 virtual 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.

  • Support for Microsoft load-balancing node's static ARP entries with unicast MAC addresses (EX9208, MX-Series, and VMX)—Starting in Junos OS Release 22.4R1, you can configure a Microsoft load-balancing node's static Address Resolution Protocol (ARP) entries for unicast MAC addresses on integrated routing and bridging (IRB) interfaces. On your provider edge (PE) device, you can create a static ARP entry for the Microsoft load-balancing node’s virtual IP address and its unicast virtual MAC address. This static ARP configuration enables your PE devices to flood traffic for the Microsoft load-balancing node’s virtual IP address to the virtual MAC address in an EVPN Layer 2 domain or any other Layer 2 domain.

    To enable unicast MAC addresses on IRB interfaces, enable the flood-as-unknown-unicas option in the [edit interfaces irb unit <logical-interface-number> family inet address <local-ip-address>/<prefix-length> arp <MSLB-virtual IP address> mac <MSLB-unicast-VMAC>] hierarchy. The flood-as-unknown-unicast option enables flooding of virtual IP addresses and virtual MAC traffic flows from a Microsoft load-balancing cluster.

    [See EVPN User Guide.]