Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Provision LSP

 

LSPs can be provisioned using either PCEP or Netconf. For Netconf, unlike PCEP, the NorthStar Controller requires periodic device collection to learn about LSPs and other updates to the network. See Scheduling Device Collection for Analytics via Netconf for more information. Once you have created Netconf collection tasks, NorthStar Controller should be able to discover LSPs provisioned via Netconf. Also unlike PCEP, the NorthStar Controller with Netconf supports logical systems.

To provision an LSP, navigate to Applications>Provision LSP. The Provision LSP window is displayed as shown in Figure 1.

Figure 1: Provision LSP Window, Properties Tab
Provision LSP Window, Properties
Tab
Note

You can also reach the Provision LSP window from the Tunnel tab of the Network Information pane by clicking the Add button at the bottom of the pane.

As shown in Figure 1, the Provision LSP window has several tabs:

  • Properties

  • Path

  • Advanced

  • Design

  • Scheduling

From any tab, you can click Preview Path at the bottom of the window to see the path drawn on the topology map, and click Submit to complete the LSP provisioning. These buttons become available as soon as Name, Node A, and Node Z have been specified.

Table 1 describes the data entry fields in the Properties tab of the Provision LSP window.

Table 1: Provision LSP Window, Properties Fields

Field

Description

Provisioning Method

Use the drop-down menu to select PCEP or NETCONF. The default is PCEP.

Note: At this time, NorthStar Controller supports Netconf provisioning only on Juniper devices.

Name

A user-defined name for the tunnel. Only alphanumeric characters, hyphens, and underscores are allowed. Other special characters and spaces are not allowed. Required for primary LSPs, but not available for secondary or standby LSPs.

Node A

Required. The name or IP address of the ingress node. Select from the drop-down list. You can start typing in the field to narrow the selection to nodes that begin with the text you typed.

Node Z

Required. The name or IP address of the egress node. Select from the drop-down list. You can start typing in the field to narrow the selection to nodes that begin with the text you typed.

IP Z

IP address of Node Z.

Provisioning Type

Use the drop-down menu to select RSVP or SR (segment routing) for PCEP LSPs. Only RSVP is available for NETCONF.

Path Type

Use the drop-down menu to select primary, secondary, or standby as the path type.

secondary (or standby) for

LSP name. Required and only available if the Path Type is set to secondary or standby. Identifies the LSP for which the current LSP is secondary (or standby).

Path Name

Required and only available primary LSPs if the provisioning type is set to RSVP, and for all secondary and standby LSPs. Name for the path.

Planned Bandwidth

Required. Bandwidth immediately followed by units (no space in between). Valid units are:

  • B or b (bps)

  • M or m (Mbps)

  • K or k (Kbps)

  • G or g (Gbps)

Examples: 50M, 1000b, 25g.

If you enter a value without units, bps is applied.

Setup

Required. RSVP setup priority for the tunnel traffic. Priority levels range from 0 (highest priority) through 7 (lowest priority). The default is 7, which is the standard MPLS LSP definition in Junos OS.

Hold

Required. RSVP hold priority for the tunnel traffic. Priority levels range from 0 (highest priority) through 7 (lowest priority). The default is 7, which is the standard MPLS LSP definition in Junos OS.

Planned Metric

Static tunnel metric. Type a value or use the up and down arrows to increment or decrement by 10.

Comment

Free-form comment describing the LSP.

The Path tab includes the fields shown in Figure 2 and described in Table 2.

Figure 2: Provision LSP Window, Path Tab
Provision LSP Window, Path
Tab

Table 2: Provision LSP Window, Path Fields

Field

Description

Selection

Use the drop-down menu to select dynamic, required, or preferred.

Hop 1

Only available if your initial selection is either required or preferred. Enter the first hop and specify whether it is strict or loose. To add an additional hop, click the + button.

The Advanced tab includes the fields shown in Figure 3 and described in Table 3.

Figure 3: Provision LSP Window, Advanced Tab
Provision LSP Window,
Advanced Tab

Table 3: Provision LSP Window, Advanced Fields

Field

Description

Coloring Include All

Double click in this field to display the Modify Coloring Include All window. Select the appropriate check boxes. Click OK when finished.

Coloring Include Any

Double click in this field to display the Modify Coloring Include Any window. Select the appropriate check boxes. Click OK when finished.

Coloring Exclude

Double click in this field to display the Modify Coloring Exclude window. Select the appropriate check boxes. Click OK when finished.

P2MP Name

