Administrator Guide

Important Points to Remember
For route-maps with more than one match clause:
Two or more match clauses within the same route-map sequence have the same match
commands (though the values are different), matching a packet against these clauses is a logical
OR operation.
Two or more match clauses within the same route-map sequence have different match
commands, matching a packet against these clauses is a logical AND operation.
If no match is found in a route-map sequence, the process moves to the next route-map sequence until
a match is found, or there are no more sequences.
When a match is found, the packet is forwarded and no more route-map sequences are processed.
If a continue clause is included in the route-map sequence, the next or a specified route-map
sequence is processed after a match is found.
Configuration Task List for Route Maps
Configure route maps in ROUTE-MAP mode and apply the maps in various commands in ROUTER RIP and
ROUTER OSPF modes.
The following list includes the configuration tasks for route maps, as described in the following sections.
Create a route map (mandatory)
Configure route map filters (optional)
Configure a route map for route redistribution (optional)
Configure a route map for route tagging (optional)
Creating a Route Map
Route maps, ACLs, and prefix lists are similar in composition because all three contain filters, but route map
filters do not contain the permit and deny actions found in ACLs and prefix lists.
Route map filters match certain routes and set or specify values.
To create a route map, use the following command.
Create a route map and assign it a unique name. The optional permit and deny keywords are the action
of the route map.
CONFIGURATION mode
route-map map-name [permit | deny] [sequence-number]
The default is permit.
The optional seq keyword allows you to assign a sequence number to the route map instance.
Access Control Lists (ACLs) 148