Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?



  • Port-based VLAN bundle services for EVPN (EX9200)—Starting in Junos OS Release 21.2R1, Junos OS supports port-based VLAN bundle services for EVPN on the EX9200 switch. The port-based VLAN bundle service maps the VLANs on a port to the same bundle service.

    [See VLAN Bundle Service for EVPN.]

  • EVPN Type 2 and Type 5 route coexistence (EX4650, QFX5110, QFX5120, and QFX10002)—Starting in Junos OS Release 21.2R1, we support the coexistence of EVPN Type 2 and Type 5 routes in EVPN-VXLAN edge-routed bridging overlay fabrics. This feature enables more efficient traffic flow and better usage of Packet Forwarding Engine resources. The switch applies a preference algorithm when you enable Type 5 routes. For any destinations for which the switch has no Type 5 route, the switch uses Type 2 routes by default. Otherwise, the switch gives preference to:

    • Type 2 routes for local ESI interfaces (locally learned routes)
    • Type 5 routes for all other destinations within the data center or across data centers

    You can refine these preferences by configuring routing policies in the EVPN routing instance to control the Type 5 routes that the switch imports and exports.

    [See EVPN Type 2 and Type 5 Route Coexistence with EVPN-VXLAN.]

  • Enhancement in the number of supported VLANs and ports (EX4400-24P, EX4400-24T, EX4400-48F, EX4400-48P, and EX4400-48T switches)—Starting with Junos OS Release 21.2R1, we have increased the combined total number of VLANs and ports that can be supported on the EX4400 switches. The number of supported VLANs remains at 4093, but Junos OS no longer limits the total number of ports and VLANS that can be configured on EVPN-VXLAN. This enhancement applies only when you use the enterprise style of configuration when configuring the interfaces.

    [See Understanding EVPN with VXLAN Data Plane Encapsulation.]