[Contents] [Prev] [Next] [Index] [Report an Error]

Defining a Group with Static Peers

To define a BGP group that recognizes only the specified BGP systems as peers, statically configure all the system’s peers by including one or more neighbor statements. The peers on at least one side of each BGP connection must be configured statically. The peer neighbor’s address can be either an IPv6 or IPv4 address.




group group-name {

peer-as autonomous-system;

type type;

neighbor address; # One "neighbor" statement for each peer
}

For a list of hierarchy levels at which you can configure these statements, see the statement summary sections for these statements.

As the number of external BGP (EBGP) groups increases, the ability to support a large number of BGP sessions may become a scaling issue. The preferred way to configure a large number of BGP neighbors is to configure a few groups consisting of multiple neighbors per group. Supporting fewer EBGP groups generally scales better than supporting a large number of EBGP groups. This becomes more evident in the case of hundreds of EBGP groups when compared with a few EBGP groups with multiple peers in each group. The following examples illustrate this point.

For sample configurations, see the following sections:

[Contents] [Prev] [Next] [Index] [Report an Error]