Provision MPLS LSPs using Device Configuration

Purpose

Use this procedure to configure MPLS LSPs using the Device Management views. This procedure is based on the overall device configuration procedure in the NSP Device Management Guide.

For example, the reference procedure in NSP Release 24.4 is ICM Process

The intent type required is icm-te-tunnel.

Prerequisites

Intent types must be installed and imported to NSP; see Install the required artifact bundles.

For this use case, the following parameters must be configured:

  • egress-statistics must be enabled on the LSPs of the NE. This parameter may be enabled by default upon provisioning, depending on the NE type.

  • pce-report - this parameter must be enabled for the LSP to appear in Path Control in NSP. This attribute is enabled by default upon provisioning.

Steps
Import the intent type
 

Log in the NSP.


Open Device Management, Configuration Intent Types.


Click png6.pngIMPORT


Choose the icm-te-tunnel intent type from the list and click IMPORT.


Create a configuration template
 

Open Device Management, Configuration Templates.


Click png6.pngTEMPLATE


In the form that opens, enter a name for the template.

Note: Template names cannot start or end with a space, or contain special characters other than spaces, underscores, or hyphens.


Click png6.png INTENT TYPE and choose the icm-te-tunnel intent type.


Choose a configuration form from the drop-down list.


10 

Click RELEASE to create the template in released state.

The configuration template is added to the list.


Deploy the configuration
 
11 
  1. Open Device Management, Configuration Templates.

  2. From the list, choose a template you created in the previous steps and click png3.png (More actions) Deploy to Network.

    The form opens with the template already selected.


12 

Choose the target NE:

  1. Click png6.png TARGET and choose NEs from the drop-down list.

  2. Choose an NE from the list to add to the Bin.

  3. Verify that the correct NE is shown in the Bin and click ADD.


13 

  1. Click VIEW/EDIT TEMPLATE CONFIG.

  2. In the form that opens, configure the template parameters. The following parameters are required:

    • A primary path must be added:

      Use Path Computation must be enabled 

      path-computation-method must be path-locally-computed

    • Signaling Type must be RSVP.

    • An association object must be created, with the path profile associated to the LSP.

      The path profile is created in Path Control; see Create a bandwidth-based path profile and Create a latency-based path profile

      It is not necessary to create path profiles before performing this procedure.

  3. Click UPDATE.

In this example, no secondary path is provisioned.


14 

Identifier fields appear in the form for each selected template. Enter information in each field.

Attention: Your input can’t contain the hash symbol (#).


15 

Click DEPLOY to apply the configuration to the targets.


Audit the configuration
 
16 

Perform an audit to verify that the configuration has deployed correctly:

  1. Open Device Management, Configuration Deployments.

  2. Choose a deployment.

  3. Click png39.png if needed to open the Deployment Details panel.

  4. Click AUDIT CONFIG. The audit results and alignment status information are updated.


Repeat to deploy other LSPs
 
17 

Repeat this procedure to deploy all other LSPs. Ensure that the correct path profile is assigned to each LSP.

End of steps

LSP creation example, template parameters