- 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 Module
- 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
- Add 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
- Set 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 Virtual Local Area Networks
- play_arrow Overhead Calculation
- play_arrow Router Reference
Compliance Assessment Results
Detailed Tab Column | Description |
|---|---|
Message | Displays information such as the general type of conformance match, mismatch, or partial match. If there is a mismatch, the line missing from the configuration is included in the Message. "not ordered" indicates that the lines are present in the configuration file but their ordering is not consistent with that of the template. "hardware type mismatch" indicates that the template type (Cisco IOS or Juniper JUNOS) does not match the configuration file type. |
Severity | There are five levels. Warning shows that compliance has failed for a given line, for example if a line is missing or failed to match. Info indicates a match or partial match. The user can also change these levels to be displayed as Minor, Major, or Critical. |
Hostname | Device hostname |
Config File | Displays the configuration file for which this entry applies. Double-clicking on a row will open this configuration file in the Main Pane. |
Block | The exact block of the configuration of the message |
Lines | Displays the corresponding start line and end line where the results entry applies. |
Template | Displays the template that was used for this compliance assessment |
Rule | Template Rule Name |
Template Lines | Range of Line numbers in which template rule occurs |
Template Line | For conform command, indicates the content of the line with violation |
Template Line # | For conform command, indicates the line number with violation |
Category | Template rule’s category (if specified) |
Vendor | Device vendor (e.g., Cisco, Juniper) |
OS | Device Operating System |
Version | Operating System Version, e.g., 12.2(53)SE |
Summary By Device Column | Description |
|---|---|
Hostname | Device name converted into Paragon Planner format |
Rules Applied | Number of template rules applied to the device |
Config Blocks Applied | Number of config blocks for which the rule was applied |
Issues | Number of issues |
Criticals | Number of critical issues |
Majors | Number of major issues |
Minors | Number of minor issues |
Warnings | Number of warnings |
Infos | Number of informational messages |
Score | Compliance score = 100 - (#criticals * 1/#rules * critical_weight) - (#majors * 1/#rules * major_weight) - (#minors * 1/#rules * minor_weight) - (#warnings * 1/#rules * warning_weight) - (#infos * 1/#rules * info_weight) |
By Rule Column | Description |
|---|---|
File | Template Rule Name |
Rules Applied | Template File Name |
Routers Applied | Number of routers for which the rule was applied |
Config Blocks Applied | Number of config blocks for which the rule was applied |
Issues | Number of issues |
Criticals | Number of critical issues |
Majors | Number of major issues |
Minors | Number of minor issues |
Warnings | Number of warnings |
Infos | Number of informational messages |
Score | Compliance score = 100 - (#criticals * 1/#rules * critical_weight) - (#majors * 1/#rules * major_weight) - (#minors * 1/#rules * minor_weight) - (#warnings * 1/#rules * warning_weight) - (#infos * 1/#rules * info_weight) |
To save the contents in the results tab, select the Export to CSV icon in the toolbar to export to a CSV file, which can be opened in Microsoft Excel. Enter in a filename. Note that 3 CSV files will be created -- one for each tab.
filename_result.csv -- Detailed tab
filename_Result_NODE.csv -- Summary By Device tab
filename_Result_RULE.csv. -- By Rule tab
