Add a Container LSP
To add a Container LSP Group:
- 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 Options (horizontal ellipsis) icon and select Container
The Container LSP tab appears.
- Click the add
The Add Container LSP page appears on the right.
- Configure the Container LSP as per Table 1.
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
Only PCEP is available.
Select RSVP or SR.
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.
Click the Node A list and select the name of the ingress (source) node from the list.
Click the Node Z list and select an egress (destination) node from the list.
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.
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 6.
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:
For example, 50M, 1000b, 25g.
If you enter a value without units, bps is applied.
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.
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.
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.
Select a routing method from the following:
Toggle the button to enable bandwidth sizing. By default, this option is disabled.
Once enabled, configure the following parameters:
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.
Enter a description for the Container LSP.
IP address of Node Z.
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: