Defining a route map, Customizing a route map – Cisco ASA 5505 User Manual

Page 460

Advertising
background image

23-4

Cisco ASA 5500 Series Configuration Guide using the CLI

Chapter 23 Defining Route Maps

Defining a Route Map

Defining a Route Map

You must define a route map when specifying which of the routes from the specified routing protocol
are allowed to be redistributed into the target routing process.

To define a route map, enter the following command:

Customizing a Route Map

This section describes how to customize the route map and includes the following topics:

Defining a Route to Match a Specific Destination Address, page 23-4

Configuring the Metric Values for a Route Action, page 23-5

Defining a Route to Match a Specific Destination Address

To define a route to match a specified destination address, perform the following steps:

Detailed Steps

Command

Purpose

route-map

name {permit | deny}

[sequence_number]

Example:

hostname(config)# route-map name {permit}

[12]

Creates the route map entry. Enters route-map configuration mode.

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.

Command

Purpose

Step 1

route-map

name {permit | deny}

[sequence_number]

Example:

hostname(config)# route-map name {permit}

[12]

Creates the route map entry. Enters route-map configuration
mode.

Route map entries are read in order. You can identify the order
using the sequence_number option, or the ASA uses the order in
which you add route map entries.

Step 2

Enter one of the following match commands to match routes to a specified destination address:

match

ip address acl_id [acl_id] [...]

[prefix-list]

Example:

hostname(config-route-map)# match ip

address acl_id [acl_id] [...]

[prefix-list]

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.

Advertising