Users Guide

Remarks that do not have a corresponding rule are incremented as a rule. These two mechanisms allow remarks to retain their original
position in the list. The following example shows remark 10 corresponding to rule 10 and as such, they have the same number before and
after the command is entered. Remark 4 is incremented as a rule, and all rules have retained their original positions.
Dell(config-ext-nacl)# show config
!
ip access-list extended test
remark 4 XYZ
remark 5 this remark corresponds to permit any host 1.1.1.1
seq 5 permit ip any host 1.1.1.1
remark 9 ABC
remark 10 this remark corresponds to permit ip any host 1.1.1.2
seq 10 permit ip any host 1.1.1.2
seq 15 permit ip any host 1.1.1.3
seq 20 permit ip any host 1.1.1.4
Dell# end
Dell# resequence access-list ipv4 test 2 2
Dell# show running-config acl
!
ip access-list extended test
remark 2 XYZ
remark 4 this remark corresponds to permit any host 1.1.1.1
seq 4 permit ip any host 1.1.1.1
remark 6 this remark has no corresponding rule
remark 8 this remark corresponds to permit ip any host 1.1.1.2
seq 8 permit ip any host 1.1.1.2
seq 10 permit ip any host 1.1.1.3
seq 12 permit ip any host 1.1.1.4
Route Maps
Although route maps are similar to ACLs and prex lists in that they consist of a series of commands that contain a matching criterion and
an action, route maps can modify parameters in matching packets.
ACLs and prex lists can only drop or forward the packet or trac. Route maps process routes for route redistribution. For example, a route
map can be called to lter only specic routes and to add a metric.
Route maps also have an “implicit deny.” Unlike ACLs and prex lists; however, where the packet or trac is dropped, in route maps, if a
route does not match any of the route map conditions, the route is not redistributed.
Implementation Information
The implementation of route maps allows route maps with the no match or no set commands. When there is no match command, all
trac matches the route map and the
set command applies.
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
dierent), matching a packet against these clauses is a logical OR operation.
– Two or more match clauses within the same route-map sequence have dierent 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 specied route-map sequence is processed after a match
is found.
Access Control Lists (ACLs)
137