Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

EVPN

  • Convergence improvements for EVPN-VPWS (ACX7020-AC, ACX7020-AC-C, ACX7020-DC, ACX7020-DC-C, ACX7024, ACX7024X, ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, PTX10001-36MR, PTX10002-36QDD, PTX10003, PTX10004, PTX10008, and PTX10016)—We've introduced EVPN-VPWS convergence enhancements on the ACX Series and PTX Series routers. With this feature, the router now supports route acknowledgment for EVPN-VPWS routes, extending the existing mechanism currently used for BGP routes. The router advertises an EVPN-VPWS route to its neighbor only after it confirms that:

    • The route has been successfully installed in the forwarding table of the Packet Forwarding Engine
    • The route version in the routing information base (RIB) matches the version in the forwarding information base (FIB) .

    If there are any acknowledgment errors, the router withdraws the EVPN-VPWS routes from the Packet Forwarding Engine. This ensures that EVPN-VPWS routes are reliably installed in hardware and that the versions are synchronized across the RIB and the FIB.

    By default, required acknowledgment from the PFE prior to advertising the EVPN-VPWS route is automatically enabled. To disable the acknowledgment requirement, include the evpn-vpws-ack-disable statement at the [edit routing-options forwarding-table] hierarchy level. Disabling the acknowledgment requirement only affects new EVPN-VPWS instances and does not impact the network.

    [See forwarding-table.]

  • EVPN VPWS and FXC with BGP-LU PIC (ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, ACX7024, and ACX7024X) —Support is added for EVPN VPWS and Flexible Cross-Connect (FXC) services in VLAN-aware and VLAN-unaware modes. BGP-LU PIC enables fast convergence for single-homing, multihoming all-active, and multihoming single-active deployments. This feature is supported across RSVP-TE, LDP, ISIS FlexAlgo, and SR-MPLS transport modes, with or without Per-Next-Hop (PNH) optimization.

    Note: For VPWS and FXC, BGP-LU PIC with PNH is not supported when the transport path uses SR-TE. In addition, BGP-PIC edge is not applicable or qualified from the control plane, and BGP-LU PIC convergence cannot be achieved without a PNH configuration.

    [See Overview of VPWS with EVPN Signaling Mechanisms.]

  • NSR and HA for EVPN VPWS Using BGP-LU PIC (ACX7332, ACX7348, and ACX7509)—Support is added for Nonstop Routing (NSR) and High Availability (HA) with EVPN VPWS, maintaining forwarding state and service continuity during Routing Engine switchover events.

    [See Overview of VPWS with EVPN Signaling Mechanisms.]

  • BGP-LU PIC with Entropy Label support (ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, ACX7024, and ACX7024X) —Support is added for entropy labels in BGP-LU to improve load balancing across equal-cost MPLS paths and optimize traffic distribution.

    [See Configuring Entropy Labels and entropy-label (protocols bgp)]

  • EVPN-VPWS service over SRv6 underlay with BGP-LU PIC (ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, ACX7024, and ACX7024X)—Configure single-active or all-active multi homed EVPN VPWS networks using segment routing over IPv6 (SRv6).

    To enable EVPN-VPWS over SRv6, configure the following:

    1. Include the end-dx2-sid statement at the [edit routing-instances instance-name protocols evpn source-packet-routing srv6 locator name] hierarchy level or at the [edit routing-instance routing-instance-name protocols evpn interface interface-name] hierarchy level for the evpn-vpws instance type.

    2. Enable advertise-srv6-service and accept-srv6-service in the [edit protocols bgp group name family evpn] hierarchy level.

      [See Configuring VPWS with EVPN Signaling Mechanisms and Understanding SRv6 Network Programming and Layer 3 Services over SRv6 in BGP.]