Configuring the Ingress as a PCE Client

A PCE client can be configured on the ingress so that the ingress establishes a PCEP session with a PCE server and sends a request to the server over the session to calculate a path.

Usage Scenario

Different from CSPF configured on the ingress, the PCE algorithm allows a PCE server to configure and manage network-wide TE information, including node, link, and tunnel attributes. Some steps are mandatory when CSPF is used but optional when PCE is used.

If the ingress has to delegate LSPs only in some TE tunnels to the PCE server, it must report information about both delegated and undelegated LSPs to the PCE server, to help the PCE server correctly calculate global bandwidth information. To implement partial LSP delegation, perform either of the following configurations:

Configure the ingress to delegate LSPs in all TE tunnels to the PCE server. Then, configure the ingress to report LSP information on a specified tunnel interface to the PCE server and withdraw the LSP delegation from the PCE server.
Configure the ingress to report information about LSPs in all TE tunnels to the PCE server, without delegating the LSPs to the PCE server. Then, configure the ingress to delegate the LSP on a specified TE tunnel interface to the PCE server.

Perform the following steps on the ingress:

Procedure

Run system-view
The system view is displayed.
Run pce-client
The ingress is configured as a PCE client, and the PCE client view is displayed.
Run quit
Return to the system view.
Run mpls
The MPLS view is displayed.
(Optional) Run mpls te pce cleanup lsp-state
The PCE client is enabled to automatically degrade to use the local path calculation function if the involved PCEP session fails.

If a PCE server fails or a PCEP connection is interrupted, to properly establish an MPLS TE tunnel, the PCE client must be able to automatically degrade to use the local path calculation function. If CSPF is configured locally, it is used for path computation. If CSPF is not configured, routes are used.
Select either of the following solutions:
- Solution 1: applicable when most LSPs need to be delegated
  1. Run mpls te pce delegate (MPLS view)
    
    The ingress is configured to delegate LSPs in all local TE tunnels to the PCE server.
  2. Run quit
    
    Return to the system view.
  3. Run interface tunnel tunnel-number
    
    The specified TE tunnel interface view is displayed.
  4. Run mpls te pce passive-delegate report-only (Tunnel interface view)
    
    The LSP information of the current tunnel is reported to the PCE server, but the LSP is not delegated to the PCE server.
- Solution 2: applicable when only a few LSPs need to be delegated
  1. Run mpls te pce passive-delegate report-only (MPLS view)
    
    The LSP information of all local tunnels is reported to the PCE server, but the LSP is not delegated to the PCE server.
  2. Run quit
    
    Return to the system view.
  3. Run interface tunnel tunnel-number
    
    The specified TE tunnel interface view is displayed.
  4. Run mpls te pce delegate (Tunnel interface view)
    
    The LSPs of the current tunnel are delegated to the PCE server.
Run commit
The configuration is committed.