Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

EVPN

  • EVPN-VXLAN fabric with an IPv6 underlay (QFX5120-32C, QFX5120-48T, QFX5120-48Y, QFX5120-48YM, QFX10002, QFX10008, and QFX10016)—Starting in Junos OS Release 21.4R1, you can configure an EVPN-VXLAN fabric with an IPv6 underlay. You can use this feature only with MAC-VRF routing instances (all service types). You must configure either an IPv4 or an IPv6 underlay across the EVPN instances in the fabric; you can’t mix IPv4 and IPv6 underlays in the same fabric.

    To enable this feature, configure the underlay VXLAN tunnel endpoint (VTEP) source interface in the MAC-VRF instance as an IPv6 address. However, you must use the IPv4 loopback address as the router ID for BGP handshaking to work.

    This feature was introduced in Junos OS Release 21.2R2.

    [See EVPN-VXLAN with an IPv6 Underlay and Understanding EVPN with VXLAN Data Plane Encapsulation.]

  • DHCP relay in an EVPN-VXLAN fabric with IPv6 underlay (QFX5120-32C, QFX5120-48T, QFX5120-48Y, QFX5120-24YM, QFX10002, QFX10008, and QFX10016)—Starting in Junos OS Release 21.4R1, EVPN-VXLAN fabrics with an IPv6 underlay support DHCP relay. You can configure the DHCP relay agent in centrally routed and edge-routed bridging overlays. Support for DHCP relay includes support for DHCPv4 and DHCPv6. This feature was introduced in Junos OS Release 21.2R2.

    [See DHCP Relay Agent over EVPN-VXLAN.]

  • CoS support for EVPN-VXLAN with IPv6 underlay (QFX5120-32C, QFX5120-48T, QFX5120-48Y, QFX5120-48YM, QFX10002, QFX10008, and QFX10016)—Starting in Junos OS Release 21.4R1, you can configure CoS features, which enable you to prioritize traffic, on an EVPN-VXLAN fabric with an IPv6 underlay. This feature was introduced in Junos OS Release 21.2R2.

    [See CoS Support on EVPN VXLANs.]

  • Support for firewall filters on EVPN-VXLAN with IPv6 underlay (QFX5120-32C, QFX5120-48T, QFX5120-48Y, QFX5120-24YM, and QFX5120-48YM)—Starting in Junos OS Release 21.4R1, QFX5120 switches support firewall filters for ingress and egress traffic on EVPN-VXLAN with an IPv6 underlay. This feature was introduced in Junos OS Release 21.2R2.

    [See Understanding EVPN with VXLAN Data Plane Encapsulation.]

  • Support for EVPN-VXLAN group-based policies (QFX5120-48Y, QFX5120-48YM, QFX5120-48T, and QFX5120-32C)—Starting in Junos OS Release 21.4R1, QFX5120 switches provide standards-based multilevel segmentation (also called group-based policy, or GBP) on the basis of Layer 3 virtual networks and group-based tags rather than IP-based filters. GBP supports an application-centric policy model that separates network access policies from the underlying network topology through the use of policy tags, thus allowing different levels of access control for endpoints and applications even within the same VLAN.

    The QFX5120 switches also provide GBP support for locally switched traffic on VXLAN access ports.

    [See Example: Micro and Macro Segmentation using Group Based Policy in a VXLAN.]

  • Support for EVPN routing policies on the MPC10E and MPC11E (MX240, MX480, MX960, MX2010, and MX2020)—Starting in Junos OS Release 21.4R1, Junos OS supports policy filter configurations for EVPN routes on the MX240, MX480, and MX960 routers with the MPC10E line cards and on the MX2010 and MX2020 routers with the MPC11E line cards. You can create policies and apply policy filters to import and export EVPN routes at a specific EVPN routing-instance level or at the BGP level if you want to apply the policy to all EVPN routing instances.

    [See Routing policies for EVPN.]

  • Support for EVPN-VXLAN group-based policies (EX4400-24MP, EX4400-24P, EX4400-24T, EX4400-48F, EX4400-48MP, EX4400-48P, EX4400-48T, EX4650, and EX4650-48Y-VC)—Starting in Junos OS Release 21.4R1, EX4400 and EX4650 switches provide standards-based multi-level segmentation (also called group-based policy, or GBP) on the basis of Layer 3 virtual networks and group-based tags rather than IP-based filters. GBP supports an application-centric policy model that separates network access policies from the underlying network topology through the use of policy tags, thus allowing different levels of access control for endpoints and applications even within the same VLAN.

    The EX4400 and EX4650 switches also provide GBP support for locally switched traffic on VXLAN access ports.

    [See Micro and Macro Segmentation using Group Based Policy in a VXLAN.]

  • Dynamic overlay load balancing in an EVPN-VXLAN network (EX4400-24MP, EX4400-24P, EX4400-24T, EX4400-48F, EX4400-48MP, EX4400-48P, and EX4400-48T) —Starting in Junos OS Release 21.4R1, EX4400 switches in an EVPN-VXLAN network (centrally routed and edge-routed bridging overlays) support dynamic load balancing on virtual tunnel endpoints (VTEPs). Juniper Networks switches have dynamic load balancing enabled by default.

    [See Dynamic Load Balancing in an EVPN-VXLAN Network.]

  • Interconnecting EVPN-VXLAN data centers with EVPN-MPLS in a WAN using gateway nodes (MX-Series, EX9200, EX9252, EX9253)—Starting in Junos OS Release 21.4R1, you can interconnect EVPN-VXLAN data centers with EVPN-MPLS in a WAN using gateway nodes, but without using logical tunnel interfaces. In Release 21.4R1, you can interconnect only those BDs/VLANs that are on the interconnected VLAN list. Note that the gateway nodes in one data center will have connectivity by means of virtual tunnel end points (VTEPs), whereas gateway nodes must be able to handle EVPN-VXLAN encapsulation on the data center side and EVPN-MPLS on the WAN (data center interconnect) side.

    EVPN interconnect CLI commands:

    [See Technology Overview of VXLAN-EVPN Integration for DCI.]

  • Symmetric integrated routing and bridging (IRB) with EVPN Type 2 routes (QFX5210)—Starting in Junos OS Release 21.4R1, you can enable symmetric IRB EVPN Type 2 routing on QFX5210 switches in an EVPN-VXLAN 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. To do this, the leaf devices use a special transit VXLAN network identifier (VNI) and Layer 3 interfaces on the associated VLAN to exchange traffic across the VXLAN tunnels.

    We support this feature with:

    • EVPN instances configured using MAC-VRF routing instances.

    • VLAN-aware bundle or VLAN-based Ethernet service types.

    • EVPN Type 5 routing using Layer 3 virtual routing and forwarding (VRF) instances with IRB interfaces for intersubnet reachability.

    This feature was introduced in Junos OS Release 21.3R1-S1.

    [See Symmetric Integrated Routing and Bridging with EVPN Type 2 Routes in EVPN-VXLAN Fabrics and Using a RIOT Loopback Port to Route Traffic in an EVPN-VXLAN Network.]