Access Control Lists (ACLs) | 93
• 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; 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
You configure route maps in ROUTE-MAP mode and apply them in various commands in ROUTER RIP
and ROUTER OSPF modes.
The following list includes the configuration tasks for route maps:
• 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)
Create 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 and enter ROUTE-MAP mode, follow these steps, starting in CONFIGURATION
mode:
The default action is permit and the default sequence number starts at 10. When you use the keyword
deny
in configuring a route map, routes that meet the match filters are not redistributed.
To view the configuration, use the
show config command in ROUTE-MAP mode (Figure 5-23).
Figure 5-23. Command Example: show config in the ROUTE-MAP Mode
Command Syntax Command Mode Purpose
route-map map-name [permit | deny]
[sequence-number]
CONFIGURATION Create a route map and assign it a unique name.
The optional permit and deny keywords are the
action of the route map. The default is permit.
The optional parameter seq allows you to assign a
sequence number to the route map instance.
FTOS(conf-route-map)#show config
!
route-map dilling permit 10
FTOS(conf-route-map)#
To Next Page
Loading...
