Configuration considerations and guidelines for PBR

• PBR route maps may only be applied to Layer 3 (L3) interfaces. Application of a route map to a non-L3 interface results in the configuration being rejected.
• PBR is not supported on any interface where the next-hop is configured to be a GRE Tunnel.
• Deletion of a route map or deletion of an ACL used in the route map “match” is not allowed when the route map is actively bound to an interface. Attempts to delete an active route map or associated ACL is rejected, and an error and log are generated.
• The “set” commands are only available within the context of a “permit” stanza.
• Consider the permit and deny keywords as allowing the specified match content as either being permitted to or denied from using the defined “set criteria” of the route map. The permit and deny keywords do not correlate to the forwarding action of forward and drop as they do in the ACL application.