User's Manual

Use Route Maps and Other Filters to Filter and Alter BGP and OSPF Routes | Page 51
OSPF: Configuring Route Maps for Filtering and Modifying OSPF Routes
External route type
The entry will match all routes of either Type 1 External or Ty p e 2 E xt er na l .
To match a route type, use the command:
match external {type-1|type-2}
A prefix, by using a prefix list
The entry will match one or more route prefixes.
For information about creating a prefix list, see "About prefix lists" on page 22.
Once you have made the prefix list, apply it to the match clause of a route map entry by
using the command:
match ip address prefix-list <list-name>
A prefix, by using an ACL
An ACL is an alternative to a prefix list for matching route prefixes.
For information about creating an ACL, see "About ACLs" on page 11.
Once you have made the ACL, apply it to the match clause of a route map entr y by using the
command:
match ip address <acl-number-or-name>
A next hop address
The entry will match the route’s next hop.
You can use either a prefix list or an ACL to specify a next hop address. Once you have made
the prefix list or ACL, apply it to the match clause of a route map entry by using one of the
commands:
match ip next-hop prefix-list <list-name>
match ip next-hop <acl-number-or-name>
Configuring a set clause
If a route matches the match clause, then the action of the route map entry will be applied
to that route. The action might simply be to permit or deny the route, or it might be to
update its parameters by applying one or more set clauses.
Note: When configuring a set clause, make sure you are in route map mode for the same
route map name sequence number as you used for the match clause.

The prompt should look like: awplus(config-route-map)#
A set clause can alter the following parameters on a route.