EVPN

BGP auto-discovery underlay (RFC5549) for EVPN-VXLAN (QFX5230-64CD, QFX5240-64OD, and QFX5240-64QD)—Simplify the EVPN-VXLAN underlay network by auto-discovering the eBGP peer neighbors using the link-local IPv6 addresses. The EVPN MAC-VRF RT2 and RT5 IPVRF EVPN-VXLAN are both supported for the overlays when running the RFC5549 BGP unnumbered in the underlay BGP. While the underlay links run the IPv6 link-local, the EVPN-VXLAN overlay can still use the IPv4 tunnel termination using the embedded advertisement.

Support for multicast IGMPv2v3/MLDv2 SMET in a bridged-overlay Layer 2 EVPN-VXLAN (QFX5130-32CD, QFX5130-48C, QFX5130-48CM, and QFX5700)—A bridged overlay EVPN-VXLAN design with these QFX models provide Ethernet bridging between leaf devices in an EVPN network. This bridge overlay extends VLANs between the leaf devices across VXLAN tunnels. Bridged overlays provide an entry-level overlay style for data center networks that require Ethernet connectivity but do not need routing services between the VLANs.

The bridged overlay EVPN-VXLAN can be a leaf-spine type of topology offering ESI-LAG multihoming or collapsed spine topology where two devices are back-to-back connected and provide the Layer 2 active/active multihoming with the ESI-LAG. The IGMP/MLD snooping in a bridged overlay constrains multicast traffic in a broadcast domain to interested receivers. In the absence of IGMP/MLD snooping, multicast traffic is treated like broadcast and is flooded in the broadcast domain. The feature supports the bridged scenario for EVPN-VXLAN where the leaves are just used for bridging purposes. The MAC-VRF instance-type with EVPN multicast related route-types RT3, RT6, RT7, and RT8 are supported with this multicast feature. Supports VLAN-based and VLAN-aware EVPN service types.

Multicast router interface synchronization for IGMPv2v3/MLDv2 SMET in bridged-overlay EVPN-VXLAN (QFX5130-32CD, QFX5130-48C, QFX5130-48CM, and QFX5700)—A bridged overlay EVPN-VXLAN design with these QFX models provide Ethernet bridging between leaf devices in an EVPN network. When an external PIM router gateway is connected to a bridged-overlay pair of border-leaf in a leaf-spine EVPN-VXLAN bridged-overlay topology, or in a collapsed spine bridged-overlay through the ESI-LAG and the explicit multicast router interface is enabled to the gateway, then to support the DF/NDF logic at the ESI-LAG level, the multicast router synchronization functionality is required for the EVPN control-plane. This is needed because from the external PIM router gateway connected to the EVPN-VXLAN bridged-overlay through the ESI-LAG, the IGMP/MLD query will be hashed to any one of the member links of the bundle, so a synchronization of the state is required.