Users Guide

Layer 3 Routing Commands 1868
the entire sequence of route-maps needs to be removed from the interface
and added back again in order to have the changed route-map configuration
be effective.
If the administrator removes match or set terms in a route-map
intermittently, the counters corresponding to the removed match term are
reset to zero. A route-map statement must contain eligible match/set
conditions for policy based routing in order to be applied to hardware.
Valid match conditions are:
match ipv4 address <acl>, match mac-list, match length
Valid set conditions are:
set ipv6 next-hop, set ipv6 default next-hop, set ipv6 precedence
A route-map statement must contain at least one of the match and one of the
set conditions specified above in order it to be eligible to be applied to
hardware. If not, the route-map is not applied to hardware. An ACL
referenced in a route-map may not be edited. Instead, create a new ACL with
the desired changes and update the route-map with the edited ACL.
Route-maps and DiffServ cannot operate on the same interface due to
allocation of conflicting resources. An error is thrown to user if when
configuring a route-map on an interface on which DiffServ has been
previously configured.
When a route map is configured on a VLAN interface and a DiffServ policy is
applied on any individual member port of the same VLAN interface, the port
policy (DiffServ) takes priority over the VLAN (route map) policy.
Command History
Command introduced in version 6.6 firmware.
Example
Considering equal-access as a previously configured route-map, the following
sequence is an example of how it is applied to an interface.
console(config)#interface gi1/0/1
console(config-if-Gi1/0/1)#ip policy route-map equal-access