D-Link xStack, Reference Manual

Page: 196 / 1284

xStack® DGS-3620 Series Layer 3 Managed Stackable Gigabit Switch CLI Reference Guide
191
13-19 config bgp peer_group
Description
This command is used to configure the BGP peer group. The purpose of the neighbor peer group
is to simplify the BGP neighbor configuration. The command is used to add an IP or to delete an IP
from a BGP peer group. The peer group must be created using the “create neighbor peer group”
command. The members must all be internal or external. If all the members of the BGP peer group
are external, they are allowed to have different AS numbers. There are two kinds of the peer
groups.
For the first kind or peer group, the remote AS is not set; members must be created as neighbors
before it can be added to the peer group. When we configure the peer group’s remote AS behind
this, the member’s remote AS will not change. For the second kind of peer group, the peer group
has set a remote AS number. A member can be added to the peer group even if the member didn’t
have an AS number before. In this situation, the system will create a neighbor for the peer group’s
remote AS automatically. The member’s remote AS will change to the configured peer group’s
remote AS, but the others’ will not change, which is created as a neighbor before added to the
peer group.
If a BGP peer belongs to a peer group, some attributes or actions can only be configured from the
peer group. The following is a list of them: local_as, capability_orf_prefix_list, next_hop_self,
route_reflector_client, send_community, soft_reconfiguration_inbound, remove_private_as,
allowas_in, holdtime, keepalive, unsuppress_map, default_originate, filter_list for out direction,
route_map for out direction, prefix_list for out direction.
On the contrary, some attributes or actions are allowed to be configured from both the peer group
and the member. If they are configured from the member, the setting will overwrite the setting
configured from the peer group.
Other attribute that can be set from an individual peer are as follows: description, filter_list for in
direction, route_map for in direction, prefix_list for in direction, ebgp_multihop, session state,
session activity, weight.
As for the above attributes, setting the attribute of a peer group will automatically affect the setting
for individual peers in the peer group.
For session state, if the peer group is configure to disable, all the members can’t set to enable. For
session activity, can’t set the peer group to disable.
As for the description attribute, setting the peer group will not affect the setting for an individual
peer.
After this command is executed, all peers belonging to this peer group, which are generated with
no indicated AS number, will change their AS number to the same value as the peer group’s, stop
and restarted values. If the peer group remote AS has a value of zero, it means “no remote_as”,
and members that are generated with no indicated AS number will be deleted.
Format
config bgp peer_group <peer_group_name 16> [remote_as <as_number 0-4294967295> |
[add | delete] <ipaddr>]
Parameters
<peer_group_name 16> - This is the name of the BGP peer group. This name can be up to 16
characters long.