Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

EVPN

  • Configuration statements and show commands for troubleshooting EVPN with L2ALM context history (EX4100-24MP, EX4100-48MP, EX4400-24MP, EX4400-48MP, EX4650, MX204, MX240, MX304, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, MX10016, QFX5110, QFX5120-32C, QFX5120-48T, QFX5120-48Y, QFX5120-48YM, QFX10002, QFX10002-60C, QFX10008, and QFX10016)—You can troubleshoot EVPN issues more effectively using updated configuration statements and show commands with Layer 2 Address Learning Manager (L2ALM) context history output. These tools assist in diagnosing and resolving Layer 2 learning and Ethernet switching context-related problems, enhancing your network management capabilities.

    [See l2-learning, ctxt-history, show l2-learning context-history, and show ethernet-switching context-history.]

  • Exception policy for enhanced OISM to avoid multicast traffic loss on packets with TTL=1 (EX4100-48MP, EX4100-24MP, EX4100-24T, EX4400-24MP, EX4400-24P, EX4400-24T, EX4400-24X, EX4400-48F, EX4400-48MP, EX4400-48P, EX4400-48T, EX4650, MX204, MX240, MX304, MX480, QFX5120-32C, QFX5120-48T, QFX5120-48T-VC, QFX5120-48Y, QFX5120-48Y-VC, and QFX5120-48YM)—Enhanced optimized intersubnet multicast (OISM) routes most multicast traffic on the OISM supplemental bridge domain (SBD) rather than on the source VLAN, even if the destination OISM device hosts the source VLAN. This extra routing decrements a packet’s time-to-live (TTL) more than once, so packets with TTL=1 don't reach the receivers. To avoid this problem on enhanced OISM devices, use the following steps to configure the devices to use the source VLAN instead of the SBD to forward multicast data to remote receivers:

    1. Configure a routing policy policy-name at the [edit policy-options policy-statement] hierarchy level to match the multicast groups (or sources and groups) for which to forward multicast traffic on the source VLAN.

    2. Set the forward-policy policy-name option at the [edit routing-instances VRF-instance-name protocols evpn oism enhanced forward-on-source-bridge-domain] hierarchy level to enable forwarding on the source VLAN instead of on the SBD for the multicast groups (or sources and groups) that match the policy.

    You can configure and apply multiple policies with the forward-policy option.

    [See forward-on-source-bridge-domain and Enhanced OISM Exception Policy to Forward on Source VLAN Instead of SBD for Packets with TTL=1.]

  • New CLI option to prevent host entries from occupying LPM table space ( EX4100-24MP, EX4100-24P, EX4100-24T, EX4100-48MP, EX4100-48P, EX4100-48T, EX4100-F-12P, EX4100-F-12T, EX4100-F-24P, EX4100-F-24T, EX4100-F-48P, EX4100-F-48T, EX4300-MP, EX4400-24MP, EX4400-24P, EX4400-24T, EX4400-24X, EX4400-48F, EX4400-48MP, EX4400-48P, EX4400-48T, EX4650, QFX5120-32C, QFX5120-48T, QFX5120-48T-VC, QFX5120-48Y, QFX5120-48Y-VC, and QFX5120-48YM)—You can prevent host entries from occupying longest prefix match (LPM) table space by configuring the no-host-as-lpm CLI option. This option blocks additional host entries from overflowing into the LPM table, ensuring that routing for these hosts is based solely on LPM routes. To enable this feature, use the set forwarding-options no-host-as-lpm command and restart the Packet Forwarding Engine. This preservation of LPM table space allows for accommodating more subnet routes, enhancing routing efficiency.

    [See Host Entry Overflow Prevention.]

  • NTP-based DF election for Ethernet segments (EX4400-24T and QFX5120-48T)—You can use the NTP-based designated forwarder (DF) election option to synchronize DF elections for multihomed Ethernet segments. This option supports existing DF election algorithms and aligns DF election timing across all devices in the segment. Use this feature to enhance network stability and performance by minimizing loops, duplicates, and traffic discarding.

    To enable this feature, configure the df-election-ntp option under the protocol evpn hierarchy. A newly defined BGP extended community with a time synchronization (T) bit communicates the Service Carving Time (SCT) for synchronized timing.

    [See NTP-Based DF Election.]

  • Optimized EVPN-VXLAN DCI with enhanced OISM and an IPv6 underlay (EX4400-24MP, EX4400-24P, EX4400-24T, EX4400-24X, EX4400-48F, EX4400-48MP, EX4400-48P, EX4400-48T, EX4650, QFX5120-32C, QFX5120-48T, QFX5120-48T-VC, QFX5120-48Y, QFX5120-48Y-VC, and QFX5120-48YM)—You can configure enhanced optimized intersubnet multicast (OISM) and seamless Data Center Interconnect (DCI) with EVPN-VXLAN instances on an IPv6 underlay. In EVPN-VXLAN DCI fabrics with enhanced OISM and an IPv6 underlay, DCI gateway (iGW) devices send EVPN Type 6 Selective Multicast Ethernet Tag (SMET) routes to remote iGW devices when hosts subscribe to multicast groups. iGW devices in the source data center selectively forward multicast traffic for a group across the DCI only if the remote data center has receivers subscribed to that group. Previously, the iGW devices always flooded multicast traffic across the interconnection even when the remote data center had no subscribed receivers.

    [See EVPN-VXLAN DCI Multicast with Enhanced OISM.]

  • VXLAN-GBP profiles with enhanced OISM in EVPN-VXLAN fabrics (EX4100-24MP, EX4100-24P, EX4100-24T, EX4100-48MP, EX4100-48P, EX4100-48T, EX4100-F-12P, EX4100-F-12T, EX4100-F-24P, EX4100-F-24T, EX4100-F-48P, EX4100-F-48T, EX4100-H-12MP, EX4100-H-24F, EX4100-H-24F-DC, EX4100-H-24MP, EX4100-H-24MP-DC, EX4400-24MP, EX4400-24P, EX4400-24T, EX4400-24X, EX4400-48F, EX4400-48MP, EX4400-48MXP, EX4400-48P, EX4400-48T, EX4400-48XP, EX4650, QFX5120-32C, QFX5120-48T, and QFX5120-48Y)—We now support running enhanced optimized intersubnet multicast (OISM) in an EVPN-VXLAN network when you configure the vxlan-gbp-mc-profile VXLAN group-based policy (GBP) unified forwarding table (UFT) profile at the [edit chassis forwarding-options] hierarchy level.

    We don’t assign GBP tags to the multicast traffic. Only nonmulticast traffic carries GBP tags in the VXLAN headers.

    You can use enhanced OISM and VXLAN-GBP with:

    • IPv4 underlay connectivity for the EVPN-VXLAN fabric
    • Intra-VLAN (Layer 2 multicast) and inter-VLAN (Layer 3 multicast) traffic
    • IPv4 multicast traffic with IGMP and IGMP snooping
    • IPv6 multicast traffic with MLD and MLD snooping

    You configure GBP and enhanced OISM together the same way you configure the features separately.

    [See Example: Micro and Macro Segmentation using Group Based Policy in a VXLAN and Optimized Intersubnet Multicast in EVPN Networks.]

  • Support for excluding specific MAC addresses from duplicate MAC detection (EX4100-24MP, EX4100-24T, EX4100-48MP, EX4300-MP, EX4400-24MP, EX4400-24P, EX4400-24T, EX4400-24X, EX4400-48F, EX4400-48MP, EX4400-48P, EX4400-48T, EX4650, QFX5120-32C, QFX5120-48T, QFX5120-48T-VC, QFX5120-48Y, QFX5120-48Y-VC, and QFX5120-48YM)—You can configure an exclusion list for MAC addresses in EVPN networks to prevent legitimate MAC address movements from being marked as duplicates. Use set protocols evpn mac-list list_name mac-address mac_address_with_prefix_len to create the list and set protocols evpn duplicate-mac-detection exclude-list list_name to apply it. This feature helps maintain network stability by avoiding unnecessary duplicate MAC detection for specified addresses, particularly in scenarios involving virtual MAC configurations in redundant setups.

    [See EVPN Duplicate MAC Detection Exclusion Lists.]