Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

MPLS

  • Enhancements to BFD-triggered fast reroute for unicast next hops (ACX7024, ACX7100-32C, ACX7100-48L, and ACX7509 Routers)—Starting in Junos OS Evolved Release 23.2R1, we've enhanced the Bidirectional Forwarding Detection (BFD)-triggered fast reroute (FRR) for unicast next hops. The BFD triggered local repair option is enabled by default.

    When a BFD link goes down at a remote link, BFD triggered repair is enabled on the local device. The BFD session is brought down on the local device PFE, and the routing protocol recalculates a new route. Use the session-id-change-limiter-indirect configuration under the [edit routing] hierarchy to limit the recalculation of parent nodes for the indirect next hop. The convergence is faster resulting in lesser traffic downtime.

    To disable this option, use the command set routing-options no-bfd-triggered-local-repair and restart routing configuration.

    [See Bidirectional Forwarding Detection (BFD) for MPLS, session-id-change-limiter-indirect, and no-bfd-triggered-local-repair.]

  • Support for bound metrics and bandwidth for PCC-initiated and PCC-delegated LSPs (RSVP-TE and SR-TE) according to RFC5440 (PTX10008)—Starting in Junos OS Evolved Release 23.2R1, we support metric object and bandwidth object for bounded constraints in Path Computation Element Protocol (PCEP) connections for segment routing LSPs. Both metric object and bandwidth object are optional objects in PCEP and can be present in PCInit, PCUpd and PCRpt PCEP messages.

    To configure bounded metric values for LSP controllers, use the igp-metric-bound <val> | te-metric-bound <val> | delay-metric-bound <val> statement at the [edit protocols mpls label-switched-path <lsp-name> lsp-external-controller controller-name] hierarchy level.

    To configure bounded metric values for compute profiles, use the bound-metric igp <val> | bound-metric te <val> | bound-metric delay <val> at the [edit protocols source-packet-routing compute-profile compute-profile-name] hierarchy level.

    To use the maximum SR-MPLS segment identifier (SID) depth, use the set protocols pcep maximum-srmpls-segment-list-depth <val> configuration command.

    To propogate the list, use the set protocols pcep propagate-lsp-max-segment-list-depth configuration command.

    [See lsp-external-controller, compute-profile, and pcep.]

  • Support for IPv6 L3VPN over IPv6 SR-TE and IPv6 underlay (ACX7024, ACX7100-32C, ACX7100-48L, and ACX7509)—Starting in Junos OS Evolved Release 23.2R1, you can configure an IPv6 Layer 3 VPN (L3VPN) connection with an IPv6 local address and an IPv6 neighbor address. You can connect an IPv6 provider edge (PE) device with a colored or non-colored IPv6 penultimate next-hop (PNH) address mapped to IPv6 segment routing–traffic engineering (SR-TE) tunnels.

    [See Understanding Static Segment Routing LSP in MPLS Networks and Link-State Distribution Using BGP Overview.]

  • Support to report bandwidth and reservation priority for delegated and PCE-initiated segment routing–traffic engineering (SR-TE) LSPs in Path Computation Element Protocol (PTX10008)—Starting in Junos OS Evolved Release 23.2R1, we support the reporting of bandwidth and reservation priority for delegated SR-TE LSPs. For PCE-initiated SR-TE LSPs, once the bandwidth, setup priority, and reservation priority request is received from the controller, the Path Computation Client (PCC) reports the same information to the controller.

    Note:

    You can configure bandwidth and reservation priority in PCC only for delegated SR-TE LSPs and not for undelegated and PCE-Initiated SR-TE LSPs.

    To configure the bandwidth-requested and bandwidth-reservation-priority for delegated SR-TE LSPs, include the bandwidth-requested | bandwidth-reservation-priority configuration statements at the [edit protocols source-packet-routing compute-profile compute-profile-name] hierarchy level.

    [See Reporting Path Optimization Metrics in PCEP.]