Install guide

2-16 Release Note
Software Version 2.7.5
C613-10454-00 REV A
Creating Route Maps for OSPF
A route map consists of multiple entries, which are in effect individual filters.
Each entry specifies both what it matches on, in a match clause, and what is
done to matching traffic, in the entry’s action and any set clauses it has.
When the router or switch applies a route map to routes for OSPF:
1. It checks the entries in order, starting with the lowest numbered entry, until
it finds a match.
2. It then takes the action specified by that entry’s action parameter. If the
action is exclude, it filters out that route. If the action is include, it filters in
that route.
3. If the action is include, it modifies the route characteristics as specified by
the entry’s set clauses if there are any.
4. It then stops processing that route; it does not check the remaining entries
in the route map.
Every route map ends with an implicit entry that matches all routes with an
action of include. This ensures that if no entries in a route map generate a
match, the route is included without modification.
The rest of this section describes:
■ How to create a route map
■ How to configure an entry with a match clause
■ How to configure an entry with a set clause
How to create a route map
You do not have to create a route map as a separate step—adding the first entry
automatically creates it.
How to configure an entry with a match clause
The match clause for a route map entry determines which routes match the
entry. Each entry can only match on one characteristic. Available characteristics
you can use with OSPF are:
■ interface
■ metric
■ next hop
■ prefix list
■ route source
■ route type
■ tag
Matching on
interface
An entry that matches on interface lets you select or discard all routes whose
next hop is reached out that interface. To do this, use the command:
add ip routemap=routemap entry=1..4294967295
[action={include|exclude}] match interface=interface