Juniper ACX2000 Configuration Guide

•
no cspf—Neither the PCE nor the PCC performs a constrained path calculation. The
endpoints and constraints are given to the RSVP module for setting up the LSP with
the IGP path.
A PCC uses no cspf computation type in the following cases:
•
When the PCE sends local cspf TLV, and when the Junos OS configuration or matching
template for this LSP included no-cspf in the PCC-delegated LSP.
•
When the PCE sends local cspf TLV, and when the Junos OS configuration template
for this LSP included no-cspf in the PCE-initiated LSP.
•
When the PCE does not send local cspf TLV with an empty ERO or loose ERO (with
loose bit set in the ERO object).
With these new computation types, a PCC can accept an ERO object either as a loose
ERO, or as an empty ERO. An external path computing entity that is not capable of
computing a path can modify parameters such as bandwidth and color, based on the
analytics. In such cases, an empty ERO object or loose ERO is used and the path to be
taken is decided by the PCC.
PCE Controlled Point-to-Multipoint RSVP-TE LSPs
After a PCEP session is established between a PCE and a PCC, the PCC reports all the
LSPs in the system to the PCE for LSP state synchronization. This includes PCC-controlled,
PCE-delegated, and PCE-initiated point-to-point LSPs. Starting with Junos OS Release
15.1F6 and 16.1R1, this capability is extended to report point-to-multipoint LSPs as well.
For a PCE, the point-to-multipoint LSP is similar to that of RSVP point-to-multipoint
LSP, where the point-to-multipoint LSP is treated as collection of point-to-point LSPs
grouped under a point-to-multipoint identifier.
By default, PCE control of point-to-multipoint LSPs is not supported on a PCC. To add
this capability, include the p2mp-lsp-report-capability statement at the [edit protocols
pcep pce pce-name] or [edit protocols pcep pce-group group-id] hierarchy levels. After
the point-to-multipoint report capability is configured on a PCC, the PCC advertises this
capability to the PCE. If the PCE advertises the same point-to-multipoint report capability
in return, then the PCC reports the complete point-to-multipoint LSP tree to the PCE for
LSP state synchronization.
A PCC with the point-to-multipoint TE LSP capability supports reporting of
point-to-multipoint TE LSPs for stateful PCEs, point-to-multipoint update, and LSP
database supporting point-to-multipoint LSP name as key. However, the following
features and functions are not supported for Junos OS Release 15.1F6 and 16.1:
•
Static point-to-multipoint LSPs
•
PCE-delegated and PCE-initiated point-to-multipoint LSPs
•
Auto-bandwidth
•
TE++
•
PCE request and reply message
•
Creation of point-to-multipoint LSPs using templates
Copyright © 2017, Juniper Networks, Inc.704
ACX Series Universal Access Router Configuration Guide

Juniper ACX2000 Specifications

General

Brand	Juniper
Model	ACX2000
Category	Network Router
Language	English