Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?



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

  • Optimized inter-subnet multicast support with symmetric bridge domain configuration in an EVPN-VXLAN fabric (QFX5110, QFX5120, QFX10002-36Q, and QFX10002-72Q)—Starting in Junos OS Release 21.2R1, you can configure optimized inter-subnet multicast (OISM) on leaf devices and border leaf devices in an EVPN-VXLAN edge-routed bridging overlay fabric. This feature helps optimize the routing of multicast traffic across VLANs in an EVPN tenant domain. This feature uses a supplemental bridge domain (SBD) and a multicast VLAN (MVLAN) to route multicast traffic from or to devices outside of the fabric. This feature also works with existing IGMP snooping and selective multicast (SMET) forwarding optimizations to minimize replication in the EVPN core when bridging within tenant VLANs.

    With this implementation, you must enable OISM and IGMP snooping on all the leaf and border leaf devices in the EVPN-VXLAN fabric. You also must configure the SBD and all tenant VLANs symmetrically on all leaf and border leaf devices in the fabric.

    You can use OISM with:

    • EVPN on the default-switch instance with VLAN-aware bundle service model (Layer 2)
    • Routing instances of type vrf (Layer 3)
    • EVPN single-homing or multihoming (all-active mode)
    • IGMPv2
    • Multicast sources and receivers within the EVPN data center
    • Multicast sources and receivers outside the EVPN data center that are reachable through the border leaf devices

    [See Optimized Inter-Subnet Multicast in EVPN Networks.]

  • Overlapping VLAN support for edge-routed bridging in an EVPN-VXLAN fabric (QFX5110 and QFX5120)—Starting in Junos OS Release 21.2R1, you can map the host VLAN to the VLAN that is provisioned on the leaf device by using VLAN translation. The host VLAN is translated to the VLAN that is already configured on the leaf device before the packet is processed. Conversely, the packet egresses from the access port with the translated VLAN.

    [See vlan-rewrite.]