EVPN

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