Cisco ASA Series Cli Configuration Manual page 629

Chapter 1 Defining Route Maps
Command
match ip address acl_id [acl_id] [...]
[prefix-list]
Example:
hostname(config-route-map)# match ip
address acl_id [acl_id] [...]
match metric metric_value
Example:
hostname(config-route-map)# match metric
200
match ip next-hop acl_id [acl_id] [...]
Example:
hostname(config-route-map)# match ip
next-hop acl_id [acl_id] [...]
match interface if_name
Example:
hostname(config-route-map)# match
interface if_name
match ip route-source acl_id [acl_id]
[...]
Example:
hostname(config-route-map)# match ip
route-source acl_id [acl_id] [...]
match route-type {internal | external
[type-1 | type-2]}
Example:
hostname(config-route-map)# match
route-type internal type-1
Configuring the Metric Values for a Route Action
If a route matches the match commands, then the following set commands determine the action to
perform on the route before redistributing it.
Purpose
Matches any routes that have a destination network that matches
a standard ACL or prefix list.
If you specify more than one ACL, then the route can match any
of the ACLs.
Matches any routes that have a specified metric.
The metric_value can range from 0 to 4294967295.
Matches any routes that have a next hop router address that
matches a standard ACL.
If you specify more than one ACL, then the route can match any
of the ACLs.
Matches any routes with the specified next hop interface.
If you specify more than one interface, then the route can match
either interface.
Matches any routes that have been advertised by routers that
match a standard ACL.
If you specify more than one ACL, then the route can match any
of the ACLs.
Matches the route type.
Cisco ASA Series CLI Configuration Guide
Customizing a Route Map
1-5