■ Use to match a community list.
■ Supported for inbound and outbound route maps.
■ Example
host1(config)#route-map nyc1 permit 10
host1(config-route-map)#match community comm5
■ Use the no version to delete the match clause from a route map or a specified
value from the match clause.
■ See match community
match distance
■ Use to match any routes that have the specified administrative distance.
■ Example
host1(config)#route-map nyc1 permit 10
host1(config-route-map)#match distance 25
■ Use the no version to delete the match clause from a route map or a specified
value from the match clause.
■ See match distance.
match extcommunity
■ Use to match an extended community list in a route map.
■ You can specify one or more extended community list names in a match clause.
If you specify more than one extended community list, the lists are logical ORed.
■ Example
host1(config)#route-map nyc1 permit 10
host1(config-route-map)#match extcommunity topeka10
■ Use the no version to remove the match clause from a route map or a specified
value from the match clause.
■ See match extcommunity.
match ip address
■ Use to match any route that has a destination network number that is permitted
by an access list, a prefix list, or a prefix tree, or performs policy routing on
packets.
■ Example
host1(config)#route-map nyc1 permit 10
host1(config-route-map)#match ip address prefix-tree boston
■ Use the no version to delete the match clause from a route map or a specified
value from the match clause.
■ See match ip address.
Configuring BGP Routing Policy ■ 73
Chapter 1: Configuring BGP Routing
To Next Page
Loading...