- 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 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
BGP Neighbor
View Neighbor Information
BGP neighbors are routers that communicate BGP routing information to one another. You can query for a BGP neighbor relationship from the Network > Protocols > BGP > BGP Neighbor menu in View or Design action mode. Alternatively, you can right-click a particular node in the map and select View>BGP Nhbrs at Node (Standard map) or View Nhbrs at Node (BGP map).
Properties Tab
The Properties tab has the following fields:
Field | Description |
---|---|
AS | The node AS. |
Neighbor AS | The neighbor node AS. |
Interface | The interface that is used to connect to the neighbor. |
Node | The name of the node (BGP speaker). |
Status | Status of the neighbor. It is either up or down. |
Group | The name of the peer group if it is applicable. |
Multihop | The optional TTL (Time to Live) number from the IOS command: neighbor {ip-address | peer-group-name} ebgp-multihop [ttl] |
VRF | The virtual routing and forwarding instance name. |
Neighbor Address | The IP address of the neighbor. |
Neighbor Node | The name of the neighbor. |
RR Client | Indicates whether the neighbor is a route reflector client or not. |
Cluster ID | The cluster ID if it is applicable. |
Address Family | Indicates if an address family such as VPNv4 or Inet-VPN is used. |
Confederation ID | Indicates the BGP Confederation ID that the AS belongs to, if any. |
Multipath | Indicates if BGP multipath has been configured for load balancing purposes. |
Next-hop self | Indicates if the router is configured as the next hop for the BGP neighbor. “ |
In and Out Policies Tabs
The In Policy tab shows all policies that are applied to incoming routes to the node from the highlighted neighbor. The Out Policy tab shows all policies that are applied to outgoing routes from the node. (Note that different literature may refer to in/out policy as import/export policy; they are equivalent.)
You should have more than one AS in your network in order to see policies.
For Cisco routers, the routing policies may specify route filtering and attribute manipulation, which use route maps, access lists, AS_path access lists, community lists, distribute lists, and filter lists.
For Juniper routers, policy statements and community lists are used. When either the In Policy tab or the Out Policy tab is selected, the policy window has the following fields:
Field | Description |
---|---|
Policy | Name of the policy |
Term/Sequence | The term number is used in the policy statement for Juniper. The sequence number is applicable to the route map for Cisco. |
Action | Permit or deny |

When a particular policy in either the In Policy or Out Policy tab is selected, the lower right pane displays the relevant statements for that policy. For instance, the in policy localonly for router RTB is shown in the figure above.
Add BGP Peering relationship
NorthStar Planner offers two ways to add BGP peering relationships; you can use either the Modify > Protocols > BGP > BGP Neighbor... menu or the Modify > Protocols > BGP > Add Multiple BGP Neighbors... menu.
To define a BGP peering relationship from a node to its neighbor node, on the menu bar navigate to Network > Protocols > BGP > BGP neighbor. Then click on the Add button to bring up the Add BGP Neighbors window as shown in the following figure.
Figure 3: Add BGP Neighbor WindowChoose the AS number and Node from the AS and Node dropdown menus. Similarly, choose the Neighbor AS number and the Neighbor Node from the Neighbor AS and Neighbor Node dropdown menus. Clicking OK results in a BGP peer being established from the Node to the Neighbor Node. To establish a BGP peering relationship in the opposite direction, simply perform the same steps but swap the AS and Node selections with the Neighbor AS and the Neighbor Node selections. Note that if you are adding a bgp neighboring relationship from a route reflector to its client, be sure to check the RR Client box and specify the Cluster ID.
To add multiple BGP peering relationships between a node and it neighbor, use the Modify > Protocols > BGP > Add Multiple BGP Neighbors... menu to bring up the Add Multiple BGP Neighbors window. The Type dropdown menu includes Intra AS and Inter AS options. The following figure shows how the Add Multiple BGP Neighbors window with Type selected as Intra AS is used to create a full mesh of IBGP neighboring relationships within the AS. Note that balanced neighbors (neighboring relationships established in both directions) are created.
Figure 4: Add Multiple BGP neighbors window