1. Home
    2. /
  2. Manuals
    3. /
  3. D-Link
    4. /
  4. DGS-3612
    5. /
  5. 29
Page 141 / 757 Scroll up to view Page 136 - 140
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
137
clear bgp
Purpose
This command is used to reset the Border Gateway Protocol (BGP) connections using hard
or soft reconfigurations.
Syntax
clear bgp [all | ipaddr <ipaddr> | as <as_number 1-65535> | peer_group
<peer_group_name 16> | external ] {soft {[ in { prefix_filter} | out ]}}
Description
This command is used to initiate a hard reset or a soft reset for a connection.
If a hard reset is applied to the inbound session, the inbound session will be torn down and
the local inbound routing table and the remote outbound routing table will be cleared.
If a soft reset is applied to the inbound session, the session will not be rebuilt but the local
inbound routing table will be cleared and needs to be rebuilt.
If a soft reconfiguration inbound is enabled, then the routing table can be rebuilt based on the
stored route updates information. If a soft reconfiguration inbound is disabled, then the local
router will send the route refresh request to the neighbor to ask for the route refresh.
When the inbound session is soft reset with the prefix filter option, and the
capability_orf_prefix_list is enabled in the send direction, then the local BGP will send ‘clear
the routing table’, and notify the remote neighbor for the prefix filter.
This is a way to notify the neighbor of the prefix filter whenever a change is made to the
prefix filter.
Parameters
all
- Specifies that all current BGP sessions will be reset.
<as_number>
- Specifies to reset sessions with BGP peers in the specified Autonomous
System.
peer_group
- Specifies to reset a peer group.
ipaddr
- Specifies to reset the session with the specified neighbor.
external
- All eBGP sessions will be reset.
soft
- Initiates a soft reset. Does not tear down the session.
in
- Initiates inbound reconfiguration. If neither in nor out keywords are specified, both
inbound and outbound sessions are reset.
prefix_filter
- The local site configured prefix filter will be notified to the remote neighbor when
inbound soft reset is applied.
out
- Initiates outbound reconfiguration.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To reset all Border Gateway Protocol (BGP) connections:
DGS-3627:admin#
clear bgp all
Command: clear bgp all
Success.
DGS-3627:admin#
clear bgp ipaddr 10.10.1.2 soft in
Command: clear bgp ipaddr 10.10.1.2 soft in
Success.
DGS-3627:admin#
clear bgp dampening
Purpose
This command is used to clear the BGP route dampening information and to unsuppressed
suppressed routes.
Syntax
clear bgp dampening {[<ipaddr> | <network_address>]}
Page 142 / 757
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
138
clear bgp dampening
Description
This command clears the route dampening information stored in the routing table. If no
parameters are specified, the dampening information for the entire routing table will be
cleared.
Parameters
<ipaddr>
- Specifies an IPv4 address to clear the dampening information.
<network_address>
- Specifies an IPv4 network to clear the dampening information.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To clear route dampening information from network 192.168.10.0/24 and free suppressed routes:
DGS-3627:admin#
clear bgp dampening 192.168.10.0/24
Command: clear bgp dampening 192.168.10.0/24
Success.
DGS-3627:admin#
create bgp as_path access_list
Purpose
This command is used to configure an Autonomous System path access list.
Syntax
create bgp as_path access_list <list_name 16>
Description
The command is used configure an Autonomous System path access list. You can apply an
Autonomous System path access list to both inbound and outbound routes exchanged by a
BGP peer session.
Parameters
<list_name 16>
- AS path access list name.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To create an Autonomous System path access list:
DGS-3627:admin#
create bgp as_path access_list test
Command: create bgp as_path access_list test
Success.
DGS-3627:admin#
config bgp as_path access_list
Purpose
This command is used to configure matching rules for an Autonomous System path access
list using regular expressions.
Syntax
config bgp as_path access_list <list_name 16> [add | delete] <regexp_str 80> [deny |
permit]
Description
This command configures the match rules for the AS list. Each rule is defined by a regular
expression.
Parameters
<list_name 16>
- AS path access list name.
add
- Add a matching rule.
delete
- Delete a matching rule.
Page 143 / 757
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
139
config bgp as_path access_list
<regexp_str 80>
- Regular expression that defines the as_path filter.
permit
- Permits advertisement based on matching conditions.
deny
- Denies advertisement based on matching conditions.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
This example configures a matching rule for an AS path access list:
DGS-3627:admin#
create bgp as_path access_list test
Command: create bgp as_path access_list test
Success.
DGS-3627:admin# config bgp as_path access_list test add (_64[6-9][0-9][0-9]_|_65[0-9][0-
9][0-9]_) deny
Command:4# config bgp as_path access_list test add (_64[6-9][0-9][0-9]_|_65[0-9][0-9][0-
9]_) deny
Success.
DGS-3627:admin# config bgp as_path access_list test add .* permit
Command: config bgp as_path access_list test add .* permit
Success.
DGS-3627:admin#
delete bgp as_path access_list
Purpose
This command is used to delete an Autonomous System path access list.
Syntax
delete bgp as_path access_list [ list_name <list_name 16> | all]
Description
This command is used to delete an Autonomous System path access list.
Parameters
<list_name 16>
- AS path access list name.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To configures a matching rule for an AS path access list:
DGS-3627:admin# delete bgp as_path access_list list_name test
Command: delete bgp as_path access_list list_name test
Success.
DGS-3627:admin#
show bgp as_path access_list
Purpose
This command is used to display the Autonomous System path access list.
Syntax
show bgp as_path access_list {<list_name 16>}
Page 144 / 757
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
140
show bgp as_path access_list
Description
This command displays the Autonomous System path’s access list. If a specific access list is
not specified, all AS path access lists will be displayed.
Parameters
<list_name 16>
- AS path access list name.
Restrictions
None.
Example usage:
To display an AS path access list:
DGS-3627:admin#
show bgp as_path access_list 1
Command: show bgp as_path access_list 1
BGP AS Path Access List: 1
deny (_64[6-9][0-9][0-9]_|_65[0-9][0-9][0-9]_)
permit 33
Total Filter Entries: 2
Total AS Path Access List Number: 1
DGS-3627:admin#
create bgp community_list
Purpose
This command is used to create a BGP community list.
Syntax
create bgp community_list [standard | expanded] <list_name 16>
Description
This command is used to create a BGP community list.
Parameters
standard
- Configures a standard named community list.
expanded
- Configures an expanded named community list.
<list_name 16>
- This is the name of the community list that will be created. The string size is
16 bytes.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To create a standard BGP community list:
DGS-3627:admin#
create bgp community_list standard list1
Command: create bgp community_list standard list1
Success.
DGS-3627:admin#
config bgp community_list
Purpose
The command is used to configure the matching rules for a BGP community list.
Syntax
config bgp community_list [standard <list_name 16> [add | delete] {internet | local_as |
no_advertise | no_export | community_set <community_set 80>} [deny | permit] |
expanded <list_name 16> [add | delete] <regexp_str 80> [deny | permit]]
Description
This command is used to configure the matching rule for the community access list.
Page 145 / 757
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
141
config bgp community_list
Multiple rules can be defined for a community list.
Each rule is either in the permit form or in the deny form.
Each rule in the standard community list contains one community.
A community string, which contains multiple communities, can be defined for a rule.
A Route can be associated with a community string. To match a rule, two community strings
must exactly match.
The built-in community strings including internet, local_as, no_advertise, and no_export.
The user-defined community is 4-bytes long, with the leading two bytes representing the AS
number and the trailing two bytes representing a user defined number.
BGP community attributes exchanged between BGP peers are controlled by the neighbor
send-community command.
The community string associated with routes can be controlled by the route map. By default,
the community string “internet” will be sent. If the route map sets a community string, this
community string will be added to the existing community string associated with the route.
If permit rules exist in an access list, then routes with community that does not match any
rule in the list will be denied.
If there are no rules or only deny rules configured for the community list, all routes will be
denied.
Parameters
standard
- Configures a standard community list.
expanded
- Configures an expanded community list.
<list_name 16>
- Name of community list to be configured.
deny
- Denies the routes if the rule is matched.
permit
- Permits the routes if the rule is matched.
add
- Adds a rule to the community list.
delete
- Deletes a rule from the community list.
internet
- Routes with this community will be sent to all peers either internal or external.
local_as
- Routes with this community will be sent to peers in the same AS, but will not be
sent to peers in another sub AS in the same confederation and to the external peers.
no_advertise
- Routes with this community will not be advertised to any peer either internal or
external.
no_export
- Routes with this community will be sent to peers in the same AS or in other sub
Autonomous Systems within a confederation, but will not be sent to an external BGP (eBGP)
peer.
<community_set>
- A community is 4 bytes long, including the 2 bytes’ for the Autonomous
System’s number and 2 bytes for the network number This value is configured with two 2-
byte numbers separated by a colon. The valid range of both numbers is from 1 to 65535.
A community set can be formed by multiple communities, separated by a comma.
An example of a community string is 200:1024, 300:1025,400:1026
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To create a standard community list and configure permit routes from the network 10 in the Autonomous System
50000:10

Rate

4.5 / 5 based on 2 votes.

Popular D-Link Models

Famous Router IPs
Famous Router Companies
Bookmark Our Site

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

Share
Top