13-41 config bgp community_list
Description
This command is used to configure the matching rule for the community access list. Mutliple 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 exact 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 is
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.
Format
config bgp community_list [standard <list_name 16> [add | delete] {internet | local_as |
no_advertise | no_export | community_set <community_set 80>}(1) [deny | permit] |
expanded <list_name 16> [add | delete] <regexp_str 80> [deny | permit]]
Parameters