MPLS
-
Support for bound metrics and bandwidth for PCC Initiated/Delegated type LSPs (RSVP-TE and SR-TE) per RFC5440 (ACX5448, ACX5448-M, ACX5448-D, ACX710, MX204, MX240, MX304, MX150, MX480, MX960, MX10003, MX10004, MX10008, MX10016, MX2008, MX2010, MX2020, and vMX)—Starting in Junos OS Release 23.2R1, we support metric object and bandwidth object for bounded constraints in a Path Computation Element Protocol (PCEP) connection for Segment Routing label-switched paths (SR-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 an LSP controller, you can enter
igp-metric-bound <val> | te-metric-bound <val> | delay-metric-bound <val>
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, you can enter
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.To propogate the list, use the
set protocols pcep propagate-lsp-max-segment-list-depth
configuration.[See lsp-external-controller, compute-profile, and pcep.]
-
Support to report bandwidth and reservation priority for delegated and PCE-initiated segment routing–traffic engineering (SR-TE) LSPs in Path Computation Element Protocol (ACX5448, ACX5448-M, ACX5448-D, ACX710, MX150, MX204, MX240, MX304, , MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, MX10016, and vMX)—Starting in Junos OS Release 23.2R1, we support the reporting of bandwidth and reservation priority for delegated segment routing–traffic engineering (SR-TE) label-switched paths (LSPs). For Path Computation Client (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
andbandwidth-reservation-priority
for delegated SR-TE LSPs, include thebandwidth-requested | bandwidth-reservation-priority
configuration statement at the[edit protocols source-packet-routing compute-profile compute-profile-name]
hierarchy level.