Add a Container LSP

To add a container LSP:

Click Network > Topology.
The Topology page is displayed with the topology map at the center and the network information table at the bottom of the page.
Hover over the More Tabs list and select Container LSP.

The Container LSP tab appears.
Click the add (+) icon.
The Add Container LSP page appears on the right.
Configure the Container LSP as per Table 1.
Note:
Fields marked with asterisk (*) are mandatory.
Click Add.
A confirmation message appears stating that the Add Container LSP request is successfully sent. The new Container LSP is displayed under the Container LSP tab.

Table 1: Fields on the Add Container LSP Page
Field	Description
Properties
Provisioning Method	Only PCEP is available.
Provision Type	Select RSVP or SR.
Container Name	Enter name for the Container LSP. Only alphanumeric characters, hyphens, and underscores are allowed. Other special characters and spaces are not allowed. Note: The name you assign to the container LSP is used for automatic naming of the sub-LSPs that are created.
Node A	Click the Node A list and select the name of the ingress (source) node from the list.
Node Z	Click the Node Z list and select an egress (destination) node from the list.
Merging Bandwidth	Enter merging bandwidth value. Aggregate bandwidth thresholds are used to trigger merging of sub-LSPs during normalization. When the aggregate bandwidth usage falls below the merging bandwidth (the lower threshold), the number of sub-LSPs during normalization is reduced.
Splitting Bandwidth	Enter splitting bandwidth value. Aggregate bandwidth thresholds are used to trigger splitting of sub-LSPs during normalization. When the aggregate bandwidth usage rises above the splitting bandwidth (the upper threshold), sub-LSPs are added during normalization.
Minimum and Maximum LSP Count	Enter the minimum and maximum number of sub-LSPs that can be created in the container LSP. Range is 1 through 32767.
Minimum and Maximum LSP Bandwidth	Enter the minimum and maximum bandwidth that can be signaled for the sub-LSPs during normalization or initialization, 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) For example, 50M, 1000b, 25g. If you enter a value without units, bps is applied.
Planned Metric	Enter the metric value for static tunnel or use the up and down arrows to increment or decrement the value. For more information, see Basic LSP Configuration in MPLS Applications User Guide.
Setup	Enter the 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	Enter the 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.
Routing Method	Select a routing method from the following: Admin Weight Constant Default Note: Do not change the routing method for PCEP-provisioned sub-LSPs; they should always have a routing method of “default”. Delay Distance ISIS OSPF Route by Device
Bandwidth Sizing	Toggle the button to enable bandwidth sizing. By default, this option is disabled. Once enabled, configure the following parameters: Adjustment threshold (in percentage)—Controls the sensitivity of the automatic bandwidth adjustment. The new planned bandwidth is only considered if it differs from the existing bandwidth by the value of this setting percentage or more. Minimum and Maximum (planned) Bandwidth: If the new planned bandwidth is greater than the maximum setting, Paragon PathFinder signals the LSP with the maximum bandwidth. If the new planned bandwidth is less than the minimum setting, Paragon PathFinder signals the LSP with the minimum bandwidth. If the new planned bandwidth falls in between the maximum and minimum settings, Paragon Pathfinder signals the LSP with the new planned bandwidth. Minimum Variation Threshold—Specifies the sensitivity of the automatic bandwidth adjustment when the new planned bandwidth is compared to the current planned bandwidth. The new planned bandwidth is only considered if the difference is greater than or equal to the value of this setting. This can be used to prevent small fluctuations from triggering unnecessary bandwidth changes. If both the adjustment threshold and the minimum variation threshold are greater than zero, both settings are taken into consideration. In that case, the new planned bandwidth is considered if: • The percentage difference is greater than or equal to the adjustment threshold and • The actual difference is greater than or equal to the minimum variation.
Constraints Enables you to configure administrative groups to bypass label-switched paths (LSPs). For more information, see Assign Names to Admin Group Bits.
Admin Group Include All	Specifies the administrative groups whose links the bypass LSP must traverse. Select one or more bit-level link coloring options from the list.
Admin Group Include Any	Specifies the administrative groups whose links the bypass LSP can traverse. Select one or more bit-level link coloring options from the list.
Admin Group Exclude	Specifies the administrative groups to exclude for a bypass LSP. Select one or more bit-level link coloring options from the list.
Advanced
Description	Enter a description for the Container LSP.
IP Z	IP address of Node Z.
Custom Attributes	Simple name-value pairs which can be used to add any arbitrary customer-specific information. For example, to differentiate between properties for different vendor nodes. To add custom properties associated with the node: Click add (+) icon to add a new row. Click the newly added row to enter the Name and Value. Click √ icon to save your changes. Note: You can add multiple rows (properties). To delete an entry (row), select the row and click the delete (trash can) icon.

Add a Container LSP

Related Documentation