Cisco Crosswork Planning Design 7.2.x User Guide

Create and visualize LSPs and LSP paths

Updated: August 14, 2026

Want to summarize with AI?

Describes how to create and visualize MPLS LSPs within the network design interface.

To simulate MPLS LSPs in the network, you must first set up the LSPs to be routed. Use this task to create and visualize LSPs from the UI.

Procedure

	1.	Open the plan file (refer to Open plan files ). It opens in the Network Design page.
	2.	From the toolbar, choose Actions > Insert > LSPs > LSP. Alternatively, in the Network Summary panel on the right side, click > LSPs in the LSPs tab. The LSPs tab is available under the More tab. If it is not visible, then click the Show/hide tables icon () and check the LSPs check box.
	3.	Choose the Type, which determines whether this is an RSVP LSP or an SR LSP.
	4.	In the Name field, enter the name of the LSP.
	5.	Select the Active or FRR enabled check box.
	6.	Expand the Source & destination panel. Choose the appropriate source and destination site and node details.
	7.	(Optional) Expand the other panels (Routing, CSPF, and Other) and enter the relevant parameters.
	8.	Save your changes.
	9.	To visualize the LSP in the network plot, select the LSP from the LSPs table. They appear in the plot as purple arrows. Figure 1. LSP visualization

To add a mesh of LSPs between the selected nodes, use any of these options:
- From the toolbar, choose Actions > Insert > LSPs > LSP mesh.
- In the Network Summary panel on the right side, click > LSP mesh in the LSPs tab.
To filter to related information such as related interfaces, source and destination nodes, demands, or LSP paths, select the LSP, click , and choose the appropriate option.

Need help?

Open a support case

(Requires a Cisco Service Contract)

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.