- play_arrow Introduction
- play_arrow Router Data Extraction
- play_arrow Routing Protocols
- play_arrow Equal Cost Multiple Paths
- play_arrow Static 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 Integrity Check Report
- play_arrow Virtual Local Area Networks
- play_arrow Overhead Calculation
- play_arrow Router Reference
Viewing and Modifying Policy Based Routes
The workflow is as follows:
Use the configuration files import to create your network.
View policies from the link window.
Check how the policies will affect routing by performing a path analysis.
Modify the link PBR field to perform what-if studies.
Importing the Config Files
Viewing PBR Details from the Link Window
Select the Network > Elements > Links menu. To display the PBR route map in the link table summary pane, right-click on a column header and select Table Options. Select PBR_A and PBR_Z from the Available items window and click “Add>” to move them to the Selected Item(s) window and then click “OK”.
PBR_A and PBR_Z refer to the route-map names in both directions on the link. PBR_A refers to the direction from Node A to Node Z, while PBR_Z refers to the direction from Node Z to Node A.
Scroll so that you can see the PBR_A and PBR_Z headings. Click on the columns to sort the columns and see which interfaces have policies on them.
Select a link row for a link that has an interface with a policy applied to it. Then click the PBR tab. The tab is divided into a section for the interface on Node A and a section for the interface on Node Z. Each section contains the PBR information, including the route-map, sequence number, match criteria, and the action to perform if there is a match.
Figure 1: PBR Tab
Path Placement
To perform a path placement, select Network > Path&Capacity> Path. Optionally specify a source and/or destination IP address (to match against the route map) that corresponds to a node’s loopback address or one of its interface addresses. Then click on the map the from-node followed by the to-node.
The Path window will be displayed. In addition, the Console window will display the relevant policy based routing information.
Modifying Link PBR Field
You can modify a link to specify which policy to use on an interface from the Links tab of the Network Info table. To do so, navigate to Links tab. You can sort on the PBR_A and PBR_Z column to quickly see which links have policies attached to them. The instructions are the same as given in step 1.
Select the links you want to modify from the table and click Modify. On the Modify Link window, select the PBR tab.
Enter in the name of the Policy for the interface in the node A to node Z direction or vice versa. The policy name should correspond to a route-map on node A for the AZ direction or node Z for the reverse direction. If the policy typed in is invalid, an error message will pop up. Click “OK” and view the Console message to see possible PBR policies to apply for the link interface. When you are finished modifying the link, click OK. You can then retry a path analysis.
PBR Example
The following 6-router network will explain a case of policy based routing that checks the source IP address of incoming packets against the match condition of the route-map statement to determine whether to take the action in the route-map statement. (Note that more sophisticated policies can be used to check other properties such as the destination IP address, protocol information, etc.)
In this example, router A has applied the following route-map on its interface to A1:
route-map my_route_map permit 20 match ip address 111 set interface Serial1/0/1 !
The corresponding match condition is specified in the access list (111) as follows: “access-list 111 permit 11.5.5.5 0.0.0.0.” The corresponding interface to forward to in case the match condition is satisfied is Serial1/0/1, which connects A to B. As a result of the policy, router A will forward any packet coming from A1 with a source IP address of 11.5.5.5 out the interface Serial1/0/1 toward B. A Path analysis is used to verify the routing behavior.
Suppose a path analysis is performed from A1 to D1 by selecting Network > Path & Capacity > Paths. The source and destination IP addresses must be entered in to simulate Policy Based Routing. In this case, we use 11.5.5.5 as the source IP address (router A1’s IP address). The packet is then forwarded to router B. This example uses OSPF and the links have equal OSPF metric, so after the packet is forwarded to B, it may equally well go from B to C to D to D1 as back to A and then to D to D1.
The results are also displayed in the Console. The Console messages for the left figure above are as follows:
* * * A1(A1) - D1(D1): bw= 0 * * * - - Find path from A1 to D1 (0.0.0.0) - - Apply PBR my_route_map at A: Set interface to Serial1/0/1 PBR route from A to B new 11.5.5.5 D1 0 R,A2Z 02,02 A1--A--B--C--D--D1 (OSPF) Route-cost=325. Max_Path_Bw= 1.536M Tunnels matching search criteria: 0
On the other hand, suppose a path analysis is performed from A1 to D1 using another interface IP address at A1 such as 10.10.10.17. In this case, the source IP address no longer matches the route-map condition and hence the routing table (OSPF in this case) is used instead:
The corresponding Console message appears as follows: * * * A1(A1) - D1(D1): bw= 0 * * * -- Find path from A1 to D1 (0.0.0.0) -- Apply PBR my_route_map at A: new 10.10.10.17 D1 0 R,A2Z 02,02 A1--A--D--D1 (OSPF) Route-cost=195. Max_Path_Bw= 1.536M