Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

EVPN

  • Support for single-link targeting on redundant logical tunnel (MX240, MX480, MX960, MX10003, MX1008, and MX10016)—Starting in Junos OS Release 24.2R1, we support single-link targeting. When you configure single-link targeting, all subscribers using the RLT are terminated when the targeted logical tunnel link goes down.

    [See Logical Tunnel Interfaces and Redundant Logical Tunnels].

  • Support for minimum active links on RLT (MX250, MX480, MX960, MX10003, MX10008, and MX10016)—Starting in Junos OS Release 24.2R1, you can configure a minimum number of active links on a redundant logical tunnel (RLT) interface. When the number of up logical tunnel links in the RLT drops below the configured minimum, the RLT goes down. Pseudowire interfaces stacked on the same RLT also go down in this scenario.

    [See Logical Tunnel Interfaces, Redundant Logical Tunnels, Pseudowire Configuration, and Pseudowire Headend Termination (PWHT)].

  • RFC7432 compliance for VLAN-based EVPN with an IRB interface (MX960)—Starting in Junos OS Release 24.2R1, we've added a new CLI statement advertise-zero-ethernet-tag for VLAN-based EVPN instances using an IRB interface to provide Layer 3 gateway (L3GW) functionality. You use this configuration to advertise EVPN Type 2 (MAC/IP Advertisement) and EVPN Type 3 (Inclusive Multicast Ethernet Tag) routes with an Ethernet tag value of 0 for RFC7432 compliance when the instance has a valid vlan-id. This statement enables a VLAN-based service to provide L3GW functionality with a vlan-id configured and still be RFC7432 compliant for Layer 2 gateway (L2GW) functionality by advertising EVPN routes with an Ethernet Tag ID set to 0 instead of using the vlan-id.

    [See advertise-zero-ethernet-tag.]

  • EVPN ESI per EVI Instance Support (MX960)—Starting in Junos OS Release 24.2R1, you can provide Ethernet segment ID (ESI) support at the EVPN instance (EVI) level for EVPN VLAN-based service in active-standby redundancy mode. We've introduced a new statement per-evi to support this feature. To enable this feature, configure a unique ESI at the EVI level and configure all access logical interfaces (IFLs) under the EVI with the same ESI value and the per-evi statement. When you enable this feature, the designated forwarder (DF) switches to the non-designated forwarder (NDF) role only when all the access IFLs under the EVI go down. You can avoid traffic interruption by preventing a role switch when a single access IFL fails on the EVI.

    [See per-evi.]

  • Suppress EVPN Type 5 host routes from DCI to DC (EX4400-24MP, EX4400-48F, MX304, QFX5120-32C, QFX5120-48T, QFX5120-48T-VC, QFX5120-48Y, QFX5120-48Y-VC, and QFX5120-48YM)—Starting in Junos OS Release 24.2R1, you can suppress EVPN Type 5 host route advertisements that re-originate from the data center interconnect (DCI) to the local DC. You can achieve better scaling and performance on leaf devices with this feature.

    [See suppress-host-routes-from-dci-to-dc.]

  • Non-revertive preference-based DF election in EVPN-MPLS networks (EX4400-24P, MX960, and vMX)—Starting in Junos OS Release 24.2R1, you can configure non-revertive preference-based designated forwarder (DF) election for an Ethernet segment identifier (ESI) in an Ethernet VPN—MPLS (EVPN-MPLS) network. By default, preference-based DF election for an Ethernet segment identifier (ESI) is revertive, which means:

    • If the EVPN provider edge (PE) device currently in the DF role goes down, the next preferred PE device becomes the new DF.

    • When the old DF comes back up, the DF role reverts to the old DF.

    Changing the current DF role for an ESI frequently can impact traffic flow. To avoid revertive DF role changes, you can now set the non-revertive option at the [edit interfaces name esi df-election-type preference] hierarchy level.

    We also provide new options you can configure to load-balance DF election per EVPN instance (EVI) or per ESI based on the lowest configured preference value or the highest configured preference value, as follows:

    • At the EVI level—Use the designated-forwarder-preference-least option or the designated-forwarder-preference-highest option at the [edit routing-instances evpn-instance-name protocols evpn] hierarchy level.

    • At the ESI level—Use the least option at the [edit interfaces interface-name esi df-election-type preference] or [edit protocols evpn interconnect esi df-election-type preference] hierarchy level.

    [See df-election-type and evpn].

  • [See dot1x.]

  • Support for EVPN-VPWS over SRv6 with micro-SID (MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, and MX10008)—Starting in Junos OS Release 24.2R1, we support Segment Routing for IPv6 (SRv6) underlay feature with micro segment identifier (micro-SIDs) over Ethernet VPN–virtual private wireless service (EVPN-VPWS)..

    Note: The MX series of routers support a single segment identifier with this feature.

    [See Configuring Micro-SIDs in EVPN-VPWS.]