CLI Guide

Layer 3 Routing Commands 1508
User Guidelines
Policy-based routing must be configured on the VLAN interface that receives
the packets, not on the VLAN interface from which the packets are sent.
Packets matching a deny route map are routed using the routing table. Policy
maps with no set clause are ignored.
When a route-map applied on an interface is changed, i.e. new statements are
added to route-map or match or set terms are added/removed from the route-
map statement, or if any route-map that is applied on an interface is removed,
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 ip address <acl>, match mac-list, match length
Valid set conditions are:
set ip next-hop, set ip default next-hop, set ip 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.