MPLS and RSVP-TE
150
MPLS Guide
© 2022 Nokia.
Use subject to Terms available at: www.nokia.com
3HE 18686 AAAB TQZZA
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: config>router>mpls>path>hop hop-index ip-address {strict
| loose}
config>router>mpls>lsp>primary path-name
3.23.3 Configuring Path Computation and Control for
SR-TE LSPs
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: config>router>mpls>lsp>pce-computation
config>router>mpls>lsp>pce-control
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: config>router>mpls>pce-report sr-te {enable | disable}
config>router>mpls>lsp>pce-report {enable | disable |
inherit}
3.23.3.1 Configuring Path Profile and Group for PCC-initiated and
PCE-computed/controlled LSPs
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: config>router>mpls>lsp>path-profile profile-id [path-
group group-id]
To Next Page
Loading...
Need help?
General
