Juniper ACX2000 Configuration Guide

Table 47: Applicability of MPLS and Existing LSP Configurations to a
PCE-Controlled LSP
Applicable MPLS
Configuration
Statements
Applicable LSP
Configuration
StatementsSupport for PCE-Controlled LSP
•
admin-group
•
admin-groups
•
admin-group-extended
•
hop-limit
•
no-cspf
•
smart-optimize-timer
•
admin-group
•
auto-bandwidth
•
hop-limit
•
least-fill
•
most-fill
•
random
These configuration statements can be
configured along with the PCE configuration.
However, they take effect only when the local
configuration is in use. During PCE control, these
configuration statements remain inactive.
•
priority
•
bandwidth
•
primary
•
priority
These configuration statements can be
configured along with the PCE configuration,
but are overridden by the PCE-controlled LSP
attributes. However, when the local
configuration is in use, the configured values for
these configuration statements are applied.
NOTE: Changes to the local configuration using
the CLI while the LSP is under the control of a
stateful PCE do not have any effect on the LSP.
These changes come into effect only when the
local configuration is applied.
•
p2mp-lsp-next-hop
•
p2mp
•
template
These configuration statements cannot be
configured along with the PCE configuration.
The rest of the LSP configuration statements are applicable in the same way as for
existing LSPs. On configuring any of the above configuration statements for a
PCE-controlled LSP, an MPLS log message is generated to indicate when the configured
parameters take effect.
PCE-Controlled LSP Protection
The protection paths, including fast reroute and bypass LSPs, are locally computed by
the PCC using constraint-based routing. A stateful PCE specifies the primary path (ERO)
only. A PCE can also trigger a non-standby secondary path, even if the local configuration
does not have a non-standby secondary path for LSP protection.
PCE-Controlled LSP ERO
For PCE-controlled LSPs (PCC-delegated LSPs and PCE-initated LSPs), only a full-blown
Explicit Route Object (ERO) object has to be sent from the PCE to the PCC; otherwise
the PCC rejects the PCUpdate or PCCreate message for that PCEP session.
Starting in Junos OS Release 17.2, in addition to external cspf, two new path computation
types are introduced for the PCE-controlled LSPs: local cspf and no cspf.
•
local cspf—A PCC uses the local cspf computation type only when the PCE sends in a
Juniper Vendor TLV (enterprise number: 0x0a4c) of type 5.
703Copyright © 2017, Juniper Networks, Inc.
Chapter 23: Configuring Path Computation Element Protocol (PCEP)

Juniper ACX2000 Specifications

General

Brand	Juniper
Model	ACX2000
Category	Network Router
Language	English