Login
- Table of Contents
-
- 04-Policies
- 01-Security policy
- 02-Security policy redundancy analysis
- 03-Security policy hit analysis
- 04-Security policy optimization
- 05-Policy-based NAT
- 06-Interface NAT
- 07-AFT
- 08-QoS
- 09-Bandwidth management
- 10-Application audit
- 11-Application proxy
- 12-IP reputation
- 13-Domain reputation
- 14-Blacklist
- 15-Connection limit
- 16-Server connection detection
- 17-Access rate limit
- 18-DLP
- 19-Server load balancing
- 20-Outbound link load balancing
- 21-Inbound link load balancing
- 22-Transparent DNS proxy
- 23-NetShare control
- 24-Zero trust policy
- 25-Trusted application proxies
- 26-Trusted API proxies
- 27-NAT66
- 28-uRPF
- 29-Load balancing common configuration
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 08-QoS | 33.01 KB |
QoS
This help contains the following topics:
Introduction
In data communications, Quality of Service (QoS) provides differentiated service guarantees for diversified traffic in terms of bandwidth, delay, jitter, and drop rate, all of which can affect QoS.
QoS manages network resources and prioritizes traffic to balance system resources.
QoS policy
A QoS policy has two components: traffic class and traffic behavior. By associating a traffic class with a traffic behavior in a QoS policy, you can perform QoS actions on matching packets.
A QoS policy can only be applied to an interface to perform bandwidth control. Only one QoS policy can be applied to one direction of an interface. In the current software version, a QoS policy can only be applied to the inbound direction of an interface.
Traffic class
A traffic class is as set of criteria used to match packets. The device supports only IPv4 ACLs and IPv6 ACLs as criteria.
Traffic behavior
A traffic behavior is used control the amount of bandwidth consumed by matching packets.
Configure QoS
Configure a QoS policy
1. Click the Policies tab.
2. In the navigation pane, select QoS Policies.
3. Click Create, and select an interface apply a QoS policy.
4. Click Policy details for the interface.
5. Click Create to create a QoS policy.
Table 1 QoS policy configuration items
|
Item |
Description |
|
Match IPv4 ACL |
Specify an IPv4 ACL by its number as the match criterion. The value range for the ACL number is 2000 to 3999. |
|
Match IPv6 ACL |
Specify an IPv6 ACL by its number as the match criterion. The value range for the ACL number is 2000 to 3999. |
|
Match logic |
Specify a match logic. · AND: To match a traffic class, a packet must match all IPv4 or IPv6 ACLs of the traffic class. · OR: To match a traffic class, a packet needs to match only one IPv4 or IPv6 ACL of the traffic class. |
|
CIR |
Specify the CIR. |
|
CBS |
Specify the CBS. |
|
EBS |
Specify the EBS. |
|
PIR |
Specify the PIR. |
|
Green action |
Specifies the action to take on packets that conform to the CIR. · pass: Permits the packet to pass through. · remark-dot1p-pass: Sets the 802.1p priority of the packet to a new value and permits the packet to pass through. The value range is 0 to 7. · remark-dscp-pass: Sets the DSCP priority of the packet to a new value and permits the packet to pass through. The value range is 0 to 63. · remark-mpls-exp-pass: Sets the EXP priority of the MPLS packet to a new value and permits the packet to pass through. The value range is 0 to 7. · remark-prec-pass: Sets the IP precedence of the MPLS packet to a new value and permits the packet to pass through. The value range is 0 to 7. · discard: Drops the packet. |
|
Yellow action |
Specifies the action to take on packets that conform to the PIR but not to the CIR. Available actions are the same as those for the green action. |
|
Red action |
Specifies the action to take on packets that conform to neither CIR nor PIR. Available actions are the same as those for the green action. |
6. Click OK.
