Table of Contents
Advertisement
ip bgp-community new-format
ip community-list
neighbor send-community
Use to specify that communities must be displayed in AA:NN format, where AA
is a number that identifies the autonomous system and NN is a number that
identifies the community within the autonomous system.
Example
host1(config)#ip bgp-community new-format
Use the no version to restore the default display.
See ip bgp-community new-format.
Use to create a community list for BGP and control access to it.
The list name can be up to 32 characters long.
A route can belong to any number of communities, so a community list can have
many entries comprising many communities.
You can specify one or more community values when you create a community
list. A clause in a route map that includes a list that has more than one value
matches only a route that has all of the values; that is, the multiple values are
logical ANDed.
You can specify community values with a number or a regular expression.
Example
host1(config)#ip community-list 1 permit 100:2 100:3 100:4
host1(config)#route-map marengo permit 10
host1(config-route-map)#match community 1
A route matches this community list only if it belongs to at least all three
communities in community list 1: communities 100:2, 100:3, and 100:4.
Use the no version to remove the specified community list, including all list
entries.
See ip community-list.
Use to specify that a community attribute be sent to a BGP neighbor.
If you specify a BGP peer group by using the peer-group-name argument, all the
members of the peer group inherit the characteristic configured with this
command.
Example
host1:vr1(config-router)#neighbor 192.3.4.5 send-community standard
Use the no version to specify that common attributes not be sent to a BGP
neighbor.
See neighbor send-community.
Chapter 1: Configuring Routing Policy
Community Lists
41
Advertisement
Table of Contents
