Creating an LSP Service Definition

Specifying General Settings

From Connectivity Services Director Release 3.0 onward, you can create a service definition for Label-switched Paths (LSPs) and use this definition for your service order.

1. From the View selector, select Service View.

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

2. Click the Build icon in the Service View of the Connectivity Services Director banner.

   The functionalities that you can configure in this mode are displayed in the task pane.

3. In the Network Services pane, select Tunnel > Service Provisioning > Manage LSP Service Definitions. The Manage Service Definitions page appears displaying all the configured LSP service definitions.
4. Click the New icon, which is present above the list of configured service definitions. The Create LSP Service Definitions dialog box appears. Note

   The availability of attributes in the service definition creation workflow varies based on whether you choose Connectivity Services Director or NorthStar Controller to manage your LSPs.

   Fill in the fields in the General window.

5. Configure the general settings as indicated in Table 1.

   Table 1: General Settings

   Field	Description
   Service Definition Name	Enter a name for the service definition.
   Description (Optional)	Enter a brief description or other comment that you want to appear in the Service Definition table. Range: 0 through 200 characters. Spaces and special characters are allowed.
   Provisioning Type	Displays either RSVP or Segment Routing based on the value you choose from the NorthStar tab in the Preferences window. Default: RSVP
   Provisioning Method	Choose either NETCONF or PCEP from the drop down to specify the provisioning method. Default: NETCONF Note: PCEP is available only if the PCEP for Provisioning check box is selected from the Northstar tab in the Preferences window.
   Topology Type	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
   Retry Limit	This field is enabled only if Enable NorthStar LSP Management is cleared from the Preferences window. Range: 0 through 10,000 Default: 0
   Retry Timer (sec)	This field is enabled only if Enable NorthStar LSP Management is cleared from the Preferences window. Range: 1 through 600 seconds Default: 30 seconds
   Bandwidth (kbps)	Specify the bandwidth in Kbps. A non-zero 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: 0 through 2147483
   LDP Tunneling	Select this check box to enable LDP tunneling. Note: The attribute is not configurable for P2MP topology and is visible only if Enable NorthStar LSP Management is disabled in the Preferences window.
   Enable Fast Reroute	Select this check box to enable fast reroute. Note: The attribute is not configurable for P2MP topology and is visible only if Enable NorthStar LSP Management is disabled in the Preferences window.
   Path Selection Type	You can select either CSPF or Explicit Path options. This field is visible only if Enable NorthStar LSP Management is disabled in the Preferences window. Default: CSPF
   LSP Protection Type	You can choose either Path Protection, Local Protection, or Path and Local Protection options from the list. This field is visible only if Enable NorthStar LSP Management is disabled in the Preferences window. Default: Path Protection
   Local Protection Type	You can choose either Link Protection or Node-Link Protection type from the list. This field is visible only if Enable NorthStar LSP Management is disabled in the Preferences window. Default: Link Protection Note: This list is unavailable if the LSP Protection Type is Path Protection.
   Auto-Bandwidth	Select the Auto-Bandwidth check box to edit Adjust Interval, Minimum Bandwidth, and Maximum Bandwidth fields. Note: Auto-Bandwidth is not configurable for Full Mesh topology and also when path selection type is Explicit Path. This field is visible only if Enable NorthStar LSP Management is disabled in the Preferences window.
   Adjust Interval (sec)	Specify the bandwidth reallocation interval. Range: 300 through 4,294,967,295 seconds Default: 86,400 seconds This field is enabled only if Auto-Bandwidth check box is selected and Enable NorthStar LSP Management is disabled in the Preferences window.
   Minimum Bandwidth (kbps)	Specify the minimum bandwidth in Kbps or an LSP with automatic bandwidth allocation enabled. Default: 1000 Kbps Range: 1 through 2147483 Kbps You must enter the minimum bandwidth to be lower than the maximum bandwidth. This field is enabled only if Auto-Bandwidth check box is selected and Enable NorthStar LSP Management is disabled in the Preferences window.
   Maximum Bandwidth (kbps)	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. Default: 10000 Kbps Range:1 through 2147483 Kbps This field is enabled only if Auto-Bandwidth check box is selected and Enable NorthStar LSP Management is disabled in the Preferences window.

6. Click Next to specify the Path Settings.

   The Path settings that you can configure for the LSP service definition are displayed.

Specifying Path Settings

1. Fill in the parameters as indicated in t Table 2.

   Table 2: Path Settings

   Field	Description
   Class of Service	Specify a decimal number. This number corresponds to a 3-bit binary number. The two higher-order bits of the CoS value is used to select the transmit queue to be usedon the outbound interface card. The lower 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 be used on the output queue. If the lower order bit is 0, the non-PLP drop profile is used, and if the lower 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 available for local-Protection type of LSPs.
   Hop Limit	Specify the hop limit of the LSP. A path with two hops consists of the ingress and egress routers only. Range: 2 through 255 Default: Each LSP can traverse a maximum of 255 hops, including the ingress and egress routers.
   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 adaptive, the LSP holds onto existing resources until the until the new path is successfully established and traffic is switched over to the new LSP. Select this check box if you want to configure an LSP to be adaptive when it is attempting to reroute itself. When adaptive, the LSP holds onto existing resources until the new path is successfully established and traffic iis 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. Note: This check box is not available for P2MP topology and also when the path selection type is explicit path.
   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 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. Note: 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 bepreempted. 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.
   Routing Method	Use the drop-down menu to select a routing method. Available options include RouteByPCC, default, adminWieght, delay, constant, distance, ISIS, OSPF Note: This attribute is visible only if Enable NorthStar LSP Management is enabled in Preferences. Default: RouteByPCC
   Max Delay	Type a value or use the up and down arrows to increment or decrement by 100. Note: This attribute is visible only if Enable NorthStar LSP Management is enabled in Preferences. Default: RouteByPCC
   Max Cost	Type a value or use the up and down arrows to increment or decrement by 100. Note: This attribute is visible only if Enable NorthStar LSP Management is enabled in Preferences. Default: RouteByPCC
   Tunnel Metric	Specify a value to configure the LSP path selection for RSVP tunnels. Note: This attribute is visible only if Enable NorthStar LSP Management is enabled in Preferences. Default: RouteByPCC

2. Click Next to save the Path Settings page information.

   Continue with specifying BFD Settings.

Specifying BFD Settings

To provide the BFD attributes for this service definition:

1. Fill in the fields on the BFD Settings page as indicated in Table 3:Note

   You cannot configure BFD settings if Enable NorthStar LSP management check box is selected in the Preferences window.

   Table 3: BFD Settings

   Field	Description
   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 255,000 milliseconds Default: 300
   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 255,000 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 Adaption	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 255,000 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 – Teardown Failure Action – Make Before Break	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 re-signaled 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.

2. Click Next to review the configured settings.

   The Review page of the wizard is displayed.

Reviewing the Configured Settings

The Review page of the service definition 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.

1. Click Review to view the defined parameters.

   You can examine and modify the created service definition 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 definition.
4. Click Back to return to the previous page of the wizard; otherwise, click Cancel to discard the changes.

   The service definition inventory window appears.