Configuring Path Computation And Control For Sr-Te Lsps; Configuring Path Profile And Group For Pcc-Initiated And Pce-Computed/Controlled Lsps - Nokia 7705 SAR-W Series Manual

MPLS and RSVP-TE
Use the following CLI syntax to associate an empty path or a path with strict or loose
explicit hops with the primary paths of the SR-TE LSP:
CLI Syntax:
3.23.3 Configuring Path Computation and Control for
Use the following syntax to configure the path computation requests only (PCE-
computed) or both path computation requests and path updates (PCE-controlled) to
the PCE for a specific LSP:
CLI Syntax:
The PCC LSP database is synchronized with the PCE LSP database using the
PCEP PCRpt (PCE Report) message for LSPs that have the following commands
enabled:
CLI Syntax:
3.23.3.1
The PCE supports the computation of disjoint paths for two different LSPs originating
or terminating on the same or different PE routers. To indicate this constraint to the
PCE, the user must configure the PCE path profile ID and path group ID that the LSP
belongs to. These parameters are passed transparently by the PCC to the PCE and
are therefore opaque data to the router. Use the following syntax to configure the
path profile and path group:
CLI Syntax:
150
config>router>mpls>path>hop hop-index ip-address {strict
| loose}
config>router>mpls>lsp>primary path-name
SR-TE LSPs
config>router>mpls>lsp>pce-computation
config>router>mpls>lsp>pce-control
config>router>mpls>pce-report sr-te {enable | disable}
config>router>mpls>lsp>pce-report {enable | disable |
inherit}
Configuring Path Profile and Group for PCC-initiated and
PCE-computed/controlled LSPs
config>router>mpls>lsp>path-profile profile-id [path-
group group-id]
Use subject to Terms available at: www.nokia.com
© 2022 Nokia.
MPLS Guide
3HE 18686 AAAB TQZZA