Configuring BGP in a Network

This section focuses on configuring the BGP attributes described above for different types of networks. You can use the following workflow as a guide to configuring BGP. The remainder of this section contains detailed instructions for some of the major tasks presented in the workflow.

  1. Assign AS numbers. A group of routers with a common set of administrative policies is called an Autonomous System (AS). Each AS is identified by a number, which you can specify on the individual routers comprising the AS. You can group the routers in your network into different ASs, each running a different interior gateway protocol (such as RIP, OSPF, or IGRP) within the AS and BGP between the border routers. AS numbers can be any integer value between 1 and 65,535. If the Autonomous System Number attribute has the default value of Auto Assigned, a random value between 1 and 65,535 is assigned to each router. For proper BGP operation, you should manually assign each BGP speaker an AS number using the Protocols > BGP > Configure AS Number operation.

  2. Configure BGP neighbors and peers. BGP does not automatically discover neighbors—you must specify the neighbors of each BGP speaker. Because you specify neighbors by their IP addresses, you must first set the address of each BGP speaker to a value other than Auto-Assigned. You can do this by manually configuring the IP addresses or by using the Auto-Assign IP Addresses operation. Although the model requires only that one router of each pair of neighbors configure the other as a neighbor, configuring both routers avoids problems by enabling the model to detect misconfigurations.

    When BGP is run between routers of the same autonomous system, it is termed an Internal BGP (IBGP). If the participating routers belong to different ASs, it is an External BGP (EBGP). When a BGP speaker receives an UPDATE message from an IBGP peer, the receiving BGP speaker does not forward the routing information in the UPDATE message to other IBGP peers. Because of this, each BGP speaker needs BGP connections to all other BGP speakers in its own AS to maintain a consistent view of the routing information within the AS.

  3. Configure confederations and route reflectors. In large autonomous systems, you can reduce the number of IBGP connections by using confederations or route reflectors. Confederations divide the large AS into smaller member ASs. With route reflectors certain routers reflect routes from one IBGP peer to another.

  4. Set the BGP start time. The Start Time attribute determines when BGP activity begins on a router. For best results, all BGP speakers in a network should use the same start time. When deciding on a BGP start time, be sure that it occurs after IGP converges so that BGP neighboring sessions might are set up correctly. Also, if BGP routes are being redistributed into the IGP, make sure that BGP starts before the stop time of the IGP. Otherwise, the IGP cannot distribute the routes learned through BGP to the other routers in the AS that do not run BGP.

  5. Configure route maps. Route maps enable you to alter or filter routes based on local administrative policies. These policies determine which routes are advertised and can be based on attributes such as AS path, destination prefix, communities, and MED. Each route map contains a match clause and a set clause. The match clause specifies the criteria required for a route to match the route map. The routes that meet the criteria can be either denied or permitted after the set clause is applied. The set clause specifies changes to the route’s path attributes to produce the desired behavior. You can configure route maps in the IP > IP Routing Parameters > Route Map Configuration attribute.

  6. Apply route maps. After you have configured the route maps in IP Routing Parameters, you need to apply them to neighbor processes in the Neighbor Information table. The Routing Policies attribute in this table allows you to apply route maps to updates received from or sent to a neighbor. Use the In direction in the Routing Policies table to apply a route map to updates received from the neighbor and the Out direction for advertisements sent to the neighbor. When you apply several route maps to a neighbor, be sure to list them in the same order that they should be applied to a route map. Once a route map meets a match condition in one of the route maps, no other route maps are considered.

  7. Configure filters. You can specify the following types of filters:

    • Access lists
    • Prefix lists
    • AS Path lists
    • Community lists

    Configure access lists, community lists, and prefix lists in IP > IP Routing Parameters and AS path lists in BGP Parameters. These filters are similar to route maps but they do not have a set clause. In other words, they can filter routes, but not alter them.

  8. Apply filters. There are three ways to filter routes using the filters configured in the previous step:

    • apply the filter on a per-neighbor basis in the Route Filters attribute of the Neighbor Information table
    • apply the filter to all neighbors using the Route Filters attribute in the BGP Parameters table
    • apply the filter to a route map’s match condition
  9. Configure BGP timers. The model has configurable ConnectRetry and Hold timers. The ConnectRetry timer specifies how long the node waits before it deems its attempt to establish a TCP connection unsuccessful and tries again. TCP connection setup can fail if:

    • there is no IP route to the specified neighbor
    • the neighbor’s BGP process has not started
    • the neighbor node or the link to it is not active

    The Hold timer specifies how long routes advertised by the peer are considered valid if no update or keep alive message is received from the advertising peer. The value of the Hold timer is negotiated by the BGP connection processes when they exchange OPEN messages. The KeepAlive timer is one third of the negotiated Hold timer.