Prerequisites for SR: PCE Initiated LSPs
- The Dynamic PCC feature must be configured.
- Auto tunnels must be enabled on the PCC.
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The SR: PCE Initiated LSPs feature provides support for PCE-initiated LSPs in stateful PCE model on segment routing networks.
The SR: PCE Initiated LSPs feature supports only basic LSP generation and does not support TE attributes.
draft-ietf-pce-stateful-pce-21 describes Stateful Path Computation Element Protocol (PCEP) enables a router to report and optionally delegate Label Switched Paths (LSPs) which is established using either Resource Reservation Protocol (RSVP) protocol or Segment Routing Traffic Engineering (SR-TE) to a stateful Path Computation Element (PCE). An LSP delegated to a PCE can be updated by the PCE and a stateful PCE can compute and provide the path of an LSP to the Path Computation Client (PCC).
The PCEP Extensions for PCE-initiated LSP Setup in a Stateful PCE Model (draft-ietf-pce-pce-initiated-lsp-11) specifies a set of extensions to PCEP to enable stateful control of TE LSPs across PCEP sessions in compliance with RFC4657. The PCEP Extensions for PCE-initiated LSP Setup in a Stateful PCE Model provides information about the following:
Configuring LSPs on a PCC
Delegating control of LSP to a PCE
The SR: PCE Initiated LSPs feature allows a client to create, setup, control, and delete an LSP from PCE server, which controls creating and deleting LSP on PCC through an PCE initiate message. PCE initiated LSP is automatically delegated to the PCE server that initiated the LSP. A PCE client processes an LSP initiate message. By using the LSP initiate message, PCE client can create or delete LSP.
When a failover occurs on a route processor (RP), the failover results in the RP being disconnected from the network. To reestablish the connection, the PCE server has to resend LSP initiate message to reclaim PCE Initiated LSPs on a client, else PCE initiated LSPs created by the client are automatically deleted.
You must use the pce command for establishing a PCEP session with PCC. The force auto-route command is used to advertise an LSP within an area via the autoroute announce message and across areas via the autoroute destination message. The decision to use autoroute announce or autoroute destination is performed by a device depending on the destination IP address. Enabling the force auto-route command for an initiated LSP allows automatic routing of traffic through a TE tunnel instead of routing traffic via manually configuring static routes. The autoroute announce message installs routes announced by the destination router and downstream routers into the routing table of a headend device that can be reached through a tunnel.
The PCC configuration includes IP addresses for each PCE (both primary and standby or more). The precedence for each PCE can be explicitly specified. If the precedence for two PCEs is same, PCE with smaller IP address has a higher precedence.
The SR: PCE Initiated LSPs feature supports single and redundant PCE operations. In a single PCE operation, when a PCE fails, PCC waits until the state timeout expiry (60 seconds) to remove the LSP.
In a redundant PCE operation, if a Representational state transfer (REST) call is initiated to a standby PCE before the expiry of the timer, the initiated LSP is retained else, the LSP is removed.
![]() Note |
The REST call must be initiated again to a standby PCE if the primary PCE fails, and the call must include the standby PCE IP address. |
In a redundant PCE operation, PCC configurations include both primary and standby IP addresses for an LSP and the IP address with a lower precedence becomes the primary PCE. The IP addreseses are compared incase of equal priority.
Perform this task to configure a PCEP session PCE server XR based XTC server.
configure terminal
pce
address ipv4 192.0.2.1
end
The IP address 192.0.2.1 is the IP address of the transport controller.
configure terminal
mpls traffic-eng pcc peer 192.0.2.1 source 203.0.113.1 force-autoroute
end
In the above code snippet, 192.0.2.1 is PCE IP address and 203.0.113.1 is PCC source address for establishing a PCEP session.
configure terminal
mpls traffic-eng pcc peer 192.0.2.1 source 203.0.113.1 force autoroute precedence 255
mpls traffic-eng pcc peer 192.0.2.2 source 203.0.113.1 force-autoroute precedence 100
end
In the above code snippet, 100 is a lower precedence than 255, which is the default precedence. Therefore, the device with IP address 192.0.2.2 becomes the primary PCE and the device with 192.0.2.1 becomes the standby PCE.
A change in a PCE server’s precedence is not considered a PCE server failure. So, the change in precedence does not trigger a redelegation timeout or a re-evaluation of LSP delegation to the PCE server at a PCC.
Re-evaluation of LSP delegation to PCE servers after CLI reconfiguration is controlled by the TE reoptimisation timer. By default, the TE reoptimisation timer is set to 3600 seconds.
mpls traffic-eng reoptimize
Step 1 |
show pce ipv4 peer detail Use this command to verify PCEP session details on a PCE. In this example, the term instantiation indicates that PCE supports initiated LSP.
|
Step 2 |
show pce lsp detail Use this command to verify the initiated LSP on a PCE.
|
Step 3 |
show pce client peer Use this command to verify a PCEP session output on a PCC and to verify if the force-autoroute command is enabled.
|
Step 4 |
show mpls traffic-eng tunnel tunnel number Use this command to verify the output of the initiated LSP tunnel on a PCC.
|
Standard/RFC |
Title |
---|---|
draft-ietf-pce-pce-initiated-lsp-11 |
PCEP Extensions for PCE-initiated LSP Setup in a Stateful PCE Model |
RFC 5440 |
Path Computation Element (PCE) Communication Protocol (PCEP) |
RFC 8231 |
Path Computation Element (PCE) Communication Protocol Generic Requirements |
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to https://cfnng.cisco.com/. An account on Cisco.com is not required.
Feature Name |
Releases |
Feature Information |
---|---|---|
SR: PCE Initiated LSPs |
Cisco IOS XE Amsterdam 17.3.2 |
The SR: PCE Initiated LSPs provides support for PCE-initiated LSPs in stateful PCE model on segment routing networks. The following commands were introduced or modified: mpls traffic-eng pcc, pce, show mpls traffic-eng tunnel, show pce client peer, show pce ipv4 peer, show pce lsp . |