Access Control Lists (ACLs) | 131
Create a route map
Route maps, ACLs, and prefix lists are similar in composition because all three contain filters, but route
map filters are 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 the ROUTE-MAP mode, use the following command in the
CONFIGURATION mode:
The default action is permit and the default sequence number starts at 10. When the keyword
deny is used
in configuring a route map, routes that meet the match filters are not redistributed.
To view the configuration, use the
show config command in the ROUTE-MAP mode as shown in the
example below.
FTOS(config-route-map)#show config
!
route-map dilling permit 10
FTOS(config-route-map)#
You can create multiple instances of this route map by using the sequence number option to place the route
maps in the correct order. FTOS processes the route maps with the lowest sequence number first. When a
configured route map is applied to a command, like
redistribute, traffic passes through all instances of that
route map until a match is found. The following text shows an example with two instances of a route map.
FTOS#show route-map
route-map zakho, permit, sequence 10
Match clauses:
Set clauses:
route-map zakho, permit, sequence 20
Match clauses:
interface GigabitEthernet 0/1
Set clauses:
tag 35
level stub-area
FTOS#
To delete all instances of that route map, use the no route-map map-name command. To delete just one
instance, add the sequence number to the command syntax as shown in the following example.
FTOS(conf)#no route-map zakho 10
FTOS(conf)#end
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.
To Next Page
Loading...
