Cisco Systems ASA5515K9, ASA 5500 Configuring the Metric Values for a Route Action

23-5
Cisco ASA 5500 Series Configuration Guide using the CLI
Chapter23 Defining Route Maps
Customizing a Route Map
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.
To configure the metric value for a route action, perform the following steps:
Detailed Steps
match metric metric_value
Example:
hostname(config-route-map)# match metric
200
Matches any routes that have a specified metric.
The metric_value can range from 0 to 4294967295.
match ip next-hop acl_id [acl_id] [...]
Example:
hostname(config-route-map)# match ip
next-hop acl_id [acl_id] [...]
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.
match interface if_name
Example:
hostname(config-route-map)# match
interface if_name
Matches any routes with the specified next hop interface.
If you specify more than one interface, then the route can match
either interface.
match ip route-source acl_id [acl_id]
[...]
Example:
hostname(config-route-map)# match ip
route-source acl_id [acl_id] [...]
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.
match route-type {internal | external
[type-1 | type-2]}
Example:
hostname(config-route-map)# match
route-type internal type-1
Matches the route type.
Command Purpose
Command Purpose
Step1 route-map name {permit | deny}
[sequence_number]
Example:
hostname(config)# route-map name {permit}
[12]
Creates the route map entry.
Route map entries are read in order. You can identify the order
using the sequence_number argument, or the ASA uses the order
in which you add route map entries.
Step2 To set a metric for the route map, enter one or more of the following set commands: