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

46
• Select behavior_1 from the Behavior Name drop-down list.
• Click Apply.
Step5 Apply the policy to an interface
# Apply the policy named policy to the incoming packets of GigabitEthernet 0/1.
• Select Firewall > Traffic Policing > Apply from the navigation tree, and click Apply Policy.
Perform configuration on the page shown in
Figure 61 .
Figure 61 Apply the policy named policy to the incoming packets of GigabitEthernet 0/1
• Select GigabitEthernet 0/1 from the Interface Name drop-down list.
• Select policy from the Policy Name drop-down list.
• Select Inbound from the Direction drop-down list.
• Click Apply.
Configuration Guidelines
When configuring a QoS policy, note that:
1. 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. (Categorization of interfaces varies by device.)
• 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.
2. 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.
3. When configuring queuing for a traffic behavior, note that:
• In a policy, the system-defined class default-class cannot be associated with a traffic behavior
configured with EF; a traffic behavior configured with WFQ can be associated with only a
system-defined class.
• 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.