H3C Technologies H3C WX6000 Series Access Controllers - Manual (Page 550)

46-21
2) If an ACL is referenced by a QoS policy for defining traffic classification rules, the operation of the
QoS policy varies by interface: The definition of software/hardware interface varies with device
models. The specific process is as follows:
If the QoS policy is applied to a software interface and the referenced ACL rule is a deny clause,
the ACL rule does not take effect and packets go to the next classification rule.
If the QoS policy is applied to a hardware interface, packets matching the referenced ACL rule are
organized as a class and the behavior defined in the QoS policy applies to the class regardless of
whether the referenced ACL rule is a deny or permit clause.
3) If a QoS policy is applied in the outbound direction of a port, the QoS policy cannot influence local
packets. Local packets refer to the important protocol packets that maintain the normal operation of
the device. QoS must not process such packets to avoid packet drop. Commonly used local
packets are: link maintenance packets, ISIS packets, OSPF packets, RIP packets, BGP packets,
LDP packets, RSVP packets, and SSH packets and so on.
4) When configuring queuing for a traffic behavior:
In a policy, a traffic behavior with EF configured cannot be associated with the default class, while
a traffic behavior with WFQ configured can only be associated with the default class.
In a policy, the total bandwidth assigned to the AF and EF classes cannot be greater than the
available bandwidth of the interface to which the policy applies; the total bandwidth percentage
assigned to the AF and EF classes cannot be greater than 100%.
In the same policy, the same bandwidth unit must be used to configure bandwidth for AF classes
and EF classes, either absolute bandwidth value or percent.