H3C Technologies H3C SecPath F1000-E - Manual (Page 342)

317
{
Select policy from the Policy Name list.
{
Select Inbound from the Direction list.
{
Click Apply.
Configuration guidelines
When you configure a QoS policy, note that:
• How an ACL referenced by a QoS policy is handled depends on whether the policy is applied to
a software interface or a hardware interface.
{
If the QoS policy is applied to a software interface, only the permit statements in the referenced
ACL will take effect and the deny statements in the referenced ACL will be ignored.
{
If the QoS policy is applied to a hardware interface, packets matching the ACL are organized
as a class and the behavior defined in the QoS policy applies to the class regardless of whether
the referenced ACL is a deny or permit clause.
• The QoS policy applied in the outbound direction of a port does not take effect on local protocol
data units (PDUs). Local PDUs are packets sent by the protocols essential to device operation from
the local device, such as link maintenance packets like ISIS, OSPF, RIP, BGP, LDP, RSVP, and SSH.
Because drop of local PDUs may cause anomaly, QoS is designed not to regulate local PDUs.
• When you configure queuing for a traffic behavior, follow these guidelines:
{
The sum of the bandwidth assigned to the AF and EF classes in a policy must be smaller than the
available bandwidth of the interface to which the policy is applied. The sum of bandwidth
percentage assigned to the AF and EF classes in a policy must be less than or equal to 100.
{
The bandwidth assigned to the AF and EF classes in a policy must be represented in the same
format as absolute bandwidth values or as percentages.