Filter
Top Products
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