- play_arrow Introduction
- play_arrow Router Data Extraction
- play_arrow Routing Protocols
- play_arrow Equal Cost Multiple Paths
- play_arrow Static Routes
- play_arrow Policy-Based Routes
- play_arrow Border Gateway Protocol
- NorthStar Planner Border Gateway Protocol Overview
- Border Gateway Protocol Recommended Instructions
- BGP Data Extraction
- BGP Reports
- BGP Options
- BGP Map
- BGP Live Status Check
- BGP Routing Table
- BGP Routes Analysis
- BGP Information at a Node
- BGP Neighbor
- Apply, Modify, or Add BGP Polices
- BGP Subnets
- Getipconf Usage Notes
- BGP Report
- play_arrow Virtual Private Networks
- NorthStar Planner Virtual Private Networks Overview
- Importing VPN Information from Router Configuration Files
- Viewing the Integrity Checks Reports
- Accessing VPN Summary Information
- Accessing Detailed Information for a Particular VPN
- VPN Topology View
- Route-Target Export/Import Relationships
- Additional Methods to Access VPN Information
- VPN Path Tracing
- VPN Design and Modeling Using the VPN Wizard
- L3 (Layer 3) VPN
- L3 Hub-and-Spoke VPN
- L2M (Layer2-Martini) VPN
- L2K (Layer2-Kompella) VPN
- VPLS-BGP VPN (for Juniper)
- VPLS-LDP VPN
- L2CCC (Circuit Cross-Connect) VPN
- Inter-AS VPN
- Forming VPN Customer Groups
- Deleting or Renaming VPNs
- VPN Configlet Generation
- Adding Traffic Demands in a VPN
- VPN Traffic Generation
- VPN-Related Reports
- VPN Monitoring and Diagnostics
- play_arrow GRE Tunnels
- play_arrow Multicast
- NorthStar Planner Multicast Overview
- NorthStar Planner Recommended Multicast Instructions
- Creating Multicast Groups
- Creating Multicast Demands
- Viewing Multicast Demands in the Network
- Comparing Multicast with Unicast
- Multicast SPT Threshold
- Multicast Reports
- Multicast Simulation
- Collecting Multicast Path Data from Live Network
- Importing Multicast Path Data
- Multicast Data Processing
- Viewing Multicast Trees
- play_arrow Class of Service
- NorthStar Planner Class of Service Overview
- NorthStar Planner Recommended CoS Instructions
- The QoS Manager
- Define Class Maps
- Create Policies for Classes
- Attach Policies to Interfaces
- Adding Traffic Inputs
- Using the Text Editor
- Reporting Module
- IP Flow Information
- Link information
- Traffic Load Analysis
- Traffic Load by Policy Class
- CoS Alias File
- Bblink File
- Policymap File
- Demand File
- Traffic Load File
- play_arrow Routing Instances
- play_arrow Traffic Matrix Solver
- play_arrow LSP Tunnels
- NorthStar Planner LSP Tunnels Overview
- Viewing Tunnel Info
- Viewing Primary and Backup Paths
- Viewing Tunnel Utilization Information from the Topology Map
- Viewing Tunnels Through a Link
- Viewing Demands Through a Tunnel
- Viewing Link Attributes/Admin-Group
- Viewing Tunnel-Related Reports
- Adding Primary Tunnels
- Adding Multiple Tunnels
- Mark MPLS-Enabled on Links Along Path
- Modifying Tunnels
- Path Configuration
- Specifying a Dynamic Path
- Specifying Alternate Routes, Secondary and Backup Tunnels
- Adding and Assigning Tunnel ID Groups
- Making Specifications for Fast Reroute
- Specifying Tunnel Constraints (Affinity/Mask or Include/Exclude)
- Adding One-Hop Tunnels
- Tunnel Layer and Layer 3 Routing Interaction
- play_arrow Optimizing Tunnel Paths
- play_arrow Tunnel Sizing and Demand Sizing
- play_arrow Tunnel Path Design
- Tunnel Path Design Overview
- Tunnel Path Design Instructions
- Designing Tunnel Paths Overview
- Backup Path Configuration Options
- Default Diversity Level
- Evaluate/Tune Options
- Advanced Options
- Viewing Design Results
- Tunnel Modifications
- Exporting and Importing Diverse Group Definitions
- Advanced Path Modification
- play_arrow Inter-Area MPLS-TE
- play_arrow Point-to-Multipoint (P2MP) Traffic Engineering
- NorthStar Planner P2MP Traffic Engineering Overview
- Point-to-Multipoint Traffic Engineering Instructions
- Import a Network That Already has Configured P2MP LSP Tunnels
- Examine the P2MP LSP Tunnels
- Create P2MP LSP Tunnels and Generate Corresponding LSP Configlets
- Examine P2MP LSP Tunnel Link Utilization
- Perform Failure Simulation and Assess the Impact
- play_arrow Diverse Multicast Tree Design
- Diverse Multicast Tree Design Overview
- Diverse Multicast Tree Instructions
- Open a Network That Already Has a Multicast Tree
- Set the Two P2MP Trees of Interest to be in the Same Diversity Group
- Using the Multicast Tree Design Feature to Design Diverse Multicast Trees
- Using the Multicast Tree Design Feature
- play_arrow DiffServ Traffic Engineering Tunnels
- DiffServ Traffic Engineering Tunnels Overview
- Using DS-TE LSP
- Hardware Support for DS-TE LSP
- NorthStar Planner Support for DS-TE LSP
- Configuring the Bandwidth Model and Default Bandwidth Partitions
- Forwarding Class to Class Type Mapping
- Link Bandwidth Reservation
- Creating a New Multi-Class or Single-Class LSP
- Configuring a DiffServ-Aware LSP
- Tunnel Routing
- Link Utilization Analysis
- play_arrow Cisco Auto-Tunnels
- play_arrow Integrity Check Report
- play_arrow Virtual Local Area Networks
- play_arrow Overhead Calculation
- play_arrow Router Reference
FRR Tuning
The Tune FRR Backup Tunnels window shows a list of the possible FRR-Link Protection or Node Protection backup tunnels that can be created or optimized. Each entry is characterized by a source and destination node pair, the Protected Node (if applicable), Link Name and protection Type. This list can be customized by using the “Filter” button, described later in this section.
You can rearrange columns by clicking and dragging column headers. You can move the Type and Protected Node columns to the front so that you can see more clearly which tunnel entries are for link protection or for node protection.
Each entry in the table corresponds to a potential FRR backup tunnel. Only after an FRR backup tunnel has been designed or tuned will the rest of the columns in its table entry be filled in. To design FRR backup tunnels, select only those desired entries from the table and then press the “Tune Selected” button. Or, you can press “Tune All” to tune all the entries shown in the table. This will pop up the Tuning Options dialog window, allowing you to adjust the FRR design parameters that will be immediately applied to the selected entries.
Most of the parameters in the Tuning Options window are identical to those in the FRR Design window, with a few differences. For example, the following are additional options in Tuning:

