[Contents] [Prev] [Next] [Index] [Report an Error]

Negating Match Clauses

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. In some earlier releases, any value specified with a no match command was ignored, and the entire match entry was deleted. This change applies to all match commands configured in a route map.

For example, consider the following match entry to 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

In earlier releases, issuing a command like the following to remove a community (see Community Lists) not specified in the entry deleted the whole entry, but now nothing happens:



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

If you instead issue the following commands, the specified value is deleted:



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

Issue either of the following commands to delete the entire match community entry:



host1(config-route-map)#no match community  

host1(config-route-map)#no match community
corporate5 dade2

[Contents] [Prev] [Next] [Index] [Report an Error]