[edit protocols pcep]
user@PCC# commit
commit complete
Related
Documentation
Support of the Path Computation Element Protocol for RSVP-TE Overview on page 692•
• Example: Configuring Path Computation Element Protocol for MPLS RSVP-TE with
Support of PCE-Initiated LSPs on page 721
• pcep on page 1657
Example: Configuring Path Computation Element Protocol for MPLS RSVP-TE with Support
for PCE-Controlled Point-to-Multipoint LSPs
This example shows how to configure the Path Computation Client (PCC) with the
capability of reporting point-to-multipoint traffic engineered label-switched paths (TE
LSPs) to a Path Computation Element (PCE).
•
Requirements on page 735
•
Overview on page 735
•
Configuration on page 736
•
Verification on page 746
Requirements
This example uses the following hardware and software components:
•
Three routers that can be a combination of ACX Series, M Series, MX Series, or T Series
routers.
•
One virtual machine configured with Virtual Route Reflector (VRR) feature.
•
A TCP connection to an external stateful PCE from the VRR.
•
Junos OS Release 16.1 or later running on the PCC.
Before you begin:
•
Configure the device interfaces.
•
Configure MPLS and RSVP-TE.
•
Configure OSPF or any other IGP protocol.
Overview
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.
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.
735Copyright © 2017, Juniper Networks, Inc.
Chapter 23: Configuring Path Computation Element Protocol (PCEP)
To Next Page
Loading...
Need help?
General
