Page 126 / 757 Scroll up to view Page 121 - 125
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
122
config bgp dampening
Purpose
This command is used to configure BGP process’s dampening configurations
Syntax
config bgp dampening [ route_map <map_name 16> | clear_routemap | { state [enable |
disable] | half_life <min 1-45 > | reuse<value 1-20000> | suppress <value 1-20000> |
max_suppress_time <min 1-255 >| un_reachability_half_life <min 1-45>}(1)]
Description
The purpose of this command is to eliminate the dampening of routes and thus to avoid
unstable networks caused by flapping routes. The following describes the way it is achieved.
If a prefix is removed or is added, BGP will add a penalty on the route of 1000; if an attribute
of received route changes, BGP will add a penalty on the route of: 500.
Suppose that the half-life is configured to be 15min, the re-use value will be 800, and the
suppress value will be 1500.
When a route flaps (from up to down), add the penalty by 1000.Since the penalty is smaller
than the suppress value, BGP will work normally. It will send a withdraw message (an update
message) to the neighbors.
The penalty of the route will decrease as time elapses. Here we assume that if it passes 7.5
minutes, then the penalty of the route is 1000-500*7.5/15=750.
If another flap occurs (the route changes from down to up) then the penalty of the route will
be 1750, which is larger than the suppress value, and the route will be dampened. BGP will
not send an update message for this status change.
When the penalty of the route decreases and becomes smaller than the re-use value (800),
the route will not be dampened and the update message will be sent again.
Lastly, the max-suppress-time is the longest time the route may be suppressed. So, it
decides the maximum penalty a route may suffer regardless of the number of times that the
prefix is dampened. Here is the formula: Maximum-penalty= reuse-value*2max-suppress-
time/half-life
NOTE:
If the dampening ability is enabled and there are one or more dampened routes, the
dampened routes will be released to be the normal state immediately after we disable the
dampening function.
Parameters
state
- Specifies the BGP dampening function’s state.
half_life
- Specifies the time (in minutes) after which the penalty of the reachable routes will
be down, by half. The default setting is 15 minutes.
reuse
- If the penalty for a flapping route decreases enough to fall below this value, the route
is unsuppressed. The default setting is 750.
suppress
- A route is suppressed when its penalty exceeds this limit. The default setting is
2000.
max_suppress_time
- The maximum time (in minutes) a route can be suppressed. The
default setting is 60 minutes
un_reachablity_half_life
- Specifies the time (in minutes) after which the penalty of the
unreachable routes will be down, by half. The default setting is 15 minutes.
route_map
- This is to set the dampening running configuration..
clear_routemap
- This option will withdraw the route map configuration.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To disable the dampening function:
Page 127 / 757
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
123
DGS-3427:5#config bgp dampening state disable
Command: config bgp dampening state disable
Success.
DGS-3627:admin#
show bgp dampening
Purpose
This command is used to show the BGP dampening configurations.
Syntax
show bgp dampening
Description
The purpose of this command is to show the BGP dampening configurations.
Parameters
None.
Restrictions
None.
Example usage:
To display the BGP dampening configurations:
DGS-3627:admin#
show bgp dampening
Command:4# show bgp dampening
BGP Dampening State
:Enabled
BGP Dampening Route Map
:dmp1
Half-life Time
:15 mins
Reuse Value
:750
Suppress Value
:2000
MAX Suppress Time
:45 mins
Unreachable route's Half-life :15 mins
DGS-3627:admin#
config bgp peer_group
Purpose
This command is used to configure the BGP peer group.
Syntax
config bgp peer_group <peer_group_name 16> [add | delete] <ipaddr>
Description
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 of 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 exist 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
Page 128 / 757
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
124
config bgp peer_group
from the peer group. The following is a list of them:
capability_orf_prefix_list
next_hop_self
route_reflector_client
send_community
soft_reconfiguration_inbound
remove_private_as
allowas_in
holdtime
keepalive
unsuppress_map
filter_list for out direction
route_map for out direction
prefix_list for out direction
AS Orginate timer
Connect timer
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 attributes 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.
default_originate.
update_source.
As for the above attributes, setting the attribute of a peer group will automatically affect the
setting for individual peers in the peer group.
If Users configure the peer group’s session state to disable, all the peer group members
session state can’t be set to enable. Users can’t set the peer group’s session activity to
disable.
As for the description attribute, setting the peer group will not affect the setting for an
individual peer.
Parameters
<peer_group_name>
- This is the name of the BGP peer group. The length is up to 16 bytes.
<ipaddr>
- The IP address to be added or deleted.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To delete a member from the peer group named “local”:
Page 129 / 757
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
125
DGS-3627:admin#
config bgp peer_group local delete 10.2.2.2
Command: config bgp peer_group local delete 10.2.2.2
Success.
DGS-3627:admin#
config bgp peer_group remote_as
Purpose
This command is used to configure the BGP peer group’s remote AS number.
Syntax
config bgp peer_group <peer_group_name 16> remote_as <as_number 0-65535>
Description
The command is used to configure the AS number of a BGP peer group.
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.
The default AS number is 0.
Parameters
<peer_group_name>
- The name of the BGP peer group. The length is up to 16 bytes.
<as_number 0-65535>
- The number of autonomous systems to which the peer group
belongs to. The range is from 0 to 65535.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To set a peer group named local remote_as to 50:
DGS-3627:admin#
config bgp peer_group local remote_as 50
Command: config bgp peer_group local remote_as 50
Success.
DGS-3627:admin#
create bgp neighbor
Purpose
This command is used to create a BGP neighbor.
Syntax
create bgp neighbor [<ipaddr> [remote_as <as_number 1-65535>| peer_group
<peer_group_name 16>] | peer_group <peer_group_name 16>]
Description
The command is used to create a BGP neighbor. Either a single router or a peer group can
be a neighbor.
If the created neighbor has a single IP address, the remote AS must be specified. A peer
group must be specified for which this BGP speaking neighbor belongs to, and in this
condition, a remote AS must be specified to the peer group first.
If the created neighbor is a peer group, then the remote AS cannot be specified here. The
remote AS must specified by using the config peer_group remote_as command.
Parameters
<ipaddr>
- The IP address of the BGP speaking neighbor.
<peer_group_name>
- Specifies the peer group to be created and added as a neighbor.
<as_number>
- The number of Autonomous Systems to which the neighbor belongs. The
range is from 0 to 65535.
Restrictions
Only Administrator and Operator-level users can issue this command.
Page 130 / 757
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
126
Example usage:
To create a neighbor peer whose address is 10.10.10.2:
DGS-3627:admin#
create bgp neighbor 10.10.10.2 remote_as 10
Command: create bgp neighbor 10.10.10.2 remote_as 10
Success.
DGS-3627:admin#
delete bgp neighbor
Purpose
This command is used to delete the BGP neighbor.
Syntax
delete bgp neighbor [<ipaddr> | peer_group <peer_group_name 16> | all]
Description
The command is used to delete a BGP neighbor.
Parameters
<ipaddr>
- Specifies the IP address of the neighbor that will be deleted.
<peer_group_name>
- Specifies the peer group that will be deleted as a neighbor.
all
- Delete all BGP neighbors, including individual peers and peer groups.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To delete a neighbor whose address is 10.10.10.2:
DGS-3627:admin#
delete bgp neighbor 10.10.10.2
Command: delete bgp neighbor 10.10.10.2
Success.
DGS-3627:admin#
config bgp neighbor description
Purpose
This command is used to configure the BGP neighbor’s description attribute.
Syntax
config bgp neighbor [<ipaddr> | peer_group <peer_group_name 16>] [description
<desc 80> | clear_description]
Description
The command is used to configure the description for a BGP neighbor.
Parameters
<ipaddr>
- Specifies the IP address of the neighbor to be configured.
<peer_group_name>
- Specifies the peer group to be configured.
description
- Associate a description with a neighbor. By default, the description is not
specified.
clear_description
- Removes the neighbor’s description.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To configure a neighbor’s description:

Rate

4.5 / 5 based on 2 votes.

Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top