pce
Syntax
pce pce-id {
authentication-key key;
authentication-key-chain key-chain;
delegation-cleanup-timeout seconds;
delegation-priority priority-number;
destination-ipv4-address ipv4-address;
destination-port port-number;
local-address ip-address;
lsp-cleanup-timer seconds;
lsp-provisioning;
lsp-retry-delegation;
lsp-retry-delegation-timer seconds;
max-sid-depth max-sid-depth;
max-unknown-messages messages-per-minute;
max-unknown-requests requests-per-minute;
p2mp-lsp-init-capability;
p2mp-lsp-report-capability;
p2mp-lsp-update-capability;
pce-group pce-group-name;
pce_traffic_steering;
pce-type ;
request-timer seconds;
request-priority priority;
spring-capability;
srv6-capability;
traceoptions ;
Hierarchy Level
[edit protocols pcep]
Description
Configure per-Path Computation Element (PCE) parameters.
Options
| pce-id | IP address of the PCE. |
| authentication-key key | (Optional) Authentication password. It can be up to 126 characters. Characters can include any ASCII strings. If you include spaces, enclose all characters in quotation marks (“ ”). It is recommended to define and bind an authentication key for securing a PCEP session, as opposed to binding an authentication keychain. |
| authentication-key-chain key-chain | (Optional) Authentication keychain password. It can be up to 126 characters. Characters can include any ASCII strings. If you include spaces, enclose all characters in quotation marks (“ ”). |
| local-address ip-address | (Optional) IP address of the local end of the PCEP session, the PCC. |
| lsp-retry-delegation | (Optional) Enable retry LSP delegation process. |
| lsp-retry-delegation-timer | (Optional) Specify the amount of time (in seconds) that the Path Computation Client (PCC) must wait before retrying delegation of Path Computation Element (PCE)-initiated LSPs in case of delegation failure or re-delegation.
|
| max-sid-depth | (Optional) Specify the maximum value for service identifier (SID) depth.
|
| p2mp-lsp-init-capability | (Optional) Capability to provision point-to-multipoint RSVP-TE LSPs by a PCE. By default, this capability is not supported on a PCC, and should be explicitly configured to enable PCE-initated point-to-multipoint LSPs. |
| p2mp-lsp-report-capability | (Optional) Capability to report point-to-multipoint RSVP-TE LSPs to a PCE. By default, this capability is not supported on a PCC, and should be explicitly configured to enable reporting of point-to-multipoint LSPs to a PCE. |
| p2mp-lsp-update-capability | (Optional) Capability to update point-to-multipoint RSVP-TE LSP parameters by a PCE. By default, this capability is not supported on a PCC, and should be explicitly configured to enable updating of PCE-initated point-to-multipoint LSPs. |
| pce_traffic_steering | (Optional) Configure the flow specification capability (also called traffic steering functionality) for enabling the mapping of PCE-initiated point-to-multipoint LSPs to an MVPN routing-instance. |
| spring-capability | (Optional) Enable SPRING-based provisioning for the PCE. |
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 12.3.
Support for PTX Series added in Junos OS Release 14.2.
Support for QFX Series switches added in Junos OS Release 16.1R3.
Support for ACX Series added in Junos OS Release 17.1R1.
lsp-cleanup-timer, lsp-provisioning, max-unknown-requests, request-timer, and request-priority options introduced in Junos OS Release 13.3.
authentication-key key, authentication-key-chain key-chain, and p2mp-lsp-report-capability options introduced in Junos OS Release
16.1.
max-sid-depth and spring-capability options
introduced in Junos OS Release 17.2.
p2mp-lsp-init-capability and p2mp-lsp-update-capability options introduced in Junos OS Release
18.3R1 on all platforms.
pce_traffic_steering option introduced in Junos OS
Release 19.4R1 on all platforms.