Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Add a Container LSP

A container LSP is a logical grouping of sub-LSPs that share common container-level properties, including ingress and egress nodes, provisioning type, routing method, priorities, and bandwidth thresholds. Routing Director provisions container LSPs through PCEP and supports both SR and RSVP sub‑LSPs.

Routing Director dynamically adds (split) or removes (merge) sub‑LSPs based on traffic conditions, helping optimize resource utilization and reducing the need to find a path capable of accommodating large bandwidth reservations.

To provision a container LSP:

  1. Navigate to Observability > 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.
  2. Navigate to the Container LSP tab.
  3. Click the + icon.
    The Add Container LSP Page appears.
  4. Complete the configuration on each tab according to the guidelines in Table 1.
    Note:

    Fields marked with an asterisk (*) are mandatory.
  5. Click Add to add the container LSP.

    A confirmation message appears on the top of the page, indicating that a container LSP request was successfully created.

    Note: Routing Director performs the splitting or merging action on the container LSP only when you enable the Container LSP Normalization toggle button. Do not forget to enable it by navigating to Organization Settings page (Settings Menu > System Settings) on the Network Optimization Settings section and update the following fields:

    • Adjustment Period

    • Statistical Function

    For more information, see Manage Organization Settings.
    Table 1: Fields on the Add Container LSP Page

    Field

    Description

    PROPERTIES

    Provisioning Method

    From the list, select PCEP (Path Computation Element Protocol) method to be used to provision the container LSP.

    Provision Type

    From the list, select the type of tunnel that you want to provision:

    • RSVP
    • SR (segment routing)

    Container Name

    Specify the name of the container LSP. Use alphanumeric characters, underscore, hyphen, period, or colon.

    The name you assign to the container LSP is used as the base for automatic naming of the sub-LSPs that are created.

    Ensure that the container LSP name is unique to its source node. Note that the same container LSP name can be reused for different source nodes.

    For example, ContainerLSP-1.

    Device A

    From the list, select the device that you want to use as the ingress node.

    Device Z

    From the list, select the device that you want to use as the egress node.

    Merging Bandwidth

    Enter the bandwidth threshold for removing sub-LSPs during container normalization, followed by units (no space in between). The valid units are B or b (bps), M or m (Mbps). K or k (Kbps), or G or g (Gbps). If you specify a value without units, bps is automatically applied.

    If the traffic per sub-LSP is below this value, Routing Director removes some sub-LSPs. The traffic per sub-LSP is obtained by dividing the aggregate container traffic by number of sub-LSPs.

    Ensure that the Merging Bandwidth value is less than the Splitting Bandwidth value. The default value is 1 (in bps).

    Splitting Bandwidth

    Enter the bandwidth threshold for creating additional sub-LSPs during container normalization, followed by units (no space in between). The valid units are B or b (bps), M or m (Mbps). K or k (Kbps), or G or g (Gbps). If you specify a value without units, bps is automatically applied.

    When the traffic per sub-LSP exceeds this value, Routing Director adds new sub-LSPs. The traffic per sub-LSP is obtained by dividing the aggregate container traffic by number of sub-LSPs.

    Ensure that the Splitting Bandwidth value is greater than the Merging Bandwidth value. The default value is 2 (in bps).

    Minimum LSP Count

    Specify the minimum number of sub-LSPs that should always exist. The default value is 1.
    Maximum LSP Count

    Specify the maximum number of sub-LSPs that can exist. The default value is 64.
    Minimum LSP Bandwidth

    Specify the minimum bandwidth that each sub-LSP of this container can be assigned during container normalization or when the container was initially created. The valid units are B or b (bps), M or m (Mbps). K or k (Kbps), or G or g (Gbps). If you specify a value without units, bps is automatically applied.

    This value should be less than or equal to the Splitting Bandwidth value. The default value is 0.
    Maximum LSP Bandwidth

    Specify the maximum bandwidth that each sub-LSP of this container can be assigned during container normalization. The valid units are B or b (bps), M or m (Mbps). K or k (Kbps), or G or g (Gbps). If you specify a value without units, bps is automatically applied.

    This value should be greater than or equal to the Merging Bandwidth value. The default value is 1 (in bps).

    Planned Metric

    Specify the static tunnel metric.

    The PCE assigns this metric to each sub-LSP, and the PCC uses it to decide whether to use or avoid a particular path while routing packets to the egress node address of the sub‑LSP.

    Setup

    Specify the 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 tunnel definition in Junos OS.

    Based on the setup priority, the PCE determines whether a new tunnel can be established by preempting an existing tunnel. The PCE can preempt the existing tunnel if:

    • Setup priority of the new tunnel is higher than the hold priority of the existing tunnel.

    • Preemption releases enough bandwidth for the new tunnel.

    Routing Method

    From the list, select a routing method to specify whether the PCE should compute and provision the path for the tunnel:

    The available options are:

    • default - The Routing Director (RD) computes the best path, under the current network state, based on Traffic Engineering (TE) metrics of the links between the source and destination, while adhering to bandwidth and administrative constraints.

    • delay - The RD computes the best path based on the calculated end‑to‑end delay between the source and destination, while adhering to bandwidth and administrative constraints

    • ISIS and OSPF - The RD computes the best path based on link metrics configured or assigned by the active IGP, while adhering to bandwidth and administrative constraints.

    Hold

    Specify the 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 tunnel definition in Junos OS.

    Based on the hold priority, the PCE determines whether the tunnel can be preempted or not. If the hold priority for a tunnel is higher, it is unlikely for the tunnel to be preempted.
    FlexAlgo ID
    Note:

    This field is available only for the SR provision type.

    Select the flex algo ID that you want to associate with the LSP. This field lists all the flex algo IDs that are associated with both ingress and egress devices in your network.

    When the LSP is provisioned, the LSP adheres to the pre-defined FAD constraints such as metric type, administrative group restrictions, optimizing traffic paths, and so on.

    You can select the flex algo ID only for SR (segment routing).
    Bandwidth Sizing

    Click the toggle button to enable or disable (default) bandwidth sizing for the tunnel.

    If you enable bandwidth sizing, the tunnel is included in the periodic re-computation of planned bandwidth based on aggregated tunnel traffic statistics.
    Adjustment Threshold (%)

    Specify the sensitivity (in percentage) of the automatic bandwidth adjustment. The new planned bandwidth is considered only if the percentage difference is greater than or equal to the threshold value. It is the minimum percentage change in the measured traffic that is required to trigger an automatic bandwidth adjustment.

    The default value is 10%.
    Minimum Bandwidth *

    Specify the minimum planned bandwidth (along with valid units, with no space between the bandwidth and units) for the tunnel.

    If the aggregate LSP traffic is lesser than both the current bandwidth and the minimum bandwidth and if the difference exceeds the adjustment threshold (in %) and minimum variation threshold values, then the new planned bandwidth of the LSP will be set to the minimum bandwidth value.

    If you do not specify any value then the by default the minimum bandwidth value is considered as zero.

    The valid units are B or b, M or m, K or k, or G or g. If you specify a value without units, bps is automatically applied.

    Examples: 50M, 1000b, 25g.
    Maximum Bandwidth

    Specify the maximum planned bandwidth (along with valid units, with no space between the bandwidth and units) for the tunnel.

    If the aggregate LSP traffic is greater than the maximum bandwidth value and the current bandwidth, and if the difference between LSP traffic and current bandwidth exceeds the adjustment threshold (in %) and minimum variation threshold values, then the new planned bandwidth of the LSP will be set to the maximum bandwidth value.

    The valid units are B or b, M or m, K or k, or G or g. If you specify a value without units, bps is automatically applied.

    Examples: 50M, 1000b, 25g.
    Minimum Variation Threshold

    Specify the sensitivity of the automatic bandwidth adjustment when the new planned bandwidth is compared with the current planned bandwidth.

    The default value is 0.

    The new planned bandwidth is only considered if the difference is greater than or equal to the value you have specified here. Because it is not a percentage, this is 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. 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

    Admin Group Include All

    From the list, select one or more admin group bits for the tunnel to traverse links that include all of the admin groups specified in this field. The maximum number of selections allowed is 32.

    Admin Group Include Any

    From the list, select one or more admin group bits. The tunnel traverses links that include at least one of the admin groups specified in this field. The maximum number of selections allowed is 32.

    Admin Group Exclude

    From the list, select one or more admin group bits. The tunnel traverses links that do not include any of the admin groups specified in this field. The maximum number of selections allowed is 32.

    ADVANCED

    Description

    Specify a comment or description for the container for your reference. All sub-LSPs of this container will show the same description.
    IP Z Select the IP address of the egress device (Device Z).

    For example, 10.1.1.1.

Related Documentation