- 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 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 Fast Reroute
- NorthStar Planner Fast Reroute Overview
- Fast Reroute Supported Vendors
- Import Config and Tunnel Path
- Viewing the FRR Configuration
- Viewing FRR Backup Tunnels
- Viewing Primary Tunnels Protected by a Bypass Tunnel
- Modifying Tunnels to Request FRR Protection
- Modifying Links to Configure Multiple Bypasses (Juniper only)
- Modifying Links to Trigger FRR Backup Tunnel Creation (Cisco)
- FRR Design
- FRR Auto Design
- FRR Tuning
- Viewing Created Backup Tunnels
- Generating LSP Configlets for FRR Backup Tunnels
- Failure Simulation—Testing the FRR Backup Tunnels
- Exhaustive Failure
- Link, Site and Facility Diverse Paths
- play_arrow Cisco Auto-Tunnels
- play_arrow Integrity Check Report
- play_arrow Compliance Assessment Tool
- Compliance Assessment Tool Overview
- Using The Compliance Assessment Tool
- CAT Testcase Design
- Creating a New Project
- Loading the Configuration Files
- Creating Conformance Templates
- Reviewing and Saving the Template
- Saving and Loading Projects
- Run Compliance Assessment Check
- Compliance Assessment Results
- Publishing Templates
- Running External Compliance Assessment Scripts
- Scheduling Configuration Checking in Task Manager
- Building Templates
- Special Built-In Functions
- Paragon Planner Keywords For Use Within a Rule
- More on Regular Expressions
- IP Manipulation
- play_arrow Virtual Local Area Networks
- play_arrow Overhead Calculation
- play_arrow Router Reference
Sizing Tunnels
Although the steps below are for tunnel sizing, demand sizing works the same way.
Open a network project spec that contains tunnels, by double-clicking on the specification file in the File Manager.
Since the tunnel sizing feature is designed for use in Tunnel layer, switch to Tunnel layer mode by clicking on the Tunnel layer button on the main menu bar, as shown below.
Figure 1: Tunnel Layer Button
If you plan to resize your tunnels based upon the bandwidth of routed end to end flows, you should have demands defined in your network, in the demand file. If not, you can add some by switching into Modify mode, and selecting Modify > Elements > Demands... and selecting Add > Multiple Demands....
If you plan to resize your tunnels based upon actual measured tunnel traffic statistics, then you should have read in the NorthStar Planner formatted tunnel traffic load file. To read it in, go to File > Load Network Files and select the entry T_trafficload (for “tunnel trafficload”) and click Browse to find the desired input file. Alternatively, you can simply include the tunnel trafficload file into your specification file with the following line:
T_trafficload = T_trafficload.runcodeThe following shows the tunnel traffic load format for one tunnel, named tunDenDet, originating at node DEN and with three periods of measured tunnel traffic:
DEN:tunDenDet A2Z - 3.0M 4.0M 9.1KSelect Report > Report Manager to open the Report Manager window. At least one of the following reports will be of interest to you.
If you plan to resize your tunnels based upon the bandwidth of routed end to end flows, click on the “Demand Traffic on Tunnel” report in the left pane under Tunnel Layer Network Reports > Tunnel Reports to generate and view it in the right-pane. This report provides information on existing tunnels such as the tunnel’s planned bandwidth (Bandwidth), the total bandwidth of flows traversing the tunnel (FlowBW), and the difference between those two values (BW_Diff). This report identifies network inefficiencies by allowing the user to see the under-booked and over-booked tunnels in the network. The tunnel sizing feature can then automate an adjustment of these tunnels’ bandwidths according to user-specified settings.
Figure 2: Demand Traffic on Tunnel Report (formerly Planned Tunnel Util)
If you plan to resize your tunnels based upon actual measured tunnel traffic statistics, click on the “Measured Tunnel Traffic” report. This displays the measured tunnel traffic load numbers, as read in from the T_trafficload file, in tabular format.
In Design mode, select Design > TE Tunnels > Tunnel Sizing. If you did not switch to Tunnel layer earlier, the program will ask you to switch to Tunnel layer. Click “Yes” to continue.
A Find Tunnels window will appear as shown in Figure 275. In addition to the regular options, there are options specific to tunnel sizing. Those fields are described in the table below
Figure 3: Find Tunnels for Tunnel Sizing
Field
Description
BW Diff (KB) greater than
If the absolute value of the difference between the tunnel bandwidth and total flow bandwidth is greater than this value (expressed in kilobits), then those tunnels are fetched.
BW Diff Ratio greater than
If the absolute value of the ratio of bandwidth difference to tunnel bandwidth is greater than this value, then those tunnels are fetched.
Sort Field
Sorts the displayed tunnels by either bandwidth difference or bandwidth difference ratio.
Sort Order
Sorts the displayed tunnels according to the type in the Sort field; sorts either in decreasing order or in decreasing order of the absolute value.
BW Source
Specifies the source of traffic: “Layer 3 Demands” or “Traffic Load” (measured tunnel traffic). This parameter will show up as the “FlowBW” field in the Tunnel Sizing window. It is also used as the flow bandwidth of the new bandwidth calculation.
Traffic Period
This field specifies the time period of traffic to be used. If the BW Source is Layer 3 Demands, then the Planned traffic from the demand file is used. If the BW Source is Tunnel Traffic Load, then possible values are Period1 through Period24, and Peak. Peak indicates the heaviest/worst load experienced among any of these 24 traffic periods.
# Tunnels Per Page
Specifies how many tunnels to display per page.
The next step is to check your tunnel sizing options. In the Find Tunnels window, select the “Sizing Parameters” tab.
Note:Alternatively, you can set the sizing parameters globally via Tools > Options > Design and click on the “Demand/Tunnel Sizing” options pane. When the options in the Design Options window are set, click “OK”. A window will ask you whether to reroute the tunnels. You can click “No” since changing the tunnel sizing options does not affect tunnel routing. (You are prompted because the program is aware that you have modified the design options. Though the tunnel sizing options do not affect routing, other design options might.)
Figure 4: Tunnel Sizing Parameters
Set the sizing parameters to your preferred setting. The table below describes each field.
When the options have been selected, click “OK” to fetch tunnels that match the specified criteria. Those tunnels will then be displayed in the Tunnel Sizing window as shown in Figure 4.
Field
Description
Parameter in Dparam File
Minimum Tunnel BW
The minimum value to be assigned for any new tunnel bandwidth. If the calculated bandwidth is less than this value, then this value is used as the new bandwidth.
minSizingBW
Maximum Tunnel BW
The maximum value to be assigned for any new tunnel bandwidth. If the calculated bandwidth is greater than this value, then this value is used as the new bandwidth.
maxSizingBW
Tunnel BW Increment
The increment by which the bandwidth will be increased. Basically, the calculated bandwidth will be rounded up to the nearest multiple of this value.
incSizingBW
Tunnel Growth Multiplier
This value is multiplied by the total flow bandwidth to calculate the new bandwidth. For example, 1.00 will generate a new tunnel bandwidth assignment that is 100% of the total flow bandwidth traversing the tunnel, and 1.5 will generate a value that is150% of the traffic load bandwidth.
sizing_growthmultiplier
Tunnel Growth Constant
A constant offset to add in the calculation of the new bandwidth.
sizing_growthconstant
Standby Tunnel BW %
If the primary tunnel being resized has an associated standby tunnel, then use this field to indicate a percentage value of the new primary tunnel bandwidth that should be used to set the standby tunnel bandwidth. The default is 100%, or the same as the primary tunnel bandwidth.
sizing_standbypct
Resize Option
The “Only Increase” option is for sizing only overbooked tunnels. When this option is set, a new bandwidth will only be calculated if the total flow bandwidth is greater than or equal to the current planned tunnel bandwidth.
When the “Fit to Traffic” option is set, a new bandwidth will always be calculated.
sizing_resizeopt
Figure 5: Tunnel Sizing Window
In the Tunnel Sizing window, each entry in the table represents a tunnel. The “Bandwidth” column indicates the planned tunnel bandwidth. The “Flow BW” column indicates the actual measured traffic load on that tunnel based upon the inputs in the T_trafficload file. The “New BW” column, in white, will automatically be populated with a proposed new bandwidth value for each tunnel, based upon the Tunnel Sizing option settings specified in the Design Options window. If a “New BW” column field is blank, that indicates that the Tunnel Sizing conditions were not met for this particular demand, and no new value is proposed. For more information on how exactly this field is calculated, see Calculation of the New Tunnel Bandwidth.
The proposed “New BW” values for the tunnels is not taken into effect until you confirm, or approve of the changes. To do so, you can either press “Confirm All” to approve all the proposed changes. Once an entry is confirmed, the “Bandwidth” column will be replaced by the value in the “New BW” column, and the “New BW” column will be cleared. You can also highlight just the desired entries in the table (using <SHIFT>-click and <CTRL>-click for multiple selection), and press the “Confirm Selected” button to approve just the changes in the selected rows.
To adjust the Tunnel Sizing options for selected tunnels, you can do so directly in the Tunnel Sizing window, by selecting the desired table entries, and pressing the “Recalculate Selected” button. You will then be prompted to enter the desired Tunnel Sizing parameters, which will be applied only to the selected tunnels. Enter the new values here and click “OK” to recalculate.
Figure 6: Options Window To Recalculate Selected Tunnels
Once you are satisfied with your changes in the Tunnel Sizing window, press the “OK” button. Any changes that were confirmed should now be in effect. Any new bandwidth value that was not confirmed will not be saved when the Tunnel Sizing window is closed.
During the confirmation process, the server will determine if the tunnel using the new bandwidth value can be placed. If it cannot be placed, the tunnel will keep its old bandwidth, and an error message will be displayed in the console.
The following sections describe some other features available in the Tunnel Sizing window.
The columns in the Tunnel Sizing table can be customized to show or hide certain fields. Right-click on the table and select “Customize Current View” from the pop-up menu (Figure 6). A window will appear that allows the user to select the desired columns for display.
Figure 7: Right-click Pop-up Menu
The table can also be sorted by any column by clicking on the column header. This sorts the tunnels currently displayed in the table.
If there are multiple pages of tunnels, the user may wish to sort the tunnels across all the pages by either BW diff or BW diff ratio in order to see the most overbooked tunnels on one page. This can be done in the previous “Find Tunnels” window. If the tunnels have already been fetched, you may sort by right-clicking on the body of the table and selecting “Sort Globally”. A window will appear as shown in Figure 280 allowing you to select the sorting options.
Figure 8: Select Sort Options Window
You may override the suggested new bandwidth by typing in a new value directly into the table. To do this, either double-click on the tunnel’s “New BW” field. The table cell will then become editable. Alternatively, right-click on the selected tunnel(s) and choose “Replace New BW Values”. You will then be prompted to enter a new BW value for those tunnel(s).
