Add a Container LSP
To add a container LSP:
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. The container normalization task computes aggregated bandwidth for each container LSP and sends it to the Path Computation Server (PCS). Aggregate bandwidth thresholds are used to trigger merging of sub-LSPs during normalization. When the average bandwidth per sub-LSP (computed using aggregate bandwidth of container and current number of sub-LSPs) falls below the merging bandwidth (the lower threshold), sub-LSPs are reduced during normalization. Note:
Aggregation is based on the selected percentile [80th, 90th, 95th, 99th (X percentile)], or Average, or Max. For more information, see Table 2. |
Splitting Bandwidth |
Enter splitting bandwidth value. The container normalization task computes aggregated bandwidth for each container LSP and sends it to the Path Computation Server (PCS). Aggregate bandwidth thresholds are used to trigger splitting of sub-LSPs during normalization. When the average bandwidth per sub-LSP (computed using aggregate bandwidth of the container and current number of sub-LSPs) is above the splitting bandwidth (upper threshold), sub-LSPs are added during normalization. Note:
Aggregation is based on the selected percentile [80th, 90th, 95th, 99th (X percentile)], or Average, or Max. For more information, see Table 2. |
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:
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:
|
Bandwidth Sizing |
Toggle the button to enable bandwidth sizing. By default, this option is disabled. Once enabled, configure the following parameters:
|
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:
Note:
|
Aggregation Statistic |
Description |
---|---|
80th, 90th, 95th, 99th Percentile |
Aggregation is based on the selected percentile. The ‘X’ percentile is the value at which ‘X’ percent of all the samples taken in the previous sampling period lie at or below the calculated value. |
Average |
For each interval, the samples within that interval are averaged. If there are N samples for a particular interval, the result is the sum of all the sample values divided by N. |
Max |
For each interval, the maximum of the sample values within that interval is used. |