Pcc-Initiated And Pcc-Controlled Lsps - Nokia 7705 SAR-W Series Manual

MPLS Guide
The global MPLS- level pce-report command can be used to enable or disable PCE
reporting for all SR-TE LSPs for the purpose of LSP database synchronization. This
configuration is inherited by all LSPs of a particular type. The PCE reports both CSPF
and non-CSPF LSPs. The default value is disabled (no pce-report). This default
value controls the introduction of the PCE into an existing network and allows the
operator to decide if all LSP types need to be reported.
The LSP-level pce-report command overrides the global configuration for PCE
reporting for an LSP. The default value is to inherit the global MPLS-level value. The
inherit value reconfigures the LSP to inherit the global configuration for that LSP
type.
Note: If PCE reporting is disabled for the LSP, either due to inheritance or due to LSP-level
configuration, enabling the pce-control option for the LSP has no effect. To help
troubleshoot this situation, operational values of both the pce-report and pce-control are
added to the output of the LSP show commands.
For more information about configuring PCC-initiated and PCC-controlled LSPs, see
Configuring PCC-controlled, PCE-computed, and PCE-controlled SR-TE
3.12.2.1
For PCC-initiated and PCC-controlled LSPs, the user configures the LSP name,
primary path name, and optional secondary path name with the path information in
the referenced path name, entering a full or partial explicit path with all or some hops
to the destination of the LSP. Each hop is specified as an address of a node or an
address of the next hop of a TE link. Optionally, each hop can be specified as a SID
value that corresponds to the MPLS label to use on a hop. If this option is used, the
whole path must consist of SIDs.
To configure the primary path or secondary path to always use a specific link
whenever it is up, the strict hop must be entered as an address corresponding to the
next hop of an adjacency SID. If the strict hop corresponds to a loopback address, it
is translated to an adjacency SID as explained below and therefore there is no
guarantee that the same TE link is picked.
To use an SR-TE path that consists of unprotected adjacency SIDs, each hop of the
path must be configured as a strict hop with the address matching the next hop of the
adjacency SID and protection on each of these adjacencies must be disabled as
explained in
3HE 18686 AAAB TQZZA

PCC-initiated and PCC-controlled LSPs

SR-TE LSP Path
Use subject to Terms available at: www.nokia.com
Computation.
© 2022 Nokia.
MPLS and RSVP-TE
LSPs.
93