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

    Modifying an Explicit Path in RSVP LSP Services

    In explicit routing, the route the label-switched path (LSP) takes is defined by the ingress node. The path consists of a series of hops defined by the ingress label-switching router (LSR). Each hop can be a traditional interface, an autonomous system, or an LSP. You can choose a new explicit path from the existing paths, create and map a new explicit path, and delete the explicit path associated with RSVP service. When explicit-path LSPs are configured, the LSP is established along the path you specified.

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

    To configure an explicit-path LSP:

    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.
    4. From the Service View pane, click the plus sign (+) sign next to Tunnels, and select RSVP LSPs.
    5. From the Tasks 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. Select an RSVP service and click Modify. The Modify LSP service wizard appears.

      Note: You can modify the primary path or the secondary path of an RSVP service only.

    7. Navigate to the Path Settings page of the wizard.

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

      From 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 preference, CoS, and bandwidth values for the primary path, which override any equivalent values that you configure for the LSP.

      From 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 in the General Settings page of the wizard.

    8. Modify the primary and secondary path.

      To modify the primary or secondary path:

      1. Select a primary path or 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

      2. Select the Automaticradio button for an automatic path to be used for the LSP for the primary path or secondary path.

    9. Create a new path.

      To create a new primary or secondary path:

      1. Select the Create New radio button to create a new path. The fields to create a new path are displayed in the Path Name section.

      2. Specify the following fields:

        • Path Name—Name of the new path

        • IP address—IP address of the new path

        • Loose/Strict—Explicit Route Objects (EROs) type.

          EROs limit LSP routing to a specified list of LSRs. By default, RSVP messages follow a path that is determined by the network IGP's shortest path. However, in the presence of a configured ERO, the RSVP messages follow the path specified. EROs consist of two types of instructions: loose hops and strict hops.

          When a loose hop is configured, the hop denotes one or more transit LSRs through which the LSP must be routed. The network IGP determines the exact route from the inbound router to the first loose hop, or from one loose hop to the next. The loose hop specifies only that a particular LSR be included in the LSP.

          When a strict hop is configured, the hop identifies an exact path through which the LSP must be routed. Strict-hop EROs specify the exact order of the routers through which the RSVP messages are sent.

      3. Click Add to add the new path.

        The new path now appears in the primary and secondary paths list.

    10. Click Modify.

    Connectivity Services Director modifies the explicit path of a RSVP LSP service. If the path is topologically not feasible, either because the network is partitioned or insufficient resources are available along some parts of the path, the LSP fails. No alternative paths can be used.

    If the setup succeeds, the LSP stays on the defined path indefinitely.

    Note: Select the View Deployment Jobs option on the tasks pane in Deploy mode to check whether the deployment jobs completed successfully.

    Modified: 2017-09-13