1. Home
    2. /
  2. Manuals
    3. /
  3. D-Link
    4. /
  4. DGS-3612
    5. /
  5. 24
Page 116 / 757 Scroll up to view Page 111 - 115
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
112
config bgp neighbor general
[<ipaddr> | peer_group <peer_group_name 16>] { ebgp_multihop <value 1-255>
| weight [<value 0-65535>| default ] | update_source [add | delete] ipif
<ipif_name 12>| send_community [standard | none] | next_hop_self [enable |
disable] | soft_reconfiguration_inbound [enable | disable] | remove_private_as
[enable | disable] | allowas_in [enable {<value 1-10>}| disable] | default_originate
[enable {route_map <map_name 16>} | disable] }(1)
config bgp neighbor timer
[<ipaddr> | peer_group <peer_group_name 16>] { advertisement_interval [<sec
0-600> | default ] | [ keepalive <sec 0-65535> holdtime <sec 0-65535>
|default_keepalive_holdtime ] | as_origination_interval [<sec 1-600> | default] |
connect [<sec 1-65535> | default ]}(1)
config bgp neighbor
route_reflector_client
[<ipaddr> | peer_group <peer_group_name 16>] state [enable | disable]
config bgp neighbor map
[<ipaddr> | peer_group <peer_group_name 16>] { unsuppress_map [add |
delete] <map_name 16> | route_map [ in | out] [add | delete ] <map_name
16>}(1)
config bgp neighbor filter
[<ipaddr> | peer_group <peer_group_name 16>] { filter_list [ in | out] [add |
delete] <list_name 16> | prefix_list [in | out] [add | delete] <list_name 16> |
capability_orf_prefix_list [receive | send | both | none]}(1)
show bgp peer_group
{<peer_group_name 16>}
config bgp route_reflector cluster_id
<ipaddr>
config bgp client_to_client_reflection
[enable | disable]
config bgp confederation identifier
<as_number 0-65535>
config bgp confederation peers
[add | delete] <aspath_list>
clear bgp
[all | ipaddr <ipaddr> | as <as_number 1-65535> | peer_group
<peer_group_name 16> | external ] {soft {[ in { prefix_filter} | out ]}}
clear bgp dampening
{[<ipaddr> | <network_address>]}
create bgp as_path access_list
<list_name 16>
config bgp as_path access_list
<list_name 16> [add | delete] <regexp_str 80> [deny | permit]
delete bgp as_path access_list
[ list_name <list_name 16> | all]
show bgp as_path access_list
{<list_name 16>}
create bgp community_list
[standard | expanded] <list_name 16>
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]]
delete bgp community_list
[list_name <list_name 16> | all]
show bgp community_list
{<list_name 16>}
show bgp route
{[ regexp <desc 80> | inconsistent_as | cidr_only | filter_list <list_name 16> |
route_map <map_name 16> | community {community_set <community_set 80>
| local_as | no_advertise | no_export | internet}{exact_match} | community_list
<list_name 16> {exact_match} | ipaddress <ipaddr> | network
<network_address> {longer_prefixes} | prefix_list <list_name 16>]}
show bgp neighbors
{<ipaddr> {[ advertised_routes | received_routes | routes| received_prefix_filter|
statistics ]}}
show bgp dampened_routes
show bgp flap_statistics
show bgp
{summary}
show bgp reflection
Page 117 / 757
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
113
show bgp confederation
config bgp trap
[peer_established | peer_idle | all ] [enable | disable]
show bgp trap_state
config bgp scan_timer
[<sec 5-60> | default]
config bgp
aggregate_next_hop_check
[enable | disable]
config bgp fast_external_fallover
[enable | disable]
config bgp neighbor maximum_prefix
[<ipaddr> | peer_group <peer_group_name 16>] <value 1-12000> {<value 1-
100>} {warning_only}
clear bgp flap_statistics
{[<ipaddr> | <network_address>]}
Each command is listed, in detail, in the following sections.
enable bgp
Purpose
This command is used to enable the BGP protocol.
Syntax
enable bgp
Description
By enabling the BGP protocol, all the previous configurations will be applied to the protocol
kernel and start. By default, BGP is disabled.
Parameters
None.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To enable BGP protocol:
DGS-3627:admin# enable bgp
Command: enable bgp
Success.
DGS-3627:admin#
disable bgp
Purpose
This command is used to disable the BGP protocol.
Syntax
disable bgp
Description
By disabling the BGP protocol, all peers will be disconnected and dynamic routes will be
deleted. All the static configurations however will be reserved. If BGP is enabled again, the
previous configurations can be re-applied.
Parameters
None.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To disable BGP protocol:
Page 118 / 757
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
114
DGS-3627:admin# disable bgp
Command: disable bgp
Success.
DGS-3627:admin#
create bgp
Purpose
This command is used to create a BGP process. It’s AS number must be set.
Syntax
create bgp <as_number 1-65535>
Description
When the BGP protocol starts, it must belong to a single AS. The user must set the AS
number before configuring any of the other attributes.
Parameters
<as_number>
- Specifies the BGP AS number. The valid value is from 1 to 65535.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To create a BGP process:
DGS-3627:admin# create bgp 100
Command: create bgp 100
Success.
DGS-3627:admin#
delete bgp
Purpose
This command is used to delete the BGP process.
Syntax
delete bgp <as_number 1-65535>
Description
This command is used to delete the BGP process. The AS number must be specified. When
the BGP process is deleted, all peer and route information from BGP will be deleted. Route
entries redistributed from BGP must also be canceled.
Parameters
<as_number>
- Specifies the BGP AS number. The valid value is from 1 to 65535.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To delete a BGP process:
DGS-3627:admin# delete bgp 100
Command: delete bgp 100
Success.
DGS-3627:admin#
config bgp router_id
Purpose
This command is used to configure the BGP process’s router ID
Syntax
config bgp router_id <ipaddr>
Page 119 / 757
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
115
config bgp router_id
Description
The address of a loopback interface is preferred to an IP address on a physical interface
because the loopback interface is more effective than a fixed interface as an identifier
because there is no physical link to go down.
The user must specify a unique router ID within the network.
This command will reset all active BGP peering sessions.
When a router ID is not configured, the router ID is selected by the following rules:
If a loopback interface is configured, the router ID is set to the IP address of the loopback.
If multiple loopback interfaces are configured, the loopback with the highest IP address is
used.
If no loopback interface is configured, the router ID is set to the highest IP address on a
physical interface.
Note:
One newly created interface whose address may be preferred to be the router ID
according to the rules above, but, it will not be chosen to be router ID immediately. Only
when the router ID is set to zero or when recreating a BGP instance, the new interface may
be selected as the BGP router ID.
Parameters
<ipaddr>
- An ID to identify a BGP router. If it is set to zero the router ID will be automatically
determined. The default value is the highest IP address on a physical interface.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To configure the BGP process’s router ID:
DGS-3627:admin#
config bgp router_id 10.10.10.1
Command: config bgp router_id 10.10.10.1
Success
DGS-3627:admin#
config bgp synchronization
Purpose
This command is used to configure the BGP synchronization ability.
Syntax
config bgp synchronization [enable | disable]
Description
Usually, a BGP speaker does not advertise a route to an external neighbor unless that route
is local or exists in the IGP. By default, synchronization between BGP and the IGP is turned
off to allow the BGP to advertise a network route without waiting for route validation from the
IGP. This feature allows routers and access servers within an Autonomous System to have
the route before BGP makes it available to other autonomous systems.
Parameters
enable
- Specifies to enable synchronization..
disable
- Specifies to disable synchronization. By default, this setting is disabled.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To enable the BGP process’ synchronization ability:
DGS-3627:admin#
config bgp synchronization enable
Command: config bgp synchronization enable
Success
DGS-3627:admin#
Page 120 / 757
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
116
config bgp enforce_first_as
Purpose
This command is used to enforce the neighbor’s AS as the first AS in the AS list.
Syntax
config bgp enforce_first_as [enable | disable]
Description
This command is used to enforce the neighbor’s AS as the first AS in the AS list.
When the setting is enabled, any updates received from an external neighbor, that does not
have the neighbor’s configured Autonomous System (AS) at the beginning of the AS_PATH
in the received update, will be denied. Enabling this feature adds to the security of the BGP
network by not allowing traffic from unauthorized systems.
Parameters
enforce_first_as
- Enable or disable the enforce_first_as setting. The default setting is
disabled.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To enable the BGP process’s enforce_first_as ability:
DGS-3627:admin#
config bgp enforce_first_as enable
Command: config bgp enforce_first_as enable
Success
DGS-3627:admin#
create bgp aggregate_address
Purpose
This command is used to create an aggregate entry in the Border Gateway Protocol (BGP)
database.
Syntax
create bgp aggregate_address <network_address> {summary_only | as_set}
Description
Using the aggregate_address command with no keywords will create an aggregate entry in
the BGP routing table, if any more specific BGP routes are available that fall within the
specified range. The aggregate route will be advertised as coming from your Autonomous
System and will have the atomic aggregate attribute set to indicate that information might be
missing. That is, the original AS path associated with more specific routes will be lost. The
atomic aggregate attribute is set unless you specify the as_set keyword.
Using the as_set keyword will create an aggregate entry, but the path advertised for this
route will include an AS set consisting of all ASs that are contained in all paths that are being
summarized. Do not use continually withdrawn and updated as autonomous system path
reachability information for the summarized routes changes.
Using the summary_only keyword will create an aggregate route but suppresses
advertisements of more specific routes to all neighbors. If you want to suppress only
advertisements to certain neighbors, you may use the neighbor prefix_list command.
Parameters
<network_address>
- The IP network address aggregated.
as_set
- Generates Autonomous System set path information. The default setting is not set.
summary_only
- More specific routes will not be advertised. The default setting is not set.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To create an aggregate route of which the network address is 10.0.0.0/8, suppress more-specific routes:

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