Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

MPLS

  • Support for MLDP recursive forwarding equivalence class (FEC) (PTX10008)—Starting in Junos OS Evolved Release 23.4R1, we partially support RFC 6512. We've introduced the recursive opaque value type for the MLDP forwarding equivalence class (FEC) element. The recursive opaque value helps to form MLDP point-to-multipoint (P2MP) tunnels between two autonomous systems (ASs), where the intermediate nodes do not have the route to reach the root node.

    To enable the recursive opaque value, configure the fec statement at the [edit protocols ldp p2mp recursive] hierarchy level.

    [See Understanding Multipoint LDP Recursive FEC.]

  • Computation of unreserved bandwidth optimized RSVP dynamic bypass LSP (ACX7024, ACX7100-32C, ACX7100-48L, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 23.4R1, the Constrained Shortest Path First (CSPF) can optionally use a different approach to protect a link or a node by leveraging the computation based on unreserved bandwidths on traffic engineering (TE) links. To enable this feature, use the optimize bandwidth configuration statement at the edit protocols rsvp interface interface link-protection hierarchy level. While the default approach of RSVP bypass produces a bypass method that optimizes traffic engineering (TE) metric, enabling the new configuration statement maximizes the end-to-end unreserved bandwidth.

    [See Configuring Link Protection on Interfaces Used by LSPs.]

  • Capability to compute diverse paths between a set of LSPs (PTX10008)—Starting in Junos OS Evolved Release 23.4R1, you can associate a group of LSPs (RSVP LSPs or SR MPLS LSPs) to the Path Computation Element Communication Protocol (PCEP) to compute diverse paths for the associated LSPs. The Junos PCC advertises to a Path Computation Element (PCE) that a particular LSP belongs to a diversity-association group. RFC 8800 defines PCEP protocol extensions to associate a set of LSPs that belong to the same association group. This enables a PCE to compute diverse paths for each of the LSPs in each diversity association group and then push the results to the PCC. A PCE can also associate set of LSPs across different PCCs.

    You can enable diversity-association capability in the open message by configuring the following statement:

    After enabling diversity-association capability, you need to also configure the diversity-association group using the following statement:

    For RSVP LSPs:

    For SR LSPs:

    You can provision and delegate the following LSPs:

    • Provision PCE initiated RSVP LSPs with diverse paths

    • Delegate RSVP LSPs with diverse association groups

    • Provision PCE initiated SR MPLS uncolored LSPs with diverse paths

    • Delegate SR MPLS uncolored LSPs with diverse association groups

    • Provision PCE initiated SR MPLS colored LSPs with diverse paths

    • Delegate SR MPLS colored LSPs with diverse association groups

    • Provision PCE initiated SRv6 colored LSPs with diverse paths

    • Delegate SRv6 colored LSPs with diverse association groups

    • Provision PCE initiated SRv6 uncolored LSPs with diverse paths

    • Delegate SRv6 uncolored LSPs with diverse association groups

    [See PCEP Configuration.]

  • Map static IPv6 route to next-hop using service label (ACX7100-32C, ACX7100-48L, ACX7509, ACX7024,PTX10001-36MR, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 23.4R1, you can enable static IPv6 routes to be mapped to the next-hop over an IPv4 MPLS network. 6PE is a transitional IPv6 over IPv4 technology that uses MPLS tunnels to carry services.

    You can use the explicit-null configuration statement under the [edit routing-options rib inet6.0 static route ipv6-address] hierarchy level to push ingress service label as part of the static next hop configuration for static IPv6 routes. The explicit-null configuration statement only supports configuring IPv4 mapped IPv6 address.

    The static configuration statement under the [edit routing-options forwarding-table chained-composite-next-hop ingress] hierarchy provisions chained composite next-hop.

    Note:

    The static configuration statement must be enabled before configuring the explicit-null configuration statement.

  • PCE requests to allocate binding SIDs for SR-TE Colored LSPs (PTX10008)—Starting in Junos OS Evolved Release 23.4R1, a Path Computation Element (PCE) can request Path Computation Client (PCC) to allocate a binding SID from PCC’s label space. PCE can request PCC to allocate a specific binding SID and can also allocate binding SID of PCC’s choice.

    The following PCEP operations are now supported:

    • PCE requests PCC to allocate binding SID of PCC’s choice for delegated LSPs

    • PCE requests PCC to allocate binding SID of PCC’s choice for PCE-Initiated LSPs

    • PCE requests PCC to allocate a specific binding SID for delegated LSPs

    • PCE requests PCC to allocate a specific binding SID for PCE-Initiated LSPs

    • BGP LS for binding SID for colored SR LSP

    The following SRTE binding SID database and label show commands has been introduced to display all binding SIDs with brief and detail outputs:

    • show spring-traffic-engineering binding-sid database brief

    • show spring-traffic-engineering binding-sid database detail

    • show spring-traffic-engineering binding-sid database label label brief

    • show spring-traffic-engineering binding-sid database label label detail

    • show spring-traffic-engineering binding-sid label label brief

    • show spring-traffic-engineering binding-sid label label detail

    [See PCEP Configuration.

  • New CLI commands for MPLS LSPs (ACX7100-32C, ACX7100-48L, ACX7509, ACX7024, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved 23.4R1, you can get more visibility into the current state of the MPLS LSPs on the router to debug suspected anomalies in high scale conditions with the following newly introduced CLI commands.

    • show rsvp session bypass [bypass-name] [protected] and show rsvp session [unprotected] provides visibility into LSPs protected by a specific bypass tunnel.

    • show mpls lsp [make-before-break] and show rsvp session [multiple-lsp-sessions] provides sisibility into LSPs undergoing make-before-break.

    • show mpls tunnel-manager-statistics provides statistics on all local repair and make-before-break events for LSPs.

    • show rsvp session [fr-ingress] provides visibility into LSPs on flood-reflector edge routers.

  • PCC Policy Association with SR and RSVP LSP (PTX10008)—Starting in Junos OS Evolved 23.4R1, PCC (Path Computation Clients) can link policies with a group of Label Switched Paths (LSPs). This enhancement allows Junos PCC to communicate with a Path Computation Element (PCE) using an extended communication protocol (PCEP). Through this extension, Junos PCC can tell the PCE that a specific LSP is part of a certain Policy Association Group.