Restrictions on the Policy-Based Routing
-
ACL and PBR are not supported together on the same SVI. Only one of the access-group (permit or deny access list) or IP policy route-map can be configured on the same SVI.
-
IPv6 PBR is not supported.
-
FRR is not supported with PBR.
-
PBR is supported only on the SVI interfaces. It is not supported on Physical ports, EFPs, and EVCs.
-
Single route-map entry is supported for each ip policy route-map command usage instances. Multiple route-map sequence entries for the same route-map are not supported (route-map with multiple sequence of route-map-entries).
-
Only the access list is supported as match clause. Prefix list and other match clauses are not supported.
-
Only one ACL is supported for route-map entry match statement.
-
Only one match statement is supported for each route-map entry.
-
Only set ip next-hop command is supported for the route-map entry. The set ip next-hop recursive command is not supported. Consequently, the next-hop which is going to be MPLS path is not supported. Other set commands including set ip vrf , set ip precedence etc. are not supported.
-
PBR is applicable for ingress traffic only and is not applicable for locally generated packets.
-
IPv6 traffic filter and IPv4 PBR are not supported together on the same interface.
-
One ACL can be associated to only one SVI interface (either through "IPv4 Policy Route-map" or through "IPv4 Access group") on one device.
-
We recommend a maximum of 50 ACE rules in one access-List for all access-lists being used for PBR (route-map).