Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

EVPN

  • Optimized intersubnet multicast in an EVPN-VXLAN fabric (QFX5130-32CD, and QFX5700)—Starting in Junos OS Evolved Release 22.1R1, you can configure these platforms as optimized intersubnet multicast (OISM) server leaf and border leaf devices in an EVPN-VXLAN ERB overlay fabric.

    To support OISM on these platforms, you must configure:

    • EVPN instances of type mac-vrf with vlan-aware or vlan-based service types. (See MAC-VRF Routing Instance Type Overview.)

    • Tenant L3 routing instances with instance-type vrf.

    • A supplemental bridge domain (SBD) and all tenant VLANs on all OISM devices in the fabric.

    • IGMP snooping on all OISM devices in the fabric.

    If you need to route multicast traffic from or to devices outside of the fabric, you can’t use an OISM multicast VLAN (M-VLAN) for external multicast routing on these platforms. You can configure one of the following methods with PIM for external multicast on the border leaf devices:

    • Classic L3 interfaces to the external multicast rendezvous point (RP).

    • Non-EVPN VLANs and corresponding IRB interfaces to the external multicast RP.

    You can use OISM on these platforms with IGMPv2 or IGMPv3, and IGMP snooping. (See Overview of Multicast Forwarding with IGMP Snooping or MLD Snooping in an EVPN-VXLAN Environment.)

    [See Optimized Intersubnet Multicast in EVPN Networks.]

  • Overlapping VLAN support in EVPN-VXLAN fabrics on edge-routed bridging (ERB) overlay leaf devices (QFX5130-32CD and QFX5700)—Starting in Junos OS Evolved Release 22.1R1, we support overlapping host VLANs with access-side enterprise style interfaces on leaf devices. To enable a leaf device to process an overlapping host VLAN tag, configure the vlan-rewrite translate statement on an interface. Use this statement to map the host VLAN to a VLAN configured on the leaf device (which we refer to as the mapped VLAN value). The device processes incoming tagged packets using the mapped VLAN value instead of the host VLAN tag. On egress, the device translates the mapped VLAN value back into the host VLAN tag.

    [See Overlapping VLAN Support Using VLAN Translation in EVPN-VXLAN Networks and vlan-rewrite.]