Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

EVPN

  • Assisted replication (AR) integrated with optimized intersubnet multicast (OISM) in an EVPN-VXLAN edge-routed bridging (ERB) fabric (QFX5130-32CD and QFX5700)—Starting in Junos OS Evolved Release 22.2R1, you can configure AR and OISM together in an EVPN-VXLAN ERB overlay fabric. These devices can serve as AR replicator devices or AR leaf devices.

    Here is a summary of integrated AR and OISM support:

    • AR replicator devices are lean spine devices in the fabric. The AR replicator function can’t be collocated with the OISM border leaf or server leaf role on the same device.

    • AR leaf devices can be OISM server leaf or border leaf devices.

    • AR replicator devices must be running Junos OS Evolved software that supports OISM (even though the AR replicator devices don't operate in either an OISM server leaf or OISM border leaf role).

    When you configure AR devices:

    • You configure the EVPN instances using MAC-VRF instances with vlan-based or vlan-aware service types only.

    • You must configure the AR replicator devices with the same tenant VRF instances, corresponding IRB interfaces, and member VLANs as the OISM devices.

    [See Assisted Replication Multicast Optimization in EVPN Networks and Optimized Inter-Subnet Multicast in EVPN Networks.]

  • Blocking asymmetric EVPN Type 5 routes (QFX5130-32CD and QFX5700)—Starting in Junos OS Evolved Release 22.2R1, you can configure the local node to reject asymmetric EVPN Type 5 routes on EVPN-VXLAN networks. The local node examines the incoming EVPN Type 5 route packets and rejects the route when the virtual network identifier (VNI) in the ingress route differs from the locally configured VNI.

    To block asymmetric EVPN Type 5 routes, include the reject-asymmetric-vni statement at the [edit routing-instance routing-instance-name protocols evpn ip-prefix-routes] hierarchy level.

    [See EVPN Type 5 Route with VXLAN encapsulation for EVPN-VXLAN and ip-prefix-routes.]

  • EVPN-MPLS E-LAN flow-aware transport (FAT) label load balancing (PTX10001-36MR, PTX10004, PTX10008, PTX10016) —Starting in Junos OS Evolved 22.2R1, you can configure provider edge (PE) devices to use FAT labels in an EVPN-MPLS routing instance, according to RFC 6391. Provider edge devices use these labels to load-balance EVPN-MPLS unicast packets across ECMP paths without needing to do deep packet inspection of the MPLS payload. This feature supports E-LAN 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.

    To enable load balancing using FAT labels in an evpn routing instance:

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

  • Interconnect EVPN-VXLAN in a data center to an EVPN-VXLAN control plane in a WAN using a gateway model (QFX5130-32CD and QFX5700)—Starting in Junos OS Evolved 22.2R1, we support Data Center Interconnect (DCI) stitching for EVPN-VXLAN gateway tunnels. The gateway connects the data center and the WAN, and both data center and WAN gain forwarding states for route distinguishing, route targeting, and interconnect Ethernet segment identifier (I-ESI) support.

    DCI control plane stitching also:

    • Supports multihoming.

    • Extends the Layer 2 (L2) connectivity required for some tenants in a data center.

    • Uses the unknown MAC route to prevent MAC scale issues on data center network virtualization edge (NVE) devices.

    [See Understanding the MAC Addresses For a Default Virtual Gateway in an EVPN-VXLAN or EVPN-MPLS Overlay Network.]

  • Support for overlapping VLANs on the same leaf device (ACX7100-32C and ACX7100-48L)—Starting in Junos OS Evolved Release 22.2R1, you can configure overlapping VLANs in enterprise and service provider style CLIs. In cloud-based Platform-as-a-Service (PaaS) and Infrastructure-as-a-Service (IaaS) deployments, VLANs can overlap between the private cloud network and customer traffic. For example, the private cloud network can use a set of VLANs connected to a physical port on a leaf device. You can then connect a customer VLAN on different physical ports on the same leaf device. In this scenario, you need to forward the customer traffic over the same VXLAN core network.

    [See Ethernet Switching Guide].

  • Symmetric IRB with EVPN Type 2 routes (ACX7100, PTX10001-36MR, PTX10004, PTX10008, PTX10016, QFX5130-32CD, and QFX5700)—Starting in Junos OS Evolved Release 22.2R1, you can enable symmetric IRB EVPN Type 2 routing in an Ethernet VPN–Virtual Extensible LAN (EVPN-VXLAN) edge-routed bridging (ERB) overlay fabric. With the symmetric routing model, leaf devices can route and bridge traffic on both ingress and egress sides of a VXLAN tunnel. Leaf devices use a transit VXLAN network identifier (VNI) and Layer 3 (L3) interfaces on the associated VLAN to exchange traffic across the VXLAN tunnels.

    We support this feature with vlan-aware and vlan-based MAC-VRF instance service type configurations. To enable this feature, you must also configure EVPN Type 5 routing with L3 VRF instances to establish intersubnet reachability among the EVPN devices.

    [See Symmetric Integrated Routing and Bridging with EVPN Type 2 Routes in EVPN-VXLAN Fabrics and irb-symmetric-routing.]