Multiple Values in a Route Map Match Entry Overview
You can specify more than one value in each match entry of a route map by using any of the following match commands:
- match as-path
- match community
- match distance
- match extcommunity-list
- match ip address
- match ip next-hop
- match ipv6 address
- match ipv6 next-hop
- match ipv6 route-source
- match level
- match metric
- match policy-list
- match route-type
- match tag
A clause with multiple values matches a route that contains any of the values; that is, the multiple values are logically joined by an OR operator.
host1(config-route-map)#match ip address lisbon
madrid host1(config-route-map)#match as-path 10 20
30
You can also issue successive match commands to add new values to a route map entry for any of the preceding commands.
host1(config-route-map)#match ip address boston host1(config-route-map)#match ip address newyork
This method is equivalent to issuing the following single command:
host1(config-route-map)#match ip address boston
newyork
You cannot specify multiple values for the match metric-type command because it accepts only two values that are mutually exclusive. Specifying both values has the same effect as not specifying a metric type at all; specifying the same value more than once has no meaning.
Related Documentation
- Understanding Route Map Match and Set Clauses
- Negating Match Clauses on a Route Map
- Configuring Match Clauses and Values for a Route Map
- Monitoring Route Map Details
- match as-path
- match community
- match distance
- match extcommunity
- match ip address
- match ip next-hop
- match ipv6 address
- match ipv6 next-hop
- match ipv6 route-source
- match level
- match metric
- match policy-list
- match route-type
- match tag