Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Creating an RSVP LSP Service Order

    The service designer is responsible for creating and managing service definitions and the service provisioner uses these definitions as the basis for creating a service order. You can create a service definition that specifies attributes that are common to a group of service orders with similar service requirements, and a service order, which is an implementation object or a derivative of a service definition. For RSVP label-switched path (LSP) services, a service order can be directly created but a customized service definition cannot be created independently.

    You can create MPLS RSVP LSP (also called RSVP LSP) service orders that you can use as a starting point for provisioning LSP services. For RSVP LSP service orders, unlike the framework that is available for network services, such as point-to-point, VPLS, and Layer 3 VPN protocols, in which a service definition is created independently as a separate item and a service order can be created, based on a service definition, a service order is created, independent of a service definition. You can, however, select a customized predefined service definition during the creation of an RSVP LSP service order. When you select such a predefined service definition, the parameters that are contained in it are populated in the corresponding fields of the service order creation wizard.

    A wizard is available to create and modify a service order. The settings that you configure in the service order are organized in separate pages of the wizard, which you can launch by clicking the appropriate buttons at the top of the Create or Edit a Service Order page. Alternatively, you can proceed to the corresponding setting-related pages by clicking the Back and Next buttons in the wizard at any point during the creation of the service order.

    To create an RSVP LSP service order, you must first discover devices that have been configured for the RSVP LSP.

    1. Configuring LSP Order General Settings

    2. Configuring LSP Service Order Advanced Settings

    3. Creating a Name Pattern for LSPs in the Service Order

    4. Configuring Node Settings for LSPs in the Service Order

    5. Configuring MPLS Path Settings

    6. Configuring LSP Primary Path Settings

    7. Configuring LSP Secondary Path Settings

    8. Reviewing the Configured Settings

    Configuring LSP Order General Settings

    As the service activator, you can configure an RSVP LSP based on a predefined RSVP LSP service definition. Alternatively, you can create an RSVP LSP service order without basing it on a service definition, and use the service order as a starting point for provisioning LSP services. The service activator can configure LSP settings that the service designer specified to be editable.

    To create an RSVP LSP service order, configure the general settings.

    1. Select Service View from the View selector.

      The workspaces that are applicable to routing and tunneling services are displayed.

    2. From the Junos Space user interface, click the Deploy icon on the Connectivity Services Director banner.

      The functionalities that you can configure in this mode are displayed in the Tasks pane of the GUI window.

    3. From the Service View pane, which is the left pane in the window, click the plus sign (+) next to Network Services to expand the tree and display the different service types that you can configure.

      The different network service types that you can configure, such as point-to-point, VPLS, and L3VPN, are displayed.

    4. From the Service View pane, click the plus sign (+) sign next to Tunnels, and select RSVP LSPs.

      The RSVP LSPs node is expanded and displayed in the View pane.

    5. From the task pane, select Service Provisioning > Manage LSP.

      The Manage Network Services page is displayed in on the top right main display area, and the Manage Service Deployment window is displayed on the bottom of the main display area.

    6. Click the down arrow on the New menu and select RSVP LSPs from the drop-down menu.

      The wizard to create an RSVP LSP is displayed.

      On the General Settings page of the wizard, the Service Details pane is displayed on the left. which contains the Basic and Advanced tabs.

    7. Click the Basic tab.

      The general settings are displayed.

    8. Configure the settings on the Basic tab as indicated in the following table.

      Item

      Action

      Service Name

      Type a name that identifies the LSP service order.

      A service order name cannot exceed 50 characters and can contain only letters, numbers, and some special characters. The special characters allowed are hyphen (-), underscore (_), and period (.)

      LSP Configuration

      Perform either of the following actions to specify the method to be used for creating an LSP order:

      • Select the Create Custom option button to create a service order as an entirely new one.

      • Select the Import Existing option button to select an available LSP service definition that you created and published, and select a predefined service definition from the drop-down list. The LSP service definition on the LSP Definition drop-down menu is available for selection only if you published the service definition.

        The following are the predefined RSVP LSP service definitions:

        • RSVP LSP with BFD - Path Protection—Creates an RSVP LSP service order that protects the LSP primary path by establishing a secondary path with BFD as the signaling protocol

        • RSVP LSP with BFD - P2MP Topology—Creates an RSVP LSP service order with BFD as the signaling protocol and a point-to-multipoint topology

        • RSVP LSP with Path Protection—Creates an RSVP LSP service order that protects the primary path by establishing a secondary path

        • RSVP LSP with Node Link Protection—Creates an RSVP LSP service order that bypasses a node or link for redundancy.

        • FullMesh LSP with Node Link Protection—Creates an RSVP LSP service order in a full-mesh topology that bypasses a node or link for redundancy.

        The parameters on the different pages of the wizard are filled out with the values of parameters retrieved from the service definition you selected. You can modify them as needed.

      Topology

      Select the LSP transport topology from the list:

      • P2P—Provides a point-to-point connectivity between the selected endpoints

      • P2MP—Provides a point-to-multipoint connectivity between the selected endpoints

      • Full Mesh—Provides any-to-any unidirectional MPLS connectivity among all the selected provider edge router

      Path Selection Type

      From this list, select either CSPF or Explicit Path. In Constrained Shortest Path First (CSPF) LSPS, the intermediate hops of the LSP are automatically computed by the software. If you select CSPF, Junos OS calculates the best path for you. In explicit-path LSPs, all intermediate hops of the LSP are manually configured. The intermediate hops can be strict, loose, or any combination of the two.

      LSP Protection Type

      Select the type of protection you want to configure.

      Path Protection OnlyProtects the LSP primary path by establishing a secondary path.

      Fast reroute can be applied to the LSP if you are selecting Path Protection Only. On the Advanced page, specify the protection type as Path Protection Only and select the Enable Fast Reroute check box in the Common Settings section on the Advanced tab.

      Local Protection OnlyProvides local repair procedures that ensure faster restoration by establishing local protection as close to a failure as possible. Configuring only local protection for the ingress router of the primary LSP caues RSVP-traffic engineering to indicate to LSP setup that the primary LSP needs local protection.When there is only one path for the LSP, you can specify either link protection or node-link protection.
      Path and Local ProtectionProvides redundancy using a combination of path protection and local protection options. The primary path is protected and local repair procedures for faster redundancy is achieved using this methodology.

      Local Protection Type

      Specify the type of protection:

      Link ProtectionProvides backup support for a single link.
      Node-Link ProtectionCan bypass a node or a link to provide redundancy.

      Note: This drop-down list is unavailable if the LSP Protection Type is Path Protection Only.

    9. Click the Advanced tab.

      The advanced settings that you can configure for the LSP service order are displayed.

    Configuring LSP Service Order Advanced Settings

    On the left of the General Settings page of the wizard, the Service Details pane contains the Basic and Advanced tabs.

    To configure the settings that are globally applicable throughout the LSP in the LSP service order:

    1. Click the Advanced tab on the General Settings page of the wizard to create an RSVP LSP.

      The global or system-wide settings are displayed.

    2. You can specify the following types of settings from the Advanced tab of the LSP service order creation wizard:
      1. Common Settings—Configure the LSP retry limit, retry timer (seconds), LDP tunneling settings, auto-bandwidth settings, protections settings, and BFD settings. See Configuring Common LSP Settings for details

      2. Path Settings—Configure the primary and secondary paths on one point-to-point or several point-to-multiple-point branches. Specify the primary path to use for an LSP. You can configure only one primary path. You can optionally specify the preference, CoS, and bandwidth values for the primary path, which override any equivalent values that you configure for the LSP. See Configuring MPLS Path Settings for details.

      3. BFD Settings—Configure a Bidirectional Forwarding Detection (BFD) protocol on MPLS IPv4 LSPs. BFD is used as a periodic Operation, Administration, and Maintenance (OAM) feature for LSPs to detect LSP data plane faults. You can configure a BFD protocol for LSPs that use RSVP as the signaling protocol. See Configuring BFD Settings for LSPs in the Service Order for details.

    The following sections describe the advanced settings you can configure for the LSP service order:

    Configuring Common LSP Settings

    You can use the Common LSP Settings page to view or configure the LSP retry limit, retry timer (seconds), LDP tunneling settings, auto-bandwidth settings, protections settings, and BFD settings.

    Each LSP has a bandwidth value. This value is included in the sender’s Tspec field in RSVP path setup messages. You can specify a bandwidth value in bits per second. If you configure more bandwidth for an LSP, it should be able to carry a greater volume of traffic. The default bandwidth is 0 bits per second.

    The ingress router might make many attempts to connect and reconnect to the egress router using the primary path. You can control how often the ingress router tries to establish a connection using the primary path and how long it waits between retry attempts. The retry timer configures how long the ingress router waits before trying to connect again to the egress router using the primary path. The default retry time is 30 seconds. The time can be from 1 through 600 seconds. To modify this value, include the retry timer parameter in the service order.

    Automatic bandwidth allocation allows an MPLS tunnel to automatically adjust its bandwidth allocation based on the volume of traffic flowing through the tunnel. You can configure an LSP with minimal bandwidth; this feature can dynamically adjust the LSP’s bandwidth allocation based on current traffic patterns. The bandwidth adjustments do not interrupt traffic flow through the tunnel. You set a sampling interval on an LSP configured with automatic bandwidth allocation. The average bandwidth is monitored during this interval. At the end of the interval, an attempt is made to signal a new path for the LSP with the bandwidth allocation set to the maximum average value for the preceding sampling interval. If the new path is successfully established and the original path is removed, the LSP is switched over to the new path. If a new path is not created, the LSP continues to use its current path until the end of the next sampling interval, when another attempt is made to establish a new path. Note that you can set minimum and maximum bandwidth values for the LSP. During the automatic bandwidth allocation interval, the router might receive a steady increase in traffic (increasing bandwidth utilization) on an LSP, potentially causing congestion or packet loss. To prevent this, you can define a second trigger to prematurely expire the automatic bandwidth adjustment timer before the end of the current adjustment interval.

    To configure common settings that are applicable to all LSPs in the service order:

    1. On the Advanced pane of the General Settings page, click the plus sign beside the Common Settings section.

      The parameters that are applicable to all the LSPs are available for configuration.

    2. Fill in the parameters as indicated in the table.

      Item

      Action

      Retry limit

      Specify the number of times an ingress router can attempt to establish or reestablish a connection to the egress router by using the primary path. This counter is reset each time a primary path is created successfully. When the limit is exceeded, no more connection attempts are made. Intervention is then required to restart the connection.

      Range: 0 through 10,000

      Default: No limit is set.

      Retry timer

      Specify how long the ingress router waits before trying to connect again to the egress router by using the primary path.

      Range: 1 through 600 seconds

      Default: 30 seconds

      Bandwidth (Kbps)

      Specify the bandwidth in Kbps.

      A nonzero bandwidth requires that transit and egress routers reserve capacity along the outbound links for the path. The RSVP scheme is used to reserve this capacity. Any failure in bandwidth reservation (such as failures at RSVP policy control or admission control) might cause the LSP setup to fail. If there is insufficient bandwidth on the interfaces for the transit or egress routers, the LSP is not established.

      Range: Any positive integer

      Default: 0 (No bandwidth is reserved.)

      Enable LDP tunneling

      Select this check box to enable LSP for LDP tunneling. That is, if you are using RSVP for traffic engineering, you can run LDP simultaneously to eliminate the distribution of external routes in the core network. The LSPs established by LDP are tunneled through the LSPs established by RSVP. LDP effectively treats the traffic-engineered LSPs as single hops. When you configure the router to run LDP across RSVP-established LSPs, LDP automatically establishes sessions with the router at the other end of the LSP. LDP control packets are routed hop by hop, rather than carried through the LSP. This routing allows you to use simplex (one-way) traffic-engineered LSPs. Traffic in the opposite direction flows through LDP-established LSPs that follow unicast routing rather than through traffic-engineered tunnels.

      Enable fast reroute

      Select this check box to enable fast reroute. If you enable the fast reroute, the ingress router signals all the downstream routers that fast reroute is enabled on the LSP, and each downstream router does its best to set up detours for the LSP. If a downstream router does not support fast reroute, it ignores the request to set up detours and continues to support the LSP. A router that does not support fast reroute will cause some of the detours to fail, but otherwise has no impact on the LSP.

      Auto Bandwidth

      Select this check box to allow an MPLS tunnel to automatically adjust its bandwidth allocation based on the volume of traffic flowing through the tunnel.

      1. In the Adjust Interval field, specify the bandwidth reallocation interval.

        Range: 300 through 4,294,967,295 seconds.

        Default: 86,400 seconds.

      2. In the Maximum Bandwidth (Kbps) field, specify the maximum bandwidth in Kbps or an LSP with automatic bandwidth allocation enabled.

        You can maintain the LSP’s bandwidth between minimum and maximum bounds by specifying values. The default value is 10000 Kbps. The range is 1 through 2147483 Kbps.

      3. In the Minimum Bandwidth (Kbps) field, specify the minimum bandwidth in Kbps or an LSP with automatic bandwidth allocation enabled. The default value is 1000 Kbps. The range is 1 through 2147483 Kbps. You must enter the minimum bandwidth to be lower than the maximum bandwidth.
    3. Click the plus sign beside the Path Settings section to configure the path specifications for the LSP.

      The Path Settings section is expanded and displayed.

    Configuring LSP Path Settings in the Service Order

    When IP traffic enters an LSP tunnel, the ingress router marks all packets with a CoS value, which is used to place the traffic into a transmission priority queue. On the router, for SDH/SONET and T3 interfaces, each interface has four transmit queues. The CoS value is encoded as part of the MPLS header and remains in the packets until the MPLS header is removed when the packets exit from the egress router. The routers within the LSP use the CoS value set at the ingress router. The CoS value is encoded by means of the CoS bits (also known as the EXP or experimental bits). MPLS class of service works in conjunction with the router’s general CoS functionality. If you do not configure any CoS features, the default general CoS settings are used. For MPLS class of service, you might want to prioritize how the transmit queues are serviced by configuring weighted round-robin, and to configure congestion avoidance using random early detection (RED).

    When there is insufficient bandwidth to establish a more important LSP, you might want to tear down a less important existing LSP to free the bandwidth. You do this by preempting the existing LSP. Whether an LSP can be preempted is determined by two properties associated with the LSP:

    • Setup priority—Determines whether a new LSP that preempts an existing LSP can be established. For preemption to occur, the setup priority of the new LSP must be higher than that of the existing LSP. Also, the act of preempting the existing LSP must produce sufficient bandwidth to support the new LSP. That is, preemption occurs only if the new LSP can be set up successfully.

    • Reservation priority—Determines the degree to which an LSP holds on to its session reservation after the LSP has been set up successfully. When the reservation priority is high, the existing LSP is less likely to give up its reservation, and hence it is unlikely that the LSP can be preempted.

    You cannot configure an LSP with a high setup priority and a low reservation priority, because permanent preemption loops might result if two LSPs are allowed to preempt each other. You must configure the reservation priority to be higher than or equal to the setup priority. The setup priority also defines the relative importance of LSPs on the same ingress router. When the software starts, when a new LSP is established, or during fault recovery, the setup priority determines the order in which LSPs are serviced. Higher-priority LSPs tend to be established first and hence enjoy more optimal path selection.

    To configure LSP path settings in the service order:

    1. On the Advanced pane of the General Settings page, click the plus sign beside the Path Settings section.

      The LSP path parameters that are applicable to all the LSPs are available for configuration.

    2. Fill in the parameters as indicated in the following table.

      Item

      Action

      Hop limit

      Specify the hop limit of the LSP.

      Range: 2 through 255. A path with two hops consists of the ingress and egress routers only.

      Default: Each LSP can traverse a maximum of 255 hops, including the ingress and egress routers.

      Class of service

      Specify a decimal number. This number corresponds to a 3-bit binary number. The high-order 2 bits of the CoS value select which transmit queue to use on the outbound interface card. The low-order bit of the CoS value is treated as the packet loss priority (PLP) bit and is used to select the random early detection (RED) drop profile to use on the output queue. If the low-order bit is 0, the non-PLP drop profile is used, and if the low-order bit is 1, the PLP drop profile is used. Typically, RED aggressively drops packets that have the PLP bit set. For more information about RED and drop profiles, see the Junos OS Class of Service Configuration Guide.

      Range: A decimal number from 0 through 7

      This field is not applicable for local-protection type of LSPs.

      Bandwidth (Kbps)

      Specify a bandwidth in Kbps for an LSP. Each LSP has a bandwidth value. This value is included in the sender’s Tspec field in RSVP path setup messages. The ingress router uses the traffic specification (Tspec) object to specify the parameters for the traffic it is going to send. You can specify a bandwidth value in bits per second. If you configure more bandwidth for an LSP, it should be able to carry a greater volume of traffic. The default bandwidth is 0 bits per second.

      Standby (enable switchover)

      Select this check box to have the path remain up at all times to provide immediate switchover if connectivity problems occur.

      This field is displayed only for secondary paths.

      Adaptive

      Select this check box if you want to configure an LSP to be adaptive when it is attempting to reroute itself. When it is adaptive, the LSP holds onto existing resources until the new path is successfully established and traffic has been switched over to the new LSP. To retain its resources, an adaptive LSP does the following:

      • Maintains existing paths and allocated bandwidths—This ensures that the existing path is not torn down prematurely and allows the current traffic to continue flowing while the new path is being set up.

      • Avoids double-counting for links that share the new and old paths—Double-counting occurs when an intermediate router does not recognize that the new and old paths belong to the same LSP and counts them as two separate LSPs, requiring separate bandwidth allocations. If some links are close to saturation, double-counting might cause the setup of the new path to fail.

        By default, adaptive behavior is disabled.

      You can include the adaptive statement in two different hierarchy levels. If you specify the adaptive statement at the LSP hierarchy levels, the adaptive behavior is enabled on all primary and secondary paths of the LSP. This means both the primary and secondary paths share the same bandwidth on common links.

      This check box is not available for P2MP topology and also when the path selection type is explicit path.

      Priority

      Configure the LSP’s preemption properties by selecting a value from the Setup Priority and Hold riority lists.

      Setup Priority

      Specify a priority value, which determines whether a new LSP that preempts an existing LSP can be established. For preemption to occur, the setup priority of the new LSP must be higher than that of the existing LSP. Also, the act of preempting the existing LSP must produce sufficient bandwidth to support the new LSP. That is, preemption occurs only if the new LSP can be set up successfully. The setup priority also defines the relative importance of LSPs on the same ingress router. When the software starts, when a new LSP is established, or during fault recovery, the setup priority determines the order in which LSPs are serviced. Higher-priority LSPs tend to be established first and hence enjoy more optimal path selection.

      This field cannot be configured for local-protection type of LSPs.

      Range: Both setup-priority and reservation-priority can be a value from 0 through 7, where 0 is the highest priority and 7 is the lowest priority.

      Default: An LSP has a setup priority of 7 (that is, it cannot preempt any other LSPs) and a reservation priority of 0 (that is, other LSPs cannot preempt it). These defaults prevent preemption. When you are configuring these values, make sure that the setup priority value is lower than or equal to the hold priority value.

      Hold Priority

      Specify a hold priority value. The hold priority determines the degree to which an LSP holds onto its session reservation of the LSP that has been set up successfully. When the hold priority is high, the existing LSP is less likely to give up its reservation and, therefore, it is unlikely that the LSP can be preempted. You must configure the hold priority to be greater than or equal to the setup priority.

      This field cannot be configured for local-protection type of LSPs.

      Range: 0 through 7, where 0 is the highest priority and 7 is the lowest priority.

      Note: If traffic engineering admission control determines that there are insufficient resources to accept a request to set up a new LSP, the setup priority is evaluated against the hold priority of existing LSPs. An LSP with a hold priority lower than the setup priority of the new LSP can be preempted. The existing LSP is terminated to make room (that is, resources are freed) for the new LSP.

    3. Click the plus sign beside the BFD Settings section to configure the BFD parameters for the LSP.

      The BFD Settings section is expanded and displayed.

    Configuring BFD Settings for LSPs in the Service Order

    BFD for RSVP supports unicast IPv4 LSPs. When BFD is configured for an RSVP LSP on the ingress router, it is enabled on the primary path and on all standby secondary paths for that LSP. The source IP address for outgoing BFD packets from the egress side of an MPLS BFD session is based on the outgoing interface IP address. You can enable BFD for all LSPs on a router or for specific LSPs. If you configure BFD for a specific LSP, whatever values configured globally for BFD are overridden. The BFD sessions originate only at the ingress router and terminate at the egress router.

    The BFD failure detection timers are adaptive and can be adjusted to be more or less aggressive. For example, the timers can adapt to a higher value if the adjacency fails, or a neighbor can negotiate a higher value for a timer than the configured value. The timers adapt to a higher value when a BFD session flap occurs more than three times in a span of 15 seconds. A back-off algorithm increases the receive (Rx) interval by two if the local BFD instance is the reason for the session flap. The transmission (Tx) interval is increased by two if the remote BFD instance is the reason for the session flap.

    To configure BFD settings for RSVP LSPs in the service order:

    1. On the Advanced pane of the General Settings page, click the plus sign beside the BFD Settings section.

      The parameters that are applicable to all of the LSPs are available for configuration.

    2. Fill in the parameters as indicated in the following table:

      Field

      Action

      BFD Detection

      Select the BFD setting type:

      • This LSP—Configure BFD settings for all of the specific LSP.

      • Primary Path—Configure BFD settings for the primary path of the specific LSP.

      • Secondary Path—Configure BFD settings for the secondary path of the specific LSP.

      • None–Do not configure BFD settings. By default, BFD is not configured.

      Note: The primary path and the secondary path are listed on BFD Detection menu only if you have configured the primary and secondary paths.

      You can modify the BFD Detection settings in a service.

      Minimum Interval

      Specify the minimum transmit and receive interval. This value represents the minimum interval at which the local routing device transmits hello packets as well as the minimum interval that the routing device expects to receive a reply from a neighbor with which it has established a BFD session.

      Range: 1 through 255000 milliseconds

      Default: 50

      Minimum Receive Interval

      Specify the minimum receive interval. This value represents the minimum interval at which the peer must receive a reply from a peer with which it has established a BFD session.

      Range: 1 through 255000 milliseconds

      Default: 50

      Multiplier

      Specify the detection time multiplier. This value represents the number of hello packets not received by the neighbor before BFD declares that the neighbor is down.

      Range: 1 through 255

      Default: 3

      No adaptation

      Select this check box to disable adaptation.

      You can configure an LSP to be adaptive when it is attempting to reroute itself. When it is adaptive, the LSP holds onto existing resources until the new path is successfully established and traffic has been switched over to the new LSP. To retain its resources, an adaptive LSP does the following:

      • Maintains existing paths and allocated bandwidths—This ensures that the existing path is not torn down prematurely and allows the current traffic to continue flowing while the new path is being set up.

      • Avoids double-counting for links that share the new and old paths—Double-counting occurs when an intermediate router does not recognize that the new and old paths belong to the same LSP and counts them as two separate LSPs, requiring separate bandwidth allocations. If some links are close to saturation, double-counting might cause the setup of the new path to fail.

      By default, adaptive behavior is disabled.

      Transmit Minimum Interval

      Specify the minimum transmit interval at which the local routing device transmits hello packets to a neighbor with which it has established a BFD session. The negotiated transmit interval for a peer is the interval between the sending of BFD packets to peers. The receive interval for a peer is the minimum time that it requires between packets sent from its peer; the receive interval is not negotiated between peers. To determine the transmit interval, each peer compares its configured minimum transmit interval with its peer's minimum receive interval. The larger of the two numbers is accepted as the transmit interval for that peer.

      Range: 1 through 255000 milliseconds

      Default: 50 milliseconds

      Transmit Threshold

      Specify the high transmit interval triggering a trap.

      The threshold is used for detecting the adaptation of the transmit interval. When the BFD session transmit interval adapts to a value greater than the threshold, a single trap and a single system message are sent.

      Range: 51 through 4,294,967,295

      Default: None

      Detection Threshold

      Specify the maximum time at which to trigger a trap.

      Specify the threshold for the adaptation of the BFD session detection time. When the detection time adapts to a value equal to or greater than the threshold, a single trap and a single system log message are sent.

      Range: 0 through 4,294,967,295

      Default: None

      Failure Action

      Select an action to take when a BFD session for an RSVP LSP goes down:

      • Teardown—Causes the LSP path to be taken down and resignaled immediately.

      • Make Before Break—Attempts to signal a new LSP path before tearing down the old LSP path.

      When the BFD session for an RSVP LSP goes down, the LSP is torn down and resignaled. Traffic can be switched to a standby LSP, or you can simply tear down the LSP path. Any actions performed are logged. When a BFD session for an RSVP LSP path goes down, you can configure the Junos OS to resignal the LSP path or to simply disable the LSP path. A standby LSP path could be configured to handle traffic while the primary LSP path is unavailable. The router can automatically recover from LSP failures that can be detected by BFD. By default, if a BFD session fails, the event is simply logged.

      Teardown Timeout

      Specify a time to wait before the LSP path is taken down and resignaled. If you specify a value of 0 for the teardown-timeout interval, the LSP is taken down and resignaled immediately.

      Range: 0 through 30 seconds

      Default: None

    3. Specify the LSP pattern settings. See Creating a Name Pattern for LSPs in the Service Order for details.

    Creating a Name Pattern for LSPs in the Service Order

    Instead of using an existing predefined pattern of label-switched path (LSP) names, you can also create an LSP name of your preference or convention. The customized LSP name includes a set of common variables and supported special characters. The Transport Activate software appends a unique number to these customized name to avoid conflicts.

    To specify a name pattern for LSPs in the service order:

    1. On the General Settings page, with either the Advanced or Basic tab selected, click the plus sign (+) next to LSP Pattern Details at the bottom of the page to expand the section.
    2. Click Select adjacent to the Name field to select a pattern from the list of available patterns.

      The Select LSP Name pattern dialog box appears. The dialog box displays a table, which includes the following patterns:

      • Default LSP pattern—Uses the default LSP name pattern for a point-to-point and point-to-multipoint topology

      • Full-mesh default pattern—Uses the default LSP name pattern for a full-mesh topology

      • User-defined RSVP patterns—Creates an LSP name of your preference or convention

    3. Select the check box next to the pattern to be used in the LSP service order.
    4. Click OK to save the selection.

      You are returned to the LSP Pattern Details section of the General Settings page of the wizard.

    5. In the Pattern field, view the name of the selected pattern. For example, the pattern of Default LSP Pattern is Service Order Name_to_Egress Loopback Address.

      Alternatively, to create a new name pattern, click the Create button adjacent to the Name field.

      The Create LSP Name Pattern dialog box appears.

    6. From the Name list, select one of the following:
      • RSVP—Name pattern for RSVP LSPs.

      • General—Name pattern for general LSPs.

      • Static—Name pattern for static LSPs.

      The specified name pattern for the type of LSP you want to configure is selected.

    7. Specify the name of the pattern in the Name box.
    8. In the LSP Pattern Details section, select the Select Variable option button to select an existing variable from the Variable drop-down list. The predefined variables are listed in the Variable drop-down list.

      Alternatively, select the Add Text option button to add a new variable.

      The Variable field is available for specifying the variable.

    9. Click Add to add the variable to the pattern.

      The variable you add is displayed in pattern name of the Pattern field.

      Note: You can select any of the predefined variables from the Variable drop-down list. The variables in the Variable drop-down list are based on the Pattern Type you select.

      Alternatively, click Clear to remove the variable from the Variables drop-down list.

      The variable is deleted from the pattern name in the Pattern field.

    10. Select the Append unique number check box to append a unique number to these customized names you create to avoid conflicts.
    11. Click Create to add the name pattern to the LSP service.

      You are returned to the General Settings page of the wizard and the pattern name appears in the Patterns field.

      The pattern is also added to the Select LSP Name Patterns inventory page, which you can open by clicking Select beside the Name field in the LSP Pattern Details section. You can select this pattern name in the service order from the Select LSP Name Patterns inventory page.

      Note: You can view the details of a pattern on the Select LSP Name Patterns inventory page. You cannot modify an existing pattern.

    12. On the General Settings page of the wizard, click Next to proceed to the next step of the wizard, which is to define the node or endpoint settings.

      The Node Settings page of the wizard is displayed.

    Configuring Node Settings for LSPs in the Service Order

    On the Node Settings page, you can configure the endpoints or nodes for the LSP service order.

    Only fields that correspond to the type of topology that you selected on the General Settings page of the wizard are displayed on the Node Settings page.

    1. Fill in the parameters as described in the following table:

      Item

      Action

      Ingress Router

      1. Click Select beside the field to open the Select device dialog box.

      2. Select the check box next to an available router that must function as the ingress router.

        The local router is always considered to be the ingress router, which is the beginning of the LSP. The software automatically determines the correct outgoing interface and IP address to use to reach the next router in an LSP. By default, the router ID is chosen as the address of the ingress router.

        MPLS-signaled label-switched paths (LSPs) run from a specific ingress router to a specific egress router. For basic MPLS-signaled LSP function, you must configure the ingress router, but do not have to configure any other routers.

        This field is unavailable if the selected LSP service definition is a full-mesh RSVP definition.

      Egress Router

      1. Click Select beside the field to open the Select Device dialog box. The Select button is available only for P2P topology.

      2. Select an available router that must function as the egress router in the LSP connection established using the primary path from the ingress router. For a point-to-point topology, select one egress router.

      3. If the topology is a point-to-multipoint LSP topology, click Add in the Egress Routers table to open the Select Device dialog box.

        Note: The Egress Routers table is available only for P2MP topology. Select multiple routers to function as egress routers for the point-to-multiple-point topology.

      To delete an egress router added to the LSP service, select the device, and click Delete above the table of listed egress routers.

      Select Devices

      This field is available only for full-mesh LSP topology.

      1. If the topology is a full-mesh LSP topology, click Add in the Egress Routers table to open the Select Device dialog box. The Egress Routers table is available only for P2MP topology. Select multiple routers to function as egress routers for the point-to-multiple-point topology.

      2. To delete an egress router added to the LSP service, select the device, and click Delete above the table of listed egress routers.

    2. Click Next to proceed to the next page of the wizard, which is to configure path settings.

      The Path Settings page of the wizard is displayed.

    Configuring MPLS Path Settings

    The Path Settings page of the service order creation wizard enables you to view existing paths or add, edit, or delete new paths.

    1. Fill in the parameters as indicated in the following table under the Primary and Secondary tabs of the Path Parameters page.

      Item

      Action

      Path Name

      Define the path to be either automatic path selection or a new path name. If you do not configure both primary and secondary paths for an LSP, MPLS uses an automatic path selection algorithm.

      Automatic

      (Optional) Select this option from the Path Name list for an automatic path to be used for the LSP.

      Create New

      (Optional) Click this button create a new path.

      The Create MPLS Path dialog box is displayed.

      To add one or more new paths:

      1. Type a name in the Path Name text box.
      2. Select whether you want the LSP path to be Loose or Strict.

        To configure complete path information, specify every router hop between the ingress and egress routers, preferably by selecting the Strict attribute. To configure incomplete path information, specify only a subset of router hops. Select the Loose attribute in places where the path is incomplete. For incomplete paths, the MPLS routers complete the path by querying the local routing table. This query is performed on a hop-by-hop basis, and each router can obtain only enough information to reach the next explicit hop. It might be necessary to traverse a number of routers to reach the next (loose) explicit hop.

      3. Type an IP address in the IP address text box.
      4. Click Add to add the path to the table that displays all the configured paths. Alternatively, select a path from the table and click Delete to remove the path for the LSP.

      Hop limit

      Specify the hop limit of the LSP.

      Range: 2 through 255. A path with two hops consists of the ingress and egress routers only.

      Default: Each LSP can traverse a maximum of 255 hops, including the ingress and egress routers.

      Class of service

      Select one of the following values to specify the class of service (CoS) type for the LSP:

      • Background—Background type applications such as e-mail and FTP; has a CoS value of 1

      • Best Effort—Traffic to be transmitted as a best-effort type; has a CoS value of 0

      • Excellent Effort—Traffic to be transmitted as an excellent-load type; has a CoS value of 3

      • Critical Applications—Traffic to ensure a high-quality user experience for users of business-critical applications; has a CoS value of 2

      • Video < 100 ms—Streaming type applications such as video on demand and multimedia messaging; has a CoS value of 5

      • Voice < 10 ms—Voice messaging such as VoIP; has a CoS value of 6

      • Internetwork Control—Packets with internetwork control precedence; has a CoS value of 4

      • Network Control—Packets with network control precedence; has a CoS value of 7.

      CoS enables both subscribers and services to be differentiated from each other. Premium subscribers can be prioritized over basic subscribers, while real-time services can be prioritized over non-real-time services. The importance of QoS increases during periods of congestion. An unloaded network can meet the needs of all subscribers and services. However, as the network load increases, the prioritization of traffic determines whether performance for subscribers and services can be maintained or be degraded.

      The high-order 2 bits of the CoS value select which transmit queue to use on the outbound interface card. The low-order bit of the CoS value is treated as the PLP bit and is used to select the RED drop profile to use on the output queue. If the low-order bit is 0, the non-PLP drop profile is used, and if the low-order bit is 1, the PLP drop profile is used. Typically, RED aggressively drops packets that have the PLP bit set. For more information about RED and drop profiles, see the Junos OS Class of Service Configuration Guide.

      This field is not applicable for local-protection type of LSPs.

      Bandwidth (Kbps)

      Specify a bandwidth in Kbps for an LSP. Each LSP has a bandwidth value. This value is included in the sender’s Tspec field in RSVP path setup messages. You can specify a bandwidth value in bits per second. If you configure more bandwidth for an LSP, it should be able to carry a greater volume of traffic. The default bandwidth is 0 bits per second.

      Standby (enable switchover)

      Select this check box to have the path remain up at all times to provide immediate switchover if connectivity problems occur.

      This check box is displayed only for secondary paths.

      Adaptive

      Select this check box if you want to configure an LSP to be adaptive when it is attempting to reroute itself. When it is adaptive, the LSP holds onto existing resources until the new path is successfully established and traffic has been cut over to the new LSP. To retain its resources, an adaptive LSP does the following:

      • Maintains existing paths and allocated bandwidths—This ensures that the existing path is not torn down prematurely and allows the current traffic to continue flowing while the new path is being set up.

      • Avoids double-counting for links that share the new and old paths—Double-counting occurs when an intermediate router does not recognize that the new and old paths belong to the same LSP and counts them as two separate LSPs, requiring separate bandwidth allocations. If some links are close to saturation, double-counting might cause the setup of the new path to fail.

        By default, adaptive behavior is disabled.

      You can include the adaptive statement in two different hierarchy levels. If you specify the adaptive statement at the LSP hierarchy levels, the adaptive behavior is enabled on all primary/secondary paths of the LSP. This means both the primary and secondary paths share the same bandwidth on common links.

      This check box cannot be selected for P2MP topology and also when the path selection type is explicit path.

      Priority

      Configure the LSP’s preemption properties by selecting a value from the Setup Priority and Hold riority lists.

      Setup Priority

      Specify a priority value, which determines whether a new LSP that preempts an existing LSP can be established. For preemption to occur, the setup priority of the new LSP must be higher than that of the existing LSP. Also, the act of preempting the existing LSP must produce sufficient bandwidth to support the new LSP. That is, preemption occurs only if the new LSP can be set up successfully. The setup priority also defines the relative importance of LSPs on the same ingress router. When the software starts, when a new LSP is established, or during fault recovery, the setup priority determines the order in which LSPs are serviced. Higher-priority LSPs tend to be established first and hence enjoy more optimal path selection.

      This field cannot be configured for local-protection type of LSPs.

      Range: Both setup-priority and reservation-priority can be a value from 0 through 7, where 0 is the highest priority and 7 is the lowest priority.

      Default: An LSP has a setup priority of 7 (that is, it cannot preempt any other LSPs) and a reservation priority of 0 (that is, other LSPs cannot preempt it). These defaults prevent preemption. When you are configuring these values, make sure that the setup priority value is lower than or equal to the hold priority value.

      Hold Priority

      Specify a hold priority value.

      This field cannot be configured for local-protection type of LSPs.

      Range: 0 through 7, where 0 is the highest priority and 7 is the lowest priority.

      The hold priority determines the degree to which an LSP holds onto its session reservation of the LSP that has been set up successfully. When the hold priority is high, the existing LSP is less likely to give up its reservation and, therefore, it is unlikely that the LSP can be preempted. You must configure the hold priority to be greater than or equal to the setup priority.

      Note: If traffic engineering admission control determines that there are insufficient resources to accept a request to set up a new LSP, the setup priority is evaluated against the hold priority of existing LSPs. An LSP with a hold priority lower than the setup priority of the new LSP can be preempted. The existing LSP is terminated to make room (that is, resources are freed) for the new LSP.

    2. View any administrative groups that are configured on the device. You can configure any new administrative groups.

      Administrative groups, also known as link coloring or resource class, are manually assigned attributes that describe the color of links, such that links with the same color conceptually belong to the same class. You can use administrative groups to implement a variety of policy-based LSP setups. Administrative groups are meaningful only when constrained-path LSP computation is enabled (CSPF, instead of Explicit Path).

      You can assign up to 32 names and values (in the range 0 through 31), which define a series of names and their corresponding values. The administrative names and values must be identical across all routers within a single domain.

      If all interfaces are set to green or yellow, they are all appropriate to be used. The primary path must transit green or yellow links and must stay away from red links. The primary path is periodically recomputed and reoptimized. Finally, this path always keeps the secondary path in hot-standby state for quick failover. You can exclude the red interfaces or links from being part of the LSP.

      Fill in the parameters as indicated in the following table under the Admin Groups table of the Path Parameters page.

      Field

      Action

      Include-all

      Select an administrative group from the menu to specify that the LSP must traverse links that include all of the defined administrative groups.

      Include-any

      Select an administrative group from the menu to define the administrative groups to include in an LSP or a path’s primary and secondary paths.

      Exclude

      Select an administrative group from the menu to define the administrative groups to exclude from an LSP or a path’s primary and secondary paths.

    3. Click Next to proceed to the final step of the wizard, which is to review the configured settings.

      The Review page of the wizard is displayed.

      Alternatively, click the Primary tab to define the primary path settings of the LSP.

    Configuring LSP Primary Path Settings

    This page is unavailable if the value in the LSP protection type field is Local Protection Only.

    On the Path Settings page, click the Primary tab. The LSP Primary Path Settings page enables you to configure primary paths on one point-to-point or several point-to-multiple-point branches. Specify the primary path to use for an LSP. You can configure only one primary path. You can optionally specify the preference, CoS, and bandwidth values for the primary path, which override any equivalent values that you configure for the LSP.

    The settings that you configured in the selected LSP service definition populate the fields on this page. If you chose to create a custom LSP service order on the General Settings page of the wizard, the fields are not populated.

    1. Fill in the parameters as indicated in the following table.

      Item

      Action

      Primary Path

      Select a primary path from the LSPs pane on the left. Based on the Topology type, the paths are listed in the following pattern:

      • P2P topology

        Ingress router–> Egress router

      • P2MP topology

        Ingress router–> Egress router 1

        Ingress router–>Egress router 2

      • Full Mesh topology

        Router 1–> Router 2

        Router 2–> Router 1

      Path Name

      From the list, select the path name that you want. This is a required field.

      For a primary path Ingress router–> Egress router , the Path Name list contains the paths on the ingress router.

      Configure any primary path setting that you selected in the LSP service definition to be editable in the LSP service order. You cannot change any setting that you configured in the LSP service definition to not be editable.

    2. Click the Secondary tab on the Node Settings page.

      The LSP Secondary Path Settings page appears.

    Configuring LSP Secondary Path Settings

    This page is unavailable if the value in the LSP protection type field is Local protection only, or if the value in the Topology field is P2MP.

    On the Path Settings page, click the Secondary tab. The LSP Secondary Path Settings page enables you to configure primary paths on one point-to-point or several point-to-multiple-point branches. The settings that you configured in the selected LSP service definition populate the fields on this page. The fields are not populated with values if you chose to create a custom LSP service order on the General Settings page of the wizard.

    1. Fill in the parameters as indicated in the following table.

      Item

      Action

      Secondary Path

      Select a secondary path from the LSPs pane on the left. Based on the Topology type, the paths are listed in the following pattern:

      • P2P topology

        Ingress router–> Egress router

      • Full Mesh topology

        Router 1–> Router 2

        Router 2–> Router 1

      Path Name

      From the list, select the path name that you want. This is a required field.

      For a primary path Ingress router–> Egress router , the Path Name list contains the paths on the ingress router.

      Configure any secondary path setting that you selected in the predefined LSP service definition to be editable in the LSP service order.

    2. Click Next to proceed to the final step of the wizard, which is to review the configured settings.

      The Review page of the wizard is displayed.

    Reviewing the Configured Settings

    The Review page of the service definition or service order creation and modification wizards enable you to view and evaluate the service parameters and components you configured in the preceding steps or on the preceding pages of the wizard. This page provides a comprehensive, single-page view of all the service elements configured using the different pages of the wizard. You can either click the buttons corresponding to the various settings at the top of the wizard page to directly traverse to the page you want to modify or click the navigation buttons at the bottom of the wizard page to go to the different pages of the wizard.

    To examine the configured settings, and modify them as needed:

    1. Click Review to view the defined parameters.

      You can examine and modify the created service order parameters. Alternatively, click the corresponding buttons at the top of the wizard page to navigate to the specific pages that pertain to the settings you want to modify.

    2. Click Edit beside any of the sections to modify the parameters corresponding to that section.

      You are taken to the page pertaining to the parameter in the wizard.

    3. Click Finish to save the service order.
    4. Click Back to return to the previous page of the wizard; otherwise, click Cancel to discard the changes.

      The service order inventory window appears.

    Modified: 2017-07-20