1. Home
    2. /
  2. Manuals
    3. /
  3. D-Link
    4. /
  4. DGS-3612
    5. /
  5. 28
Page 136 / 757 Scroll up to view Page 131 - 135
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
132
DGS-3627:admin#
config bgp neighbor map peer_group Campus unsuppress_map add Profile1
Command: config bgp neighbor map peer_group Campus unsuppress_map add Profile1
Success.
DGS-3627:admin#
config bgp neighbor filter
Purpose
This command is used to configure the BGP neighbor’s filter related setting.
Syntax
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)
Description
The command is used to configure the filter related setting for a BGP neighbor.
filter_list
: If the filter list doesn’t exist, it will permit all. Or if the filter list does exist but has no
filter entry, it means deny any.
prefix_list
: If the prefix list doesn’t exist or the prefix list does exist but has no filter entry
defined, it will permit all.
capability_orf_prefix_list
: The BGP Outbound Route Filter Capability allows one BGP
router to install its configured inbound prefix list filter on to the remote BGP router. This is
used for reducing the amount of unwanted routing updates from the remote peer.
Parameters
<ipaddr>
- Specifies the IP address of the neighbor to be configured.
<peer_group_name>
- Specifies the peer group to be configured.
filter_list
- Specifies the name of an as_path access_list to be applied as a filter. The filtering
can be applied to incoming routes or outgoing routes.
prefix_list
- Specifies the name of a prefix_list to be applied as a filter. The filtering can be
applied to incoming routes or outgoing routes.
in
- Specify to apply inbound traffic.
out
- Specify to apply outbound traffic.
capability_orf_prefix_list
- Used to configure an outbound route filter prefix list capability. It
can be sent with the following values:
receive
- Enables the ORF prefix list capability in the receiving direction. The local
router will install the prefix filter list notified by the remote router.
send
- Enables the ORF prefix list capability in the sending direction. The local router
will notify the remote router for the ORF prefix list capability.
both
- Enables the ORF prefix list capability in both received and send directions.
none
- Disable the ORF prefix list capability in both received and send directions.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To configure the BGP neighbor ingress filter list for the peer group “Campus” to List1:
DGS-3627:admin#
config bgp neighbor filter peer_group Campus filter_list in add List1
Command: config bgp neighbor filter peer_group Campus filter_list in add List1
Success.
DGS-3627:admin#
show bgp peer_group
Purpose
The command is used to show the information of the BGP peer group.
Page 137 / 757
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
133
show bgp peer_group
Syntax
show bgp peer_group {<peer_group_name 16>}
Description
To display the BGP peer group’s information.
Parameters
<peer_group_name>
- The name of the BGP peer group. The length is up to 16 bytes.
This means to display all the BGP peer groups’ information that doesn’t specify the peer
group name.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To show the information of the BGP peer group local1:
Page 138 / 757
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
134
DGS-3627:admin# create bgp neighbor peer_group local1
Command:4#create
bgp neighbor peer_group local1
Success.
DGS-3627:admin# create bgp neighbor 10.2.2.2 remote_as 10
Command:4#create
bgp neighbor 10.2.2.2 remote_as 10
Success.
DGS-3627:admin# config bgp peer_group local1 add 10.2.2.2
Command:4#config bgp peer_group local1 add 10.2.2.2
Success.
DGS-3627:admin# show bgp peer_group local1
Command:4#show bgp peer_group local1
BGP Peer Group :local1
-----------------------------------------------------------------------
Description
:
Session State
: Enabled
Session Activity
: Enabled
Members
: 10.2.2.2
Remote AS
: Not Set
Advertisement Interval
: 30 seconds
Keepalive Interval
: 60 seconds.
Holdtime Interval
: 180 seconds.
AS Origination Interval
: 15 seconds
Connect Retry Interval
: 120 seconds
EBGP Multihop
: 1
Weight
: 0
Update Source
: ipif1
Next Hop Self
: Disabled
Route Reflector Client
: Disabled
Send Community
: None
Remove Private As
: Disabled
AllowAS In
: Disabled
Soft Reconfiguration Inbound
:Disabled
Unsuppressed Map
: usmap1
Default Originate
: Disabled
Incoming Update Prefix List
: prelist1
Incoming Update Filter List
: ASlist1
Route Map for outgoing Routes : routemap1
Outbound Route Filter (ORF) type (64) Prefix-list:
Send Mode
: Enabled
Receive Mode
: Disabled
Prefix Max Count
: 12000
Prefix Warning Threshold
: 75
Prefix Warning Only
: Disabled
DGS-3627:admin#
config bgp route_reflector cluster_id
Purpose
This command is used to configure the BGP process’s global attribute.
Syntax
config bgp route_reflector cluster_id <ipaddr>
Page 139 / 757
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
135
config bgp route_reflector cluster_id
Description
The route reflector and its clients together form a cluster. When a single route reflector is
deployed in a cluster, the cluster is identified by the router ID of the route reflector.
When the cluster ID is 0.0.0.0, the cluster is identified by the router ID. Otherwise, the cluster
is identified by the cluster ID.
The BGP cluster_id command is used to assign a cluster ID to a route reflector when the
cluster has one or more route reflectors. Multiple route reflectors are deployed in a cluster to
increase redundancy and to avoid a single point of failure. When multiple route reflectors are
configured in a cluster, they must be configured with the same cluster ID. This allows all route
reflectors in the cluster to recognize updates from peers in the same cluster and reduces the
number of updates that needs to be stored in BGP routing tables.
This command is only required for the reflector and not the client.
Parameters
<ipaddr>
- Specifies the IP address of the cluster ID. Setting the cluster ID to 0.0.0.0 will
remove specifications of the cluster ID. The default value is 0.0.0.0.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To configure the cluster ID:
DGS-3627:admin#
config bgp route_reflector cluster_id 10.100.200.1
Command: config bgp route_reflector cluster_id 10.100.200.1
Success.
DGS-3627:admin#
config bgp client_to_client_reflection
Purpose
This command is used to configure the BGP client to the client reflection setting.
Syntax
config bgp client_to_client_reflection [enable | disable]
Description
The command is only required for the reflector.
If the reflection is disabled, then the router will not reflect routes from the route reflect client to
other route reflect clients, but it will still send routes received from a non-reflecting client to a
reflecting client.
Parameters
enable
- The reflector will operate in reflector mode.
disable
- The reflector will operate in non-reflector mode.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To disable the client to client reflection:
DGS-3627:admin#
config bgp client_to_client_reflection disable
Command: config bgp client_to_client_reflection disable
Success.
DGS-3627:admin#
config bgp confederation identifier
Purpose
This command is used to configure the BGP confederation.
Page 140 / 757
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
136
config bgp confederation identifier
Syntax
config bgp confederation identifier <as_number 0-65535>
Description
A confederation, which is represented by an AS, is a group of the sub AS.
A confederation can be used to reduce the internal BGP (iBGP) mesh by dividing a large
single AS into multihop sub AS. External peers interact with the confederation as if it is a
single AS.
Each sub AS is fully meshed within itself and it has connections to other sub ASs within the
confederation. The next hop, Multi Exit Discriminator (MED), and local preference information
is preserved throughout the confederation, allowing users to retain a single Interior Gateway
Protocol (IGP) for all the autonomous systems.
Parameters
<as_number>
- as_number: 0-65535, Autonomous System numbers which we use to specify
a BGP confederation.
If it is set to zero, the BGP confederation number is deleted. By default, this setting is zero.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To create a confederation in which the AS number is 20:
DGS-3627:admin#
config bgp confederation identifier 20
Command: config bgp confederation identifier 20
Success.
DGS-3627:admin#
config bgp confederation peers
Purpose
This command is used to add or delete BGP confederation peers.
Syntax
config bgp confederation peers [add | delete] <aspath_list>
Description
The command is used to configure multiple adjacent Autonomous Systems in a
confederation. The Autonomous Systems specified in this command are visible internally to
the confederation. Each Autonomous System is fully meshed within itself or configures route
reflector.
Parameters
<aspath_list>
- Can be one or multiple AS number partitions, each separated by a comma.
AS number: 1-65535, Autonomous System numbers for BGP peers that will belong to the
confederation.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To add two confederation peers in which the AS numbers are 50000 and 50001:
DGS-3627:admin#
config bgp confederation peers add 50000, 50001
Command: config bgp confederation peers add 50000, 50001
Success.
DGS-3627:admin#

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