The traffic-user-queue command creates a subscriber queue on an interface to implement HQoS.
The undo traffic-user-queue command deletes a subscriber queue on an interface.
By default, no subscriber queue is configured on an interface.
If a single ACL is used, use the following command:
traffic-user-queue outbound acl { [ ipv6 ] { bas-acl | adv-acl | name acl-name } } pir pir-value [ flow-queue-profile flow-queue-profile-name | flow-mapping-profile flow-mapping-profile-name ] *
undo traffic-user-queue outbound acl { [ ipv6 ] { bas-acl | adv-acl | name acl-name } }
If both Layer 2 and Layer 3 ACLs are configured, use the following command:
traffic-user-queue outbound acl { l2-acl | name acl-name } acl { bas-acl | adv-acl | name acl-name } pir pir-value [ flow-queue-profile flow-queue-profile-name | flow-mapping-profile flow-mapping-profile-name ] *
undo traffic-user-queue outbound acl { l2-acl | name acl-name } acl { bas-acl | adv-acl | name acl-name }
traffic-user-queue outbound acl { bas-acl | adv-acl | name acl-name } acl { l2-acl | name acl-name } pir pir-value [ flow-queue-profile flow-queue-profile-name | flow-mapping-profile flow-mapping-profile-name ] *
undo traffic-user-queue outbound acl { bas-acl | adv-acl | name acl-name } acl { l2-acl | name acl-name }
The flow-mapping-profile flow-mapping-profile-name parameter is not supported on the S5731-S, S5731S-S, S5731-H, and S5731S-H.
Parameter |
Description |
Value |
---|---|---|
outbound |
Creates a subscriber queue in the outbound direction on an interface to implement HQoS scheduling. |
- |
acl |
Creates a subscriber queue based on IPv4 ACLs to implement HQoS scheduling. |
- |
ipv6 |
Creates a subscriber queue based on IPv6 ACLs to implement HQoS scheduling. |
- |
bas-acl |
Creates a subscriber queue based on basic ACLs to implement HQoS scheduling. |
The value is an integer that ranges from 2000 to 2999. |
adv-acl |
Creates a subscriber queue based on advanced ACLs to implement HQoS scheduling. |
The value is an integer that ranges from 3000 to 3999. |
l2-acl |
Creates a subscriber queue based on Layer 2 ACLs to implement HQoS scheduling. |
The value is an integer that ranges from 4000 to 4999. |
name acl-name |
Creates a subscriber queue based on named ACLs to implement HQoS scheduling. acl-name specifies the name of the ACL. |
The value must be the name of an existing ACL. |
pir pir-value |
Specifies the peak information rate (PIR) of a subscriber queue, which is the maximum rate of traffic that can pass through an interface. |
The value is an integer that ranges from 64 to 10000000, in kbit/s. |
flow-queue-profile flow-queue-profile-name |
Specifies the name of the referenced flow queue profile. |
The value must be the name of an existing flow queue profile. |
flow-mapping-profile flow-mapping-profile-name |
Specifies the name of the referenced flow mapping profile. |
The value must be the name of an existing flow mapping profile. |
GE interface view, XGE interface view, 25GE interface view, Eth-Trunk interface view, port group view
Usage Scenario
Multiple users can be differentiated based on ACL rules. When different scheduling and shaping parameters need to be set for different users and differentiated services need to be provided for different service traffic of the same user, run the traffic-user-queue command to configure multiple subscriber queues, set different scheduling modes and traffic shaping rates, and reference different flow queue profiles and flow mapping profiles to implement fine-granular scheduling.
Prerequisites
The acl (system view) or acl name command has been executed to create an ACL.
# Create a subscriber queue based on ACLs on the GE0/0/1 to implement HQoS.
<HUAWEI> system-view [HUAWEI] acl 3000 [HUAWEI-acl-adv-3000] rule 5 permit ip source 192.168.0.2 0 [HUAWEI-acl-adv-3000] quit [HUAWEI] interface gigabitethernet 0/0/1 [HUAWEI-GigabitEthernet0/0/1] traffic-user-queue outbound acl 3000 pir 1000 flow-queue-profile flow1 flow-mapping-profile map1