H3C S5810 Series, Руководство по эксплуатации

Страница: 370 / 820

2-5
If both a QoS policy referencing CAR and the qos car command are configured on an interface, the
QoS policy takes effect.
To ensure that a policy can be applied successfully, follow these guidelines when configuring a traffic
behavior:
z
Do not configure the redirect to CPU, redirect to interface, and redirect to next hop in the same
traffic behavior, because they are conflicting.
z
Do not configure the filter deny action or an aggregation CAR action with the accounting action in
the same traffic behavior, because they are conflicting.
Defining a Policy
A policy defines the mapping between a class and a traffic behavior.
In a policy, multiple class-to-traffic-behavior mappings can be configured, and these mappings are
executed according to the order configured.
Follow these steps to define a policy:
To do… Use the command… Remarks
Enter system view system-view —
Create a policy and enter policy
view
qos policy policy-name Required
Specify the traffic behavior for a
class in the policy classifier tcl-name behavior
behavior-name
Required
Display the specified class and
its associated traffic behavior in
the QoS policy
display qos policy
user-defined [ policy-name
[ classifier tcl-name ] ]
Optional
Available in any view
The ACL referenced by a QoS policy is used for traffic classification only and therefore the deny and
permit actions in the ACL rules are ignored. How the traffic matching the ACL is handled is decided by
the traffic behavior in the QoS policy.
QoS Policy Configuration Example
Network requirements
Configure a QoS policy test_policy to limit the rate of packets with IP precedence 6 to 100 kbps.