Usage Scenario
When PCE is used to calculate a path for an MPLS TE tunnel, the ingress must be configured as a PCE client. If the ingress has to delegate LSPs only in some TE tunnels to the PCE server, the ingress must report information about both delegated and undelegated LSPs to the PCE server, which helps the PCE server correctly calculate global bandwidth information. To implement partial LSP delegation, perform either of the following configurations:
- Run the mpls te pce delegate command in the MPLS view to enable the ingress to delegate LSPs in all TE tunnels to the PCE server. Then run the mpls te pce passive-delegate report-only command in a specified TE tunnel interface view to enable the ingress to report LSP information on the specified TE tunnel to the PCE server and withdraw LSP delegation from the PCE server.
- Run the mpls te pce passive-delegate report-only command in the MPLS view to enable the ingress to only report LSP information on all TE tunnels to the PCE server. Then run the mpls te pce delegate command in a specified TE tunnel interface view to enable the ingress to delegate LSPs in the specified TE tunnel to the PCE server.
Prerequisites
MPLS TE has been enabled using the mpls te command.
The tunneling protocol has been set to MPLS TE using the
tunnel-protocol mpls te command on the tunnel interface.
Precautions
If both the mpls te pce passive-delegate report-only and mpls te pce delegate commands are run in the MPLS view, the later configuration overrides the previous one.
If both the mpls te pce passive-delegate report-only and
mpls te pce delegate commands are run in the same tunnel interface view, the later configuration overrides the previous one.
PCE is in conflict with ordinary CR-LSP backup.
PCE is in conflict with best-effort CR-LSP backup.
PCE is in conflict with P2MP TE.