Only available if the Provisioning Method is set to NETCONF. If you provision multiple LSPs with the same P2MP name, the LSPs are grouped together under that name in the Topology view. See Access the Left Pane Options for information about viewing P2MP groups.

Symmetric Pair Group

When there are two tunnels with the same end nodes but in opposite directions, the path routing uses the same set of links. For example, suppose Tunnel1 source to destination is NodeA to NodeZ, and Tunnel2 source to destination is NodeZ to NodeA. Selecting Tunnel1-Tunnel2 as a symmetric pair group places both tunnels along the same set of links. Tunnels in the same group are paired based on the source and destination node.

Create Symmetric Pair

Select the checkbox to create a symmetric pair.

Diversity Group

Name of a group of tunnels to which this tunnel belongs, and for which diverse paths is desired.

Diversity Level

Use the drop-down menu to select the level of diversity as default, site, link, or SRLG.

Route on Protected IP Link

Select the check box if you want the route to use protected IP links as much a possible.

The Design tab includes the fields shown in Figure 4 and described in Table 4.

Figure 4: Provision LSP Window, Design Tab
Provision LSP Window,
Design Tab

Table 4: Provision LSP Window, Design Fields

Field

Description

Routing Method

Use the drop-down menu to select a routing method. Available options include default, adminWeight, delay, constant, distance, ISIS, OSPF, and routeByPCC.

Max Delay

Type a value or use the up and down arrows to increment or decrement by 100.

Max Hop

Type a value or use the up and down arrows to increment or decrement by 1.

Max Cost

Type a value or use the up and down arrows to increment or decrement by 100.

High Delay Threshold

Type a value or use the up and down arrows to increment or decrement by 100.

Low Delay Threshold

Type a value or use the up and down arrows to increment or decrement by 100.

High Delay Metric

Type a value or use the up and down arrows to increment or decrement by 100.

Low Delay Metric

Type a value or use the up and down arrows to increment or decrement by 100.

When provisioning via PCEP, the NorthStar Controller’s default behavior is to compute the path to be used when provisioning the LSP. Alternatively, you can select the routeByPCC routing method in the Design tab, in which the router controls part of the routing. This alternate routing method is only meaningful for two types of LSP:

  • RSVP TE PCC-controlled LSP

    Note

    For provisioning via Netconf, routeByPCC is the default routing method.

  • Segment routing PCE-initiated LSP

To select this alternate routing method:

  1. On the Design tab, select routeByPCC from the Routing Method drop-down menu.
  2. On the Path tab, select dynamic from the Selection drop-down menu.

The LSP is then set up to be provisioned with the specified attributes, and no explicit path.

The Scheduling tab relates to bandwidth calendaring. By default, tunnel creation is not scheduled, which means that tunnels are provisioned immediately upon submission. Click the Scheduling tab in the Provision LSP window to access the fields for setting up the date/time interval. Figure 5 shows the Scheduling tab of the Provision LSP window.

Figure 5: Provision LSP Window, Scheduling Tab
Provision LSP
Window, Scheduling Tab

Select Once to select start and end parameters for a single event. Select Daily to select start and end parameters for a recurring daily event. Click the calendar icon beside the fields to select the start and end dates, and beginning and ending times.

Note

The time zone is the server time zone.

Click Submit when you have finished populating fields, and the LSP is added to the Tunnel tab of the network information table.

Note

In Junos OS Release 15.1F6 and later, you can enable the router to send P2MP LSP information to a controller (like the NorthStar Controller) in real time, automatically. Without that configuration, you must run device collection for NorthStar to learn about newly provisioned P2MP LSPs.

In the Junos OS, the configuration is done in the [set protocols pcep] hierarchy for PCEs and for PCE groups:

set protocols pcep pce pce-id p2mp-lsp-report-capability
Note

After provisioning a P2MP LSP via Netconf, network utilization on the NorthStar Controller topology map might not be immediately refreshed. In this case, right-click on the topology map and select Reload Network.

To modify an existing LSP, select the tunnel on the Tunnels tab in the network information table and click Modify at the bottom of the table. The Modify LSP window is displayed, which is very similar to the Provision LSP window.

One difference between the two windows is the User Properties tab which is only available on the Modify LSP window. Use this window to define additional provisioning properties that you plan to reference in a customized provisioning script. See Templates for Netconf Provisioning for information about custom scripts.

If you modify an existing LSP via Netconf, NorthStar Controller only generates the configuration statements necessary to make the change, as opposed to re-generating all the statements in the full LSP configuration as is required for PCEP.