Provision LSP
To provision an LSP, navigate to Applications>Provision LSP. The Provision LSP window is displayed as shown in Figure 1.
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 |
|---|---|
Name | Required. A user-defined name for the tunnel. Only alphanumeric characters, hyphens, and underscores are allowed. Other special characters and spaces are not allowed. |
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). |
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 if the provisioning type is set to RSVP. Name for the path. |
Planned Bandwidth | Required. Bandwidth immediately followed by units (no space in between). Valid units are:
Examples: 50M, 1000b, 25g. If you enter a value without units, bps is applied. |
Setup | 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 | 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 | Optional. Free-form comment describing the LSP. |
The Path tab includes the fields shown in Figure 2 and described in Table 2.
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.
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. |
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. Example, 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 the route is to use protected IP links as much a possible. |
The Design tab includes the fields shown in Figure 4 and described in Table 4.
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, and OSPF. |
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. |
Scheduling 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.
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.
The time zone is the server time zone.