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).

Click on Network > Protocols > BGP > BGP Neighbor and the BGP Neighbors window will appear.
The BGP Neighbors window displays all neighboring relationships. The top section of this window lists all BGP speakers with their neighbors and properties. The lower half has three tabs: Properties, In Policy, and Out Policy.
Figure 1: BGP Neighbors Details
Click on Show Neighbor to highlight the link between the selected neighbor pair.
With the Filter button, you can search for neighbors based on various parameters, such as AS numbers, Interface, Weight, etc. After filling in search criteria, click on the Fetch button and it will bring up the BGP Neighbor window, which shows all neighbors that match the search criteria.
Note:
For the Node field, you must choose a real node and not an AS (pseudo-node). To search on an AS, you can use the AS, Neighbor AS, and Neighbor Node fields. Note that the search for AS uses exact match on the AS number. For example, you must type in 111 rather than AS111 or 1 or 1*. Wildcards are not supported in this field.
Right-click on an entry to see the options Show “Neighbor Address = Group” and “Show peergroups with no members”.
- Show “Neighbor Address = Group”: These entries list the group underneath the neighbor address column. They are intended to provide information regarding the default settings of a BGP group, e.g., configured under [edit protocols bgp group ibgp_peers] for Juniper. These default settings may be overridden for a particular neighbor within the group.
- “Show peergroups with no members”: This option will display any BGP groups which have no neighbors listed in them.

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.)

Note:

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

Figure 2: In Policy

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, bring up the BGP Neighbors window via the Network> Protocols > BGP > BGP Neighbor menu. 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 Window
Choose 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