Guidelines for Configuring Policy-based Routing

Review the guidelines before configuring any component of policy-based routing.

• You can configure policy-based route maps only on Layer 3 interfaces. Configurations on non-Layer 3 interfaces are rejected.
• You cannot delete an active route map or delete an ACL from an active route map. Attempts to delete either are rejected, resulting in an error and an error log.
• The set commands are available only for a “permit” stanza. The CLI does not allow the use of a set command in a policy-based routing “deny” stanza.
• A stanza can contain only one ACL.
• A stanza can contain either IPv4 addresses or IPv6 addresses in its match and set statements. You cannot combine IPv4 and IPv6 addresses in a stanza.
• A stanza that contains the match ip address acl command must use an IPv4 address in its set ip next-hop command.
• A stanza that contains the match ipv6 address acl command must use an IPv6 address in its set ipv6 next-hop command.
• A policy-based routing route map can contain both IPv4 and IPv6 stanzas. In such a situation, only the IPv4 stanzas are used when the route-map is enabled on an IPv4 interface. Similarly, only the IPv6 stanzas are used when the route-map is enabled on an IPv6 interface.
• Stanza sequence numbers are in the range of 1 through 1024.
• All qualifier-related limitations on ACLs apply to policy-based routing, which uses the same set of qualifiers.
• Policy-based routing does not support the set ip dscp command.