From the main menu select Network > Elements > Tunnels to open the Tunnels window.
This is the bandwidth required by the tunnel.
Indicates the type of the tunnel as specified in the Tunnel Attributes window. You may edit this field by right-clicking on the table and selecting Edit Type.
IncludeAll/ Exclude/ IncludeAny (J)
Allows you to set the affinity/mask of the tunnel for Cisco, or the include all, exclude, and include-any settings for Juniper Networks admin groups to prohibit particular tunnels from routing on trunks with particular attributes (admin-groups). Trunk attributes effectively color the trunk, whereas a tunnel’s affinity/mask or include-all, exclude, and include-any settings determine which color trunks the tunnel is permitted to be placed upon. You may edit this field by right-clicking on the table and selecting Edit Affinity/Mask for Cisco or Edit Include-All/Exclude/Include-Any for Juniper Networks.
The priority field of the circuit specification consists of two numbers separated by a comma (,), or a back-slash (/). The first number defines the setup priority of the circuit, and the second number the holding priority of the circuit. The holding priority should be at the same or lower priority as the setup priority of the tunnel. It is assumed that this tunnel can only be bumped by a tunnel with a setup priority higher than its holding priority.
Displays any comments you may wish to enter.
This is the user-specified name of the route for this tunnel. If “Dynamic” is specified, the route is chosen dynamically and you should not configure a path in that entry. Otherwise, you can specify a different path.
This field indicates the priority of this path/route in the “Opt” field. In the “Opt” field, NorthStar Planner will select the smallest number to be the primary route. For example, you may specify an Opt 2 for route “Backup1” and Opt 5 for “Backup2”. NorthStar Planner will sort these two routes and select Backup1 to be the primary route since its Opt is smaller.
This field displays the user-configured route/path for this tunnel.
Right-Click Menu Options
Show Path: Displays the current route and the defined routes (for example, primary and backup) of the given tunnel in the topology map. If multiple tunnels are selected, their primary paths are highlighted on the topology map, and the tunnel currently selected in the path window is highlighted with a slightly different color.
Highlight All: Displays on the Standard map the source to destination pairs of all tunnels listed in this window.
Bottlenecks: Displays the location of the bottleneck in the console when a tunnel is unplaced.
BW_Ovhd: Displays the bandwidth used by the tunnel and also the actual bandwidth allocated to the tunnel. This information is displayed in the console window.
Show Traffic Load: View a chart of the traffic load per period in the network as described in Traffic Load.
Path Table: When selected, a table will appear displaying each configured or calculated path that originates at the source node of this tunnel. Note that these paths are not necessarily associated with the tunnel, and are not to be confused with the configured or current path taken by the tunnel.
All Configured Routes: This option displays on the map the configured routes for this tunnel. If the path is dynamic rather than configured, you should use the Show Path option instead. If there are multiple paths
Aggregate Tunnels: View the total planned tunnel bandwidth between each node pair in table format. SeeAggregate Demands/Tunnels for more information.
Tunnel Type Parameter Generation
Click the Type button in the Add or Modify Demands window to access additional demand settings. Clicking OK causes the Type field to be populated with the corresponding keywords. Note that different parameters will appear for different hardware device models.
A tunnel metric (absolute, relative or don’t care) used by IGP if Autoroute Announce is checked.
Absolute: Use tunnel metric as is
Relative: Set tunnel metric relative to IGP Metric (for example, 10 would mean tunnel metric = IGP metric + 10)
Don’t Care: Tunnel metric defaults to IGP metric.
Specifies whether the tunnel is primary, secondary, or standby. This option can be configured for a tunnel originating at a Juniper Networks router by selecting Edit Type from the right-click menu of the bottom half of the Add Tunnel or Modify Tunnel window.
Announces the presence of the tunnel by the routing protocol. When Autoroute announce is enabled, the IGP will include the tunnel in its shortest path calculation when the tunnel is up
NOAA (No Autoroute Announce) corresponds to not selecting this checkbox
Generic Router Encapsulation
Zero Backup Bandwidth
Cisco feature. During reroute, the tunnel bandwidth is 0. If this is a backup tunnel, then selecting this option would mean that bandwidth will not be reserved from the link(s) for this tunnel.
If there was a policy class established and applied to this tunnel, it would appear here. You can click on the down arrow and review all policies that apply to the tunnel.
GB Tunnels can only be routed on trunks with available bandwidth in the SubPool.
Circuit cross-connect. This means that this tunnel is cross-connecting between two interfaces using CCC
No Border Flag. This is an artificial parameter used for design. When set, routing will not follow OSPF constraints. That is, the whole network is treated like a flat network.
Indicates that administrative groups/link attributes are ignored by this tunnel.
If checked, the tunnel is routed using the current Interior Gateway Protocol’s metric rather than the tunnel metric. The current routing method can be found in the Design Options, Path Placement options pane.
Indicates that the LSP can be automatically reoptimized if the existing path becomes suboptimal.
Specifies a configlet template in the
The maximum delay allowed for this tunnel. The max delay is calculated either from the delay inputted on the links, or else the value set in the Delay Parameters section of the Design Options window (by default, 1ms per 100 miles).
The maximum number of hops allowed for this tunnel.
The maximum total admin cost (sometimes referred to as “distance” or “admin weight”) allowed for this tunnel. That is, the total admin cost of all the links that the tunnel traverses should not exceed this value.
Allows you to specify path diversity requirements for
tunnels with standby or secondary paths. Select the desired level
of diversity NODEDIV for node disjoint paths
If SITEDIV is selected, the program will pair tunnels with the same originating and terminating sites. Paired tunnels are routed diversely.
Indicates that if there is a third path for this tunnel (for example, in the case of one primary plus two secondary paths), that all three paths should be designed to be diverse.
You should add an entry for the second and third path and then design the path by selecting Design>Diverse Path Design for NorthStar Planner to design this path.
Symmetric Pair Group
When there are two tunnels with the same end nodes but in opposite directions, the path routing will use the same set of links. Example, Tunnel1 source to destination is NodeA to NodeZ, and Tunnel2 source to destination is NodeZ to NodeA. Selecting Tunnel1-Tunnel2 as a symmetric pair group will place both tunnels along the same set of links. In the tunnel file, the keyword is PAIR=groupname in the type field. Tunnels in the same group are paired based on the source and destination node.
Virtual Trunk Tab
The Virtual Trunk tab is used to indicate traffic engineering tunnels advertised as links in an IGP network (OSPF or ISIS) and to indicate the corresponding metric assigned. Select the Virtual Trunk checkbox in order to configure the relevant protocol, area, and/or metric for which the virtual trunk will apply.
For Cisco, the corresponding statement would be “show mpls traffic-eng forwarding-adjacency”.
For Juniper Networks, the corresponding statement would be the “label-switched-path name metric metric” statement under the hierarchcy level [edit protocols ospf area area-id] or “label-switched-path name” under the hierarchy level [edit protocols isis]
If a tunnel is marked as a virtual trunk, it is known to other routers and its metric and available bandwidth information is broadcast to other routers as if it were a link. Just as a link has interfaces defined on both ends, two tunnels (one in each direction) must be defined as virtual trunks for this setting to take effect. Otherwise, the virtual trunk is perceived as being “down”.
VT or VT_areanumber
The OSPF area assigned to the Virtual Trunk. This option applies only if Virtual Trunk is selected and the network uses OSPF routing (as opposed to, say, ISIS routing). A tunnel that is marked as a virtual trunk is advertised as a link to other routers. If those routers perform OSPF area routing, they need to know what area this virtual trunk belongs to. Select the area from the pull-down box.