Feature configuration

The following MPLS-level and LSP-level CLI commands, used to configure RSVP-TE LSPs in a router acting as a PCEP Client (PCC):

config>router>mpls>pce-report rsvp-te {enable | disable}
config>router>mpls>lsp>path-profile profile-id range [path-group group-id range]
config>router>mpls>lsp>pce-report {enable | disable | inherit}
config>router>mpls>lsp>path-computation-method pce
config>router>mpls>lsp>pce-control

Note: The PCE function implemented in the NSP and referred to as the Network Resource Controller for Packet (NRC-P), supports only Shared Explicit (SE) style bandwidth management for TE LSPs. The PCEP protocol does not have means for the PCC to convey this value to the PCE. So, regardless of whether the LSP configuration option rsvp-resv-style is set to se or ff, the PCE always uses the SE style in the CSPF computation of the path for a PCE-computed or PCE-controlled RSVP-TE LSP.

A one-hop-p2p or a mesh-p2p RSVP-TE auto-lsp only supports the pce-report command in the LSP template:

config>router>mpls>lsp-template>pce-report {enable | disable | inherit}

The user must first shut down the LSP template before changing the value of the pce-report option.

A manual bypass LSP does not support any of the PCE-related commands. Reporting a bypass LSP to PCE is not required because it does not book bandwidth.

All other MPLS, LSP, and path-level commands are supported, with the exception of backup-class-type, class-type, least-fill, main-ct-retry-limit, mbb-prefer-current-hops, and srlg (on secondary standby paths), which, if enabled, results in a no operation.

The same instantiation modes are supported for RSVP-TE PCC-initiated LSPs as the SR-TE PCC-initiated LSPs. See LSP initiation for more information.