Hide Navigation Pane
Show Navigation Pane
Download
SHA1
Negating Match Clauses on a Route Map
If you specify a value when you negate a match command configured in a route map, only that value for the match entry is deleted. The routing software deletes the entire match entry only if the entry contains no other values.
For example, consider the following community lists matched to the route map miami:
host1(config)#ip community-list corporate5
permit 32 463 21 host1(config)#ip community-list dade2 permit
41 53 22 host1(config)#route-map miami permit 1 host1(config-route-map)#match community corporate5
dade2 host1(config-route-map)#exit host1(config)#exit host1#show route-map route-map miami, permit, sequence 10 Match clauses: match community corporate5 dade2
To delete the corresponding matched community list entry from the route map miami:
- Issue the no match community command in Route Map Configuration mode with a specific community list.
host1(config-route-map)#no match community
dade2 host1(config-route-map)#exit host1(config)#exit host1#show route-map route-map miami, permit, sequence 10 Match clauses: match community corporate5
To delete all matched community list entries from the route map miami, issue one of the following commands in Route Map Configuration mode:
- no match community
host1(config-route-map)#no match community
- no match community with community lists
host1(config-route-map)#no match community
corporate5 dade2
If you issue a no match community command with a community list not specified in the entry, then the entry is not affected:
host1(config-route-map)#no match community
southbeach host1(config-route-map)#exit host1(config)#exit host1#show route-map route-map miami, permit, sequence 10 Match clauses: match community corporate5 dade2
