How do I create PCE-initiated LSPs?

Purpose

Note: Before a PCE-initiated LSP can be successfully created, certain commands must be executed on the source node. See the NSP Release Description for more information.

Steps

From the Path Control, LSPs view, click on Create PCE-Init LSP . The Create PCE-Init LSP form opens with the Identification panel displayed.

Configure the required parameters:

Parameter	Description
Path Name	The name of the PCE-initiated LSP
PCC Address	The address of the PCC
Source	Specifies the source node for the path
Destination	Specifies the destination node for the path
Administration	Specifies the desired administrative state
Template ID	Specifies the ID of the template to be applied
Path Type	Specifies the type of path (must be Segment Routing)
Objective	Specifies the primary goal when identifying path resources
Bandwidth (Mbps)	Specifies the bandwidth required for the LSP
Setup Priority	Specifies a diversity-grouped LSP's priority access to the shortest path. Value 0 is the highest priority.
Assign BSID	Specifies whether or not a BSID will be assigned to the LSP

In the Constraints panel, configure the required parameters:

Parameter	Description
Max Hops (Span)	Specifies the maximum number of hops to consider
MSD	Specifies the maximum SID depth to consider
Max Cost	Specifies the maximum cost to consider
Max TE Metric	Specifies the maximum TE metric to consider
Max Latency	Specifies the maximum latency to consider
Include Any Bit Pos	Specifies any bit between 0 and 31 to include
Exclude Any Bit Pos	Specifies any bit between 0 and 31 to exclude
Include All Bit Pos	Specified all bits between 0 and 31 to include

In the Association Groups panel click + ADD. The Create Association Groups form opens. Configure the required parameters:

Parameter	Description
Association Type	Specifies the association type. PCE-initiated LSPs only support the 'Policy' type.
Association Group ID	Specifies the association group identifier. When the Association Type is set to 'Policy', the Association Group ID is used to perform a lookup against a Path Profile definition. An ID is limited to one per association type. If multiple association groups exist, the association with the lowest ID will be used.
Association Source IP Address	Specifies the IP address of the association source. Both IPv4 and IPv6 addresses are supported.

Click ADD. The Create Association Group form closes.

In the Path Profiles panel, configure the required parameters:

Parameter	Description
Profile ID	Specifies the identifier of the path profile policy to apply
Group ID	Specifies the identifier of the path profile group to which this LSP belongs

Click CREATE. The PCE-initiated LSP is created.

From the LSPs view, a variety of actions can be performed on individual PCE-initiated LSPs by clicking More and choosing the desired action from the contextual menu. These actions include show on map, re-signal, optimize, edit, shutdown, no shutdown, delete, and configure path profile override. See How do I apply a path profile override? for more information.

Note: When an LSP is re-signaled, a search is conducted for the constrained shortest path, and the LSP is rerouted to a new, best path (if one is found). The best path is determined by the LSP's objective. When all LSPs are re-signaled, they are rerouted one by one. Therefore, each previous reroute affects the viability of future reroutes. LSPs can be re-signaled on-demand at any time, though NSP periodically re-signals LSPs at set intervals.

Note: When LSPs are optimized, a set of LSPs are analyzed simultaneously, and paths are routed with the goal of producing a network with minimal bandwidth utilization on each link. Because multiple LSPs are optimized at once, there is a significant computation cost and impact to the network, however, the paths are routed with awareness and consideration of each other.

End of steps

Use subject to agreed restrictions on disclosure and use.