Configuration Guidelines for IPv6 PBR

The next hop can be configured as an IPv6 address, a tunnel ID, or as a drop interface. IPv6 ACLs can be configured as match criteria for the packets. An IPv6 policy route map can be applied globally or on an interface. If an IPv6 PBR policy is configured on an interface, it will take precedence over the global-level IPv6 PBR policy configuration.

The ip policy route-map and ipv6 policy route-map commands are independent of each other and can be applied on an interface and globally in any order, individually or simultaneously. Although IPv4 and IPv6 PBR work independently, and route maps can support IPv4 and IPv6 next hops and ACLs, the command used to apply the route map does affect which next hops and ACLs are supported:

• If a route map is applied using the ip policy route-map command, only IPv4 next hops and ACLs will be used and IPv6 next-hops and ACLs will be skipped.
• If a route map is applied using the ipv6 policy route-map command, only IPv6 next hops and ACLs will be used and IPv4 next hops and ACLs will be skipped.

IPv6 PBR follows the same configuration considerations as IPv4 PBR with the following exceptions:

• Each IPv6 PBR route map instance can support up to six IPv6 ACLs.
• IPv6 PBR is supported for the following criteria:
  • VRF support
  • Accounting
  • Stacking or HA
  • SPX