Usage Scenario
The ACL rules are generally used for redirection in the traffic behavior. However, the specification of ACL rules is limited. When ACL rules defined for MF classification do not meet the live network requirements, you can run the traffic policy command to redirect the traffic behavior to a configured traffic policy to implement cascaded MF classification.
Follow-up Procedure
Associate the traffic classifier and traffic behavior in a traffic policy and apply the traffic policy to an interface.
Precautions
When a cascaded traffic policy generates a traffic policy instance of two-levels:
- If the action in the traffic behavior in the parent traffic policy is the same as that in the traffic behavior in the child traffic policy, the action in the traffic behavior in the child traffic policy is implemented.
The same action configuration refers to the same action type. Even if the parameters are different, the actions of the same type are considered the same action configuration. In this case, the action in the traffic behavior in the child traffic policy is implemented.
- If the action in the traffic behavior in the parent traffic policy is different from that in the traffic behavior in the child traffic policy, the actions in the traffic behaviors are implemented separately.
- When the traffic behaviors for the parent and child policies are both service-class, service-class in the parent policy preferentially takes effect. However, if service-class in the parent policy carries no-remark, service-class in the child policy preferentially takes effect.
One traffic policy (parent policy) can cascade over multiple traffic policies (child policies), and one traffic policy (child policy) can be cascaded by multiple traffic policies (parent policies). However, the traffic policies cannot be circulated or nested.
After the cascading relationship is set up, the shared attribute of the cascading policy cannot be changed.
- Cascading a traffic policy over another will cause the device forwarding performance to deteriorate.
- When the traffic on an interface matches the cascaded traffic policy: The forwarding behavior and cascading a traffic policy are mutually exclusive. If the traffic behaviors in the two traffic policies are different, they can be individually implemented. If the traffic behaviors in the two traffic policies are the same, the specific behavior configuration in the cascaded traffic policy takes effect.
- On an interface, only one traffic policy can be applied to outgoing or incoming packets. If the traffic policy cascades over another traffic policy and is applied to an interface, both traffic policies take effect on the direction-specific interface.
- The parameters specified for a traffic policy, such as inbound, outbound, link-layer, mpls-layer, and all-layer, are inherited by the cascaded traffic policy.
- This command is mutually exclusive with the multicast-nat bind instance, nat bind instance, nat64 bind instance, ds-lite bind instance and service-chain bind instance commands.
- In multicast VPN and NG MVPN scenarios, the traffic policy function is not supported for L3VPN.