Create Diverse Tunnels (Planner)

When creating a route between two sites, you might not want to rely on a single tunnel to send traffic from one site to another. By creating a second tunnel (routing path) between the two sites, you can protect your network against failures and balance the network load.

Routing Director enables you to add diverse RSVP and segment routing (SR) label-switched paths (LSPs) in your network model. You can create a diversity group with two tunnels and select the diversity level at the site, shared risk link group (SRLG), or link level.

Note: We only support adjacency SID policies and we do not support Node SID policies.

To create a diverse tunnel:

Navigate to Planning > Networks > Offline Models > Model-Name > Open.
The offline topology page is displayed with the topology map at the center and the network information table at the bottom of the page.
Navigate to the Tunnels tab.
Click More > Create Diverse Tunnels.
The Create Diverse Tunnels page appears.

Enter the values by referring to the following table:

Note: Fields marked with an asterisk (*) are mandatory.

Table 1: Fields on the Create Tunnels Page
Field	Description
Provision Type*	Click the drop-down list to select a type of tunnel that you want to provision: RSVP SR (segment routing)
Diversity Group*	Specify the name of the diversity group to which this tunnel belongs. You can use alphabets, numbers, period (.), hyphen (-), colon (:), or underscore (_).
Diversity Level*	The diversity level determines the constraints that must be applied during path computation to ensure diverse and optimal paths. Select one of the following diversity levels: Link—Two paths don't intersect at any given link. Link diversity is the lowest diversity level. Shared Risk Link Group (SRLG)—Two paths don't intersect at any links or nodes within the group (except at the source and destination). SRLG diversity includes link diversity. Site—Two paths don’t intersect at any given site (except at the source and destination). Site diversity is the strongest as it includes SRLG and link diversity. Note: If a node does not belong to a site, it is considered its own site.
Tunnel 1
Name*	Specify a unique name for the tunnel. You can use any number of alphanumeric characters, period, hyphens, colons, and underscores to specify the name.
Node A*	Select the ingress node of the tunnel from the drop-down list.
Node Z*	Select the egress node of the tunnel from the drop-down list.
Planned Bandwidth	Specify the planned bandwidth of the tunnel (along with valid units, with no space between the bandwidth and units) for the tunnel. If you specify a value without units, bps is automatically applied. Valid units: B or b, M or m, K or k, or G or g.
Properties
Description	Enter a brief description about the tunnel that you are creating.
Setup Priority	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 existing tunnel can be preempted if the setup priority of the new tunnel is higher than that of the existing tunnel and the preemption releases enough bandwidth for the new tunnel.
Hold Priority	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.
Routing Method	Select a routing method from the drop-down list. The routing method determines the metric that Planner uses to compute path for tunnels. Default indicates TE Metric, IS-IS indicates IS-IS L2 or L1 metric, and OSPF indicates OSPF metric of the links.
Constraints
Admin Group Include All	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 selections allowed are 32.
Admin Group Include Any	Select one or more admin group bits. The tunnel traverse links that include at least one of the admin groups specified in this field. You can assign a maximum of 32 values.
Admin Group Exclude	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 selections allowed are 32.
Tunnel 2
Name*	Specify a unique name for the tunnel. You can use any number of alphanumeric characters, period, hyphens, colons, and underscores to specify the name.
Node A*	Select the ingress node of the tunnel from the drop-down list.
Node Z*	Select the egress node of the tunnel from the drop-down list.
Planned Bandwidth	Specify the planned bandwidth of the tunnel (along with valid units, with no space between the bandwidth and units) for the tunnel. If you specify a value without units, bps is automatically applied. Valid units: B or b, M or m, K or k, or G or g.
Properties
Description	Enter a brief description about the tunnel that you are creating.
Setup Priority	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 existing tunnel can be preempted if the setup priority of the new tunnel is higher than that of the existing tunnel and the preemption releases enough bandwidth for the new tunnel.
Hold Priority	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.
Routing Method	Select a routing method from the drop-down list. The routing method determines the metric that Planner uses to compute path for tunnels. Default indicates TE Metric, IS-IS indicates IS-IS L2 or L1 metric, and OSPF indicates OSPF metric of the links.
Constraints
Admin Group Include All	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 selections allowed are 32.
Admin Group Include Any	Select one or more admin group bits. The tunnel traverse links that include at least one of the admin groups specified in this field. You can assign a maximum of 32 values.
Admin Group Exclude	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 selections allowed are 32.

Click Submit.
A message appears indicating that the diverse tunnel is created. You are returned to the Tunnels tab where you can view the newly added tunnel.
On the Tunnels tab, select the tunnel and click Action > Update Model and Paths.
The Path Computation page appears. This pages enables you to choose the next steps that Routing Director must take.
On the Path Computation page, select one of the following options:
- All (recommended)—Routing Director recomputes paths for all tunnels and demands.
- Only Unplaced—Routing Director recomputes paths only for newly-added tunnels and demands that do not have the current path information.
- None—Routing Director does not recompute paths; it only updates parameters, such as bandwidth, link utilization, and so on.
Click Submit.
The model is saved and the processing of the request to update the model begins.
Once the processing of the update model request has successfully finished, the Reload icon on the offline topology page is enabled. Click the Reload icon.

Note: Use only the Reload icon and do not reload the browser. The Reload icon turns orange when there are computation changes that have not yet been loaded into the model and are not yet visible.

The updated model is loaded and displayed on the topology map.

Create Diverse Tunnels (Planner)

Related Documentation