Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

EVPN

  • Clone BGP routes between VRF RIBs (MX204, MX240, MX304, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, and MX10016)—You can clone a primary or secondary BGP route from one virtual routing and forwarding (VRF) routing information base (RIB) to another VRF RIB. You can also clone the route from a VRF RIB to either the inet.0 or inet6.0 table.

    [See rib-exports (Routing Options) and rib-export-strip (Policy Options).]

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

  • Uplink protection for network isolation detection (MX204, MX240, MX304, MX480, MX960, MX10004, MX10008, MX2008, MX2010, and MX2020)—With uplink protection support, you can manage network isolation by automatically shutting down Layer 2 (L2) interfaces when core isolation is detected and bringing them back up after the isolation state is cleared. This feature prevents the occurrence of traffic loops in L2 multiaccess BGP or EVPN services and improves traffic failover for multihomed customer edges during network disruptions. You can configure hold times to delay L2 interfaces' reactivation, allowing Layer 3 (L3) protocols to converge and routes to synchronize. Additionally, maintenance options enable you to bring multiple L2 interfaces up or down collectively, facilitating easier network management.

    [See Uplink Protection for Network Isolation.]