MPLS

Computation of unreserved bandwidth optimized RSVP dynamic bypass LSP (MX204, MX240, MX304, MX480, MX960, MX10003, MX10008, MX10016, MX2008, MX2010, MX2020, QFX10008, and QFX10016)—Starting in Junos OS 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.]

Map static IPv6 route to next-hop using service label (MX204, MX240, MX304, MX480, MX960, MX10003, MX10004, MX10008, MX10016, MX2008, MX2010, MX2020, virtual-chassis-fabric, QFX10002-60C, QFX10002, QFX10008, and QFX10016)—Starting in Junos OS 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.