- 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 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 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
Integrity Check Options Tab
NorthStar Planner automatically detects a variety of errors of various severity levels. Some of these warnings may not be of interest, or are not a source of concern for your network. For this reason, a number of options are provided in this tab to allow you to filter for just those integrity checks (ICs) that concern you.
Network OptionsNetwork Options
The Network section of the window is used to specify the set of configuration files to perform the integrity checking on. If you use NorthStar Planner to monitor the live network, you can select “Use live network”. Alternatively, select “Use specification file” and specify the configuration file folder and corresponding specification file path created by importing the configuration files.
Filter by Category
IC’s are organized into different categories, as listed in the window. You can mark the “Include All Categories” checkbox if you wish to see IC’s belonging to all categories. Otherwise, highlight just those categories you are interested in, in the “Select From” list on the left, and move them to the “Categories to be included” list on the right via the “Add->” button. Pressing the “Add All >>” button is equivalent to selecting the “Include All Categories” checkbox.
Filter by Message
You can filter the integrity check results according to specific IC messages. There is a predefined set of IC messages, each assigned its own msg ID (or message ID), which is the number preceding the message. These are listed in the left hand list of the Filter by Message section.
To customize the ICs to show, unselect “Include All Messages”, highlight just those categories you are interested in, in the “Select From” list on the left, and move them to the “Messages to be included” list on the right via the “Add->” button.
You can perform an additional filter on the messages to be included by entering text in the “And, optionally filter message by matching substring” text field. Only messages which include your text string will be considered.
Filter by Router
In the Filter by Router section, you can choose to see only those IC’s pertaining to certain routers. To do so, uncheck the “Include All Routers” checkbox, highlight the routers that you are interested in (corresponding to the routers in the network you specified), and move them to the “Routers to be included” list on the right-hand side using the “Add->”button.
You can perform an additional filter on the desired routers to be included by entering text in the “And, optionally filter routers by matching substring” textfield. Only those router names which include your text string as part of the name will be considered.
IC’s can also be categorized into two types:
Router IC - an IC that pertains to a single router
Network IC - an IC that pertains to two or more routers
For example, some users may wish to see:
All Router ICs, but only those Network ICs pertaining to the selected router(s)
All Network ICs, but only those Router ICs pertaining to the selected router(s)
None of the Router ICs and only those Network ICs pertaining to the selected router(s)
This explains why so many different options are provided. These options are explained below:
Router IC Filter | Explanation |
---|---|
Include All regardless of the selected routers (Show All) | Show all router ICs, even those pertaining to routers that are not selected. |
Include if a problem occurred in selected routers (Show Only for Selected Routers) | Show only those router ICs pertaining to the selected routers. |
Exclude if a problem occurred in selected router(s) (Show None) | Do not show any router ICs. |
Network IC Filter | Explanation |
---|---|
Include All regardless of the selected routers (Show All) | Show all network ICs pertaining to all routers in the network (that is, not just those selected) |
Include if a problem occurred in selected routers (Show Only for Selected Routers - Strict match) | Show only those network ICs for which ALL involved routers belong to the set of selected routers. |
Include if a problem occurred in any of selected routers (Show Only for Selected Routers - Loose match) | Show only those network ICs for which at least one of the involved routers belong to the set of selected routers. |
Exclude if a problem occurred in selected router(s) (Show None) | Do not show any network ICs. |
Filter by Group
In the Filter by Group section, you can choose to see only those IC’s pertaining to routers in certain topology groups. To do so, uncheck the “Include All Groups” checkbox, highlight the groups that you are interested in (corresponding to the routers in the network you specified), and move them to the “Groups to be included” list on the right-hand side using the “Add->”button.
Note that in order to select specific topology groups, the map for the selected network specification file should contain groups. Furthermore, these groups should be saved into the network baseline. If there are topology groups, but they are not appearing in the list, save the network first using File > Save Network... before creating a task for the Integrity Check report.
Filter by Severity
ICs are assigned one of four severity levels: High, Medium, Low, Warning. You can select the severity of integrity check errors to display. The severity levels corresponding to individual ICs can be set within the IC Profile Table (Tools > Options > Integrity Checks). See Integrity Check Options Tab for more information.
Additional Report Options
Save the report to make it available on the web | Make the IC report accessible for viewing via the NorthStar Planner Web interface. |
Report with the Header | Includes a header in the report that indicates the types of filters used to generate the particular report. For example, the report might show that the user is filtering by Category (only “OSPF” was selected), Message / msg ID (only message 93 was selected), Severity (all severity levels were selected), and Router / Error Source (only router “NWK” was selected). Note that you can look up the msg ID, or Message ID, in the Integrity Checks Profile Table. See Integrity Check Options Tab for more information. |
Report Type (Full / Compact) | Indicate the level of detail to be used in the report: Full or compact. Both reports will display the following fields: Category, Message, Detail, Severity, Error Source. The Full report will contain some additional information to identify the source of the error: Source File, Line #, Line Content, and msg ID. |