D-Link DGS-3620-52T CLI Guide - Page 169

xStack® DGS-3620 Series Layer 3 Managed Stackable Gigabit Switch CLI Reference Guide Example Following example shows how to get the BGP dampening configurations: DGS-3620-28SC:admin# show bgp dampening Command: show bgp dampening BGP Dampening State :Enabled BGP Dampening Route_Map Half Life Time Reuse Value Suppress Value MAX Suppress Time Unreachable route's Half-life :dmp1 :15 minutes :750 :2000 :45 minutes :15 mins DGS-3620-28SC:admin# 12-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. 164