Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Connectivity Services Director User Guide
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Configuring PCEP on a PE Router (from CLI)

date_range 17-Oct-23

A Path Computation Client (PCC) supports the configurations related to the Path Computation Element (PCE) and communicates with the CSD-Topology, which by default is configured to accept a Path Computation Element Protocol (PCEP) connection from any source address. However, you must configure PCEP on each PE router to configure the router as a PCC and establish a connection between the PCC and the CSD-Topology. A PCC initiates path computation requests, which are then executed by the CSD-Topology.

The following requirements apply for each PCC in the network that the CSD-Topology can access:

  • The corresponding JSDN package (with PCEP support) is installed on the router.

Note:

You must boot the PCC router with the Junos OS 14.2X1.1 image, and then boot the router a second time with the JSDN image. After the router boots up a second time, the router (functioning as a PCC) is able to support the configurations related to the PCE and communicate with the CSD-Topology.

Note:

For a PCEP connection, the PCC can connect to the CSD-Topology using an in-band or out-of-band management network, provided that IP connectivity is established between the Path Computation Server (PCS) and the specified PCEP local address. In some cases, an additional static route might be required from the CSD-Topology to reach the PCC, if the IP address is unreachable from the CSD-Topology default gateway.

To configure a PE router as a PCC:

  1. Enable external control of LSPs from the PCC router to the CSD-Topology.
    content_copy zoom_out_map
    [edit protocols]
    user@PE1# set mpls lsp-external-controller pccd
    
  2. Specify the loopback address of the PCC router as the local address, for example:
    content_copy zoom_out_map
    [edit protocols]
    user@PE1# set pcep pce csdtopology local-address 10.0.0.101
    
    Note:

    As a best practice, the router ID is usually the loopback address, but is not necessarily configured this way.

  3. Specify the CSD-Topology (csdtopology) as the PCE that the PCC connects to, and specify the CSD-Topology host external IP address as the destination address.
    content_copy zoom_out_map
    [edit protocols]
    user@PE1# set pcep pce csdtopology destination-ipv4-address 10.99.99.1
    
  4. Configure the destination port for the PCC router that connects to the CSD-Topology (PCE server) using the TCP-based PCEP.
    content_copy zoom_out_map
    [edit protocols]
    user@PE1# set pcep pce csdtopology destination-port 4189
    
  5. Configure the PCE type.
    content_copy zoom_out_map
    [edit protocols]
    user@PE1# set pcep pce csdtopology pce-type active
    user@PE1# set pcep pce csdtopology pce-type stateful
    
  6. Enable LSP provisioning.
    content_copy zoom_out_map
    [edit protocols]
    user@PE1# set pcep pce csdtopology lsp-provisioning
    
  7. To verify that PCEP has been configured on the router, open a telnet session to access the router, and run the following commands:
    content_copy zoom_out_map
    user@PE1> show configuration protocols mpls

    Sample output:

    content_copy zoom_out_map
    lsp-external-controller pccd;
    
    content_copy zoom_out_map
    user@PE1> show configuration protocols pcep

    Sample output:

    content_copy zoom_out_map
    pce csdtopology {
        local-address 10.0.0.101; 
        destination-ipv4-address 10.99.99.1;
        destination-port 4189;
        pce-type active-stateful;
        lsp-provisioning;
    }
    
footer-navigation