The “Create new tunnel(s) using selected tunnels as a template” option will create a new row in the Tuning window with the same parameters but with an additional backup tunnel protecting the given link or node. The original row will remain. The “Modify selected tunnel(s) using specific parameters” option will modify the existing backup tunnel(s) rather than creating an additional backup tunnel.

The “Remove configured paths for existing backup tunnels” option is used to allow for the backup tunnels’ paths to be redesigned.
Specify the desired options in the Tuning Options window and click “OK”. In this example, we tune all the rows. After tuning, the remainder of each row in the Tune FRR Backup Tunnels window is filled in.
For rows that remain blank in the Tune FRR Backup Tunnels window after tuning for the row, this indicates that a FRR backup tunnel was not designed. This could happen, for example, if the Reference BW Source is set to Sub-Pool BW but none of the links listed in the Tune FRR Backup Tunnels table have Sub-Pool BW.

In this example, all FRR backup paths have been successfully created and are already added to the network.
Backup tunnels created through FRR Design are automatically assigned a name of “FRRLKnum” for FRR Link Protection tunnels and “FRRNDnum” for FRR Node Protection tunnels. Notice that, in Figure 2, there are three backup tunnels named “FRRND1”. The reason is that tunnels are not required to have unique names unless the head-end node of the tunnel is the same.
Once a tunnel has been “tuned”, the latter columns in the table will be filled in. If an FRR path is successfully designed and placed, its path will show up in the Backup Route column of the Tune FRR Backup Tunnels window. Select a row in the table and click on the “Show Paths” button. The path for this tunnel will then be displayed in the Map window. A Paths window will also appear, allowing you to view either the backup path or the path of the tunnel being protected.
The Console will also display summary information regarding the total number of placed or unplaced backup tunnels for this tuning operation. If placed, the console window will indicate how many satisfied Site-Diversity or Link-Diversity or whether No Diversity was satisfied. For example:
Diversity Level= SITE Tunnel Site-Div Link-Div No-Div Unplaced Deactivated FRRBackup 2 0 0 0 0
Filtering in the FRR Tuning Window
In the Tune FRR Backup Tunnels window, you can also use the “Filter” button to view a more selective set of entries for which to tune. The following window will appear:

Node A, Node Z:The node A and node Z panels are for selecting a subset of nodes to use for filtering FRR paths. By default, all nodes in the network are used. Node A is the source, or Point of Local Repair (PLR). Node Z represents the destination, or the Next Hop / Next Next Hop node.
FRR Backup Tunnel endpoints must match (either/both) NodeA and NodeZ: This option allows you to specify the strictness of the endpoint match. Select “either” to match either Node A and Node Z. Select “both” to require a match of both.endpoints.
Primary FRR-enabled Tunnel Exists: There are three options: yes, no and "---" which means “don't care”. Selecting "Yes" means a path will be displayed only if the protected path is part of a primary FRR enabled tunnel. Selecting "no" means the opposite, and selecting "---" will ignore this option during the filter.
FRR Backup Tunnel Exists:There are three options: yes, no and "---" which means “don't care”. Selecting "Yes" means a path is displayed only if a backup tunnel exists for the protected path. Selecting no means the opposite, and selecting "---" will ignore this option during the filter.
Link is FRR Enabled: There are three options: yes, no and "---" which means “don't care”. Selecting "Yes" means a path is displayed only if the link is FRR-enabled, or requests FRR protection. See Modifying Links to Trigger FRR Backup Tunnel Creation (Cisco) for information on how to FRR-enable a link.
FRR Protection Type: This option allows the user to fetch FRR Link Protection paths, FRR Node Protection paths, or both types of FRR paths if “All” is specified.
Backup Tunnel Diversity Level:This option allows the user to fetch paths that satisfy facility, link, site, any or no diversity level.
Protected Node: Located in the Protected Element Options tab, specifying a particular set of nodes will bring up only those paths that protect these nodes.
Protected Interface: Located in the Protected Element Options tab, specifying a particular set of interface/link will bring up only those paths that protect these links.
Facilities: Located in the Protected Element Options tab, specifying a particular set of facilities will bring up only those backup paths that protect any of the nodes or links defined in the facility.