CLI Guide

Layer 3 Routing Commands 1522
Command Mode
Route Map Configuration mode
User Guidelines
The IP ACL must be configured before it can be linked to a route-map.
Specifying an unconfigured IP ACL causes an error. Actions present in an IP
ACL configuration are applied along with other actions present in route-map.
When an IP ACL referenced by a route-map is removed or rules are added or
deleted from that ACL, the configuration is rejected.
Actions in the IP ACL configuration are applied with other actions present in
the route-map. If an IP ACL referenced by a route-map is removed or rules
are added or deleted from the ACL, the configuration is rejected.
If a list of IP access lists is specified in this command and a packet matches at
least one of these access list match criteria, the corresponding set of actions in
the route map are applied to the packet. Duplicate IP access list names are
ignored.
It is strongly recommended that access lists used in a route map not be re-
used for normal access list processing. This is because:
• ACLs inherit the priority of the route map. This overrides the priority of
the including access group.
• Route maps do not have a implicit deny all at the end of the list. Instead,
non-matching packets for a permit route map use the routing table.
Example
The example below creates two access lists (R1 and R2) and two route-maps
with IP address match clauses and that associate the route-map to an
interface.
In the example, the ip policy route-map equal-access command is applied to
interface VLAN 11. All packets ingressing VLAN 11 are policy-routed.
Route map sequence 10 in route map equal-access is used to match all
packets sourced from any host in subnet 10.1.0.0. If there is a match, and if
the router has no explicit route for the packet’s destination, it is sent to next-
hop address 192.168.6.6.