Juniper ACX1000 Configuration Manual page 780

ACX Series Universal Access Router Configuration Guide
722
Overview
Starting with Junos OS Release 16.1, the PCEP functionality is extended to allow a stateful
PCE to initiate and provision traffic engineering LSPs through a PCC. Earlier, the LSPs
were configured on the PCC and the PCC delegated control over the external LSPs to a
PCE. The ownership of the LSP state was maintained by the PCC. With the introduction
of the PCE-initiated LSPs, a PCE can initiate and provision a traffic engineering LSP
dynamically without the need for a locally configured LSP on the PCC. On receiving a
PCCreate message from a PCE, the PCC creates the PCE-initiated LSP and automatically
delegates the LSP to the PCE.
By default, a PCC rejects the request for provisioning PCE-initiated LSPs from a PCE. To
enable support of PCE-initated LSPs on the PCC, include the lsp-provisioning statement
at the
[edit protocols pcep pce pce-id]
levels.
A PCC indicates its capability of supporting PCE-initiated LSPs while establishing the
Path Computation Element Protocol (PCEP) session with the PCE. A PCE selects a PCC
with this capability to initiate an LSP. The PCE provides the PCC with the PCE-initiated
LSP parameters. On receiving the PCE-initiated LSP parameters, the PCC sets up the
LSP, assigns an LSP ID, and automatically delegates the LSP to the PCE.
When the PCE initiating the LSP does not provide the PCE-initiated LSP parameters, the
PCC uses the default parameters. An optional LSP template may also be configured to
specify values for the PCE-initiated LSP when the LSP parameters are not provided by
the PCE. To configure an LSP template for PCE-initiated LSPs on the PCC, include the
label-switched-path-template statement at the
hierarchy level.
lsp-external-controller]
When a PCEP session terminates, the PCC starts two timers without immediately deleting
the PCE-initiatedLSPs— delegation cleanup timeout
disruption of services. During this time, an active stateful PCE can acquire control of the
LSPs provisioned by the failed PCE.
A PCE may return the delegation of the PCE-initiated LSP to the PCC to allow LSP transfer
between PCEs. Control over PCE-initiated LSPs reverts to the PCC at the expiration of
the delegation cleanup timeout. When the delegation cleanup timeout expires, and no
other PCE has acquired control over the LSP from the failed PCE, the PCC takes local
control of the non-delegated PCE-initiated LSP. Later, when the original or a new active
stateful PCE wishes to acquire control of the locally controlled PCE-initiated LSPs, the
PCC delegates these LSPs to the PCE and the LSP cleanup timer is stopped.
The PCC waits for the LSP cleanup timer to expire before deleting the non-delegated
PCE-initiated LSPs from the failed PCE. When the LSP cleanup timer expires, and no
other PCE has acquired control over the LSPs from the failed PCE, the PCC deletes all
the LSPs provisioned by the failed PCE.
or
[edit protocols pcep pce-group group-id]
[edit protocols mpls lsp-external-controller
and lsp cleanup timer
Copyright © 2017, Juniper Networks, Inc.
hierarchy
—to avoid