Use this command to identify a route map to use for policy-based IPv6 routing on an interface.
| Format | ipv6 policy route-map route-map-name |
| Mode | Interface Config |
| Parameter | Description |
|---|---|
| route-map-name | The name of the route map to use for policy routing. It must match a map tag specified by a route- map command. If user tries to apply a route-map name that is not configured/created yet, an error is shown to user. |
Usage Guidelines
A route-map statement should contain eligible match/set conditions for policy-based routing in order to be applied to hardware.
- Valid match conditions: match ipv6 address acl, match mac-list, match length
- Valid set conditions: set ipv6 next-hop, set ipv6 default next-hop, set ipv6 precedence
A route-map statement should contain at least one match condition and one set condition as specified above for it to be eligible to be applied to hardware. If not, the route-map is not applied to hardware.
Route-map and DiffServ cannot work on the same interface.
When a route-map is applied on a VLAN interface and a DiffServ policy is applied on a member port of the same VLAN interface, the port policy has priority over the VLAN policy.
The same route-map cannot be applied using both ip policy and ipv6 policy commands on an interface.
Example:
(Routing) (Interface vlan 40)#show ip policy Interface Route-Map ------------ ----------------------------------------- 3/4 rm6 (Routing) (Interface vlan 40)#ipv6 policy route-map rm6 Route-map is already in use for IPv6 based policy routing
When a route-map has both IPv4 and IPv6 statements provisioned and the user applies the route-map using the ipv6 policy command, then the IPv4 statements in the route-map will not take effect. A message will be displayed to the user to indicate this.
Example:
(Routing) (Interface vlan 40)#ipv6 policy route-map rm4
IPv4 statements in this route-map will not be applied using IPv6 Policy Based Routing
