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

Configuring BGP Peer Groups

You will often want to apply the same policies to most or all of the peers of a particular BGP speaker. Update policies are usually defined by route maps, filter lists, and distribution lists. You can reduce the configuration effort by defining a peer group made up of these peers.

A peer group is defined relative to a particular BGP speaker. Figure 11 shows two peer groups, eastcoast and leftcoast. Each of these peer groups is defined for router Chicago, the hub router. Routers Boston, NY, and Miami have no knowledge of being members of Router Chicago’s eastcoast peer group. Similarly, routers SanFran, LA, and SanDiego have no knowledge of being members of router Chicago’s leftcoast peer group.

The following commands configure the eastcoast peer group on router Chicago:



host1(config)#router bgp 23 

host1(config)#route-map wtset permit 10 

host1(config-route-map)#set weight 25 

host1(config-route-map)#exit 

host1(config-router)#neighbor eastcoast peer-group 

host1(config-router)#neighbor eastcoast route-map
wtset in 

host1(config-router)#neighbor 10.6.6.2 remote-as
12 

host1(config-router)#neighbor 10.6.6.2 peer-group
eastcoast 

host1(config-router)#neighbor 10.7.3.2 remote-as
12 

host1(config-router)#neighbor 10.7.3.2 peer-group
eastcoast 

host1(config-router)#neighbor 10.4.4.2 remote-as
12 

host1(config-router)#neighbor 10.4.4.2 peer-group
eastcoast

The following commands configure the leftcoast peer group on router Chicago:



host1(config-router)#neighbor leftcoast peer-group 

host1(config-router)#neighbor 10.3.3.2 remote-as
78 

host1(config-router)#neighbor 10.3.3.2 peer-group
leftcoast 

host1(config-router)#neighbor 10.3.2.2 remote-as
2143 

host1(config-router)#neighbor 10.3.2.2 peer-group
leftcoast 

host1(config-router)#neighbor 10.3.1.2 remote-as
136 

host1(config-router)#neighbor 10.3.1.2 peer-group
leftcoast

The multiprotocol extensions to BGP enable the exchange of information within different types of address families. By default, peers and peer groups exist in the unicast IPv4 address family and exchange unicast IPv4 addresses. For information on configuring and activating BGP peer groups within address families, see Configuring the Address Family.

Figure 11: BGP Peer Groups

Image g013140.gif

neighbor peer-group

Two versions of this command exist. Use to create a BGP peer group or to configure a BGP neighbor to be a member of a peer group.
To create a BGP peer group, specify a peerGroupName for the new peer group. Use the no version to remove a peer group.
To assign members to a peer group, specify an ip-address and a peerGroupName of a BGP neighbor that belongs to this group.
This command takes effect immediately.
Use the no version to remove a neighbor from a peer group.
See neighbor peer-group

Note: You cannot mix IPv4 and IPv6 peer members in a peer group. Only one type peer is allowed, IPv4 or IPv6. For example, the following error is generated if an IPv6 peer group member is added to a peer group that already has IPv4 members; that is, where the peer-group type is IPv4:

host1(config-router)#neighbor 1::1 peer-group hamburg
% Unable to set 'peer-group' for address family ipv4:unicast for peer 1::1 in core (IPv6 peer cannot be member of a peer-group of type IPv4)

For information about the inheritance of configuration values by peer groups and peers, see Inheritance of Configuration Values.

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