No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

AR500, AR510, and AR530 V200R007 Commands Reference

This document describes all the configuration commands of the device, including the command function, syntax, parameters, views, default level, usage guidelines, examples, and related commands.
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Congestion Avoidance and Congestion Management Commands

Congestion Avoidance and Congestion Management Commands

display drop-profile

Function

The display drop-profile command displays the configuration of a WRED drop profile.

Format

display drop-profile [ drop-profile-name ]

Parameters

Parameter

Description

Value

drop-profile-name

Displays detailed information about a WRED drop profile with the specified name. If the parameter is not specified, brief information about all drop profiles is displayed.

The value is a string of 1 to 31 case-sensitive characters without spaces.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

You can use the display drop-profile command to view the number of configured drop profiles and all configuration of a specified drop profile.

Precautions

In addition to the default drop profile, a maximum of 63 drop profiles can be configured on the device.

Example

# Display brief information about all drop profiles on the device.

<Huawei> display drop-profile
        Index                   Drop-profile name                               
-----------------------------------------------------------------               
        1                       drop-profile1                                           
        2                       drop-profile2                                           
-----------------------------------------------------------------               
 Total   63     Used   2 

# Display detailed information about the drop profile named drop-profile1.

<Huawei> display drop-profile drop-profile1
Drop-profile[1]: drop-profile1                                                  
IP-Precedence      Low-limit   High-limit  Discard-percentage                   
-----------------------------------------------------------------               
0(routine)         30          100         10                                   
1(priority)        30          100         10                                   
2(immediate)       30          100         10                                   
3(flash)           30          80          50                                   
4(flash-override)  30          100         10                                   
5(critical)        30          100         10                                   
6(internet)        30          100         10                                   
7(network)         30          100         10                                   
-----------------------------------------------------------------               
Table 15-14  Description of the display drop-profile command output

Item

Description

Index

Drop profile index.

Drop-profile name

Drop profile name.

To configure a drop profile, run the drop-profile (system view) command.

Total

Total number of drop profiles that can be configured on the device.

Used

Number of configured drop profiles.

Drop-profile[1]

Drop profile name in which 1 indicates the drop profile index.

IP-Precedence

WRED drop profile based on IP priorities of packets. If the WRED drop profile is based on DSCP priorities of packets, DSCP is displayed.

Low-limit

Lower drop threshold, in percentage.

High-limit

Upper drop threshold, in percentage.

Discard-percentage

Maximum drop probability, in percentage.

To set the maximum drop probability, run the ip-precedence discard-percentage or dscp discard-percentage command.

display qos queue statistics

Function

The display qos queue statistics command displays queue-based traffic statistics on an interface.

Format

display qos queue statistics interface interface-type interface-number [ queue queue-index ]

display qos queue statistics interface virtual-template vt-number virtual-access va-number [ queue queue-index ]

Parameters

Parameter

Description

Value

interface interface-type interface-number

Displays queue-based traffic statistics on a specified interface.
  • interface-type specifies the interface type.
  • interface-number specifies the interface number.

-

virtual-template vt-number

Displays queue-based traffic statistics on a specified virtual template interface. vt-number specifies the number of the virtual template interface.

The value is an integer that ranges from 0 to 1023.

virtual-access va-number

Displays queue-based traffic statistics on a specified virtual access interface. va-number specifies the number of the virtual access interface. You can run the display virtual-access command to view the virtual access interface status.

The value is an integer that ranges from 0 to 1023.

queue queue-index

Displays statistics on the queue with a specified index.

The value is an integer that ranges from 0 to 7.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

To check whether packets in each queue on an interface are forwarded or discarded because of congestion, view the statistics on each queue on the interface.

Precautions

Each WAN-side interface on the device has a protocol queue named protocol, which cannot be modified or deleted. Protocol queues are responsible for forwarding all protocol packets such as ARP packets, and ICMP packets on the control plane. Packets in a protocol queue are scheduled in Strict Priority (SP) mode. Packets in other queues can be scheduled only after packets in protocol queues are scheduled.

NOTE:
  • The Layer 2 FE interfaces and Layer 2 GE interfaces on the device do not support the display qos queue statistics command.

Example

# Display traffic statistics on queues on GE1/0/0.

<Huawei> display qos queue statistics interface gigabitethernet 1/0/0
-----------------------------------------------------------------------------   
Queue            Passed          Pass Rate        Dropped         Drop Rate     
            (Packets/Bytes)      (pps/bps)    (Packets/Bytes)     (pps/bps)     
-----------------------------------------------------------------------------   
0                      0/              0/              -/              -/       
                       -               -               -               -        
1                      0/              0/              -/              -/       
                       -               -               -               -        
2                      0/              0/              -/              -/       
                       -               -               -               -        
3                      0/              0/              -/              -/       
                       -               -               -               -        
4                      0/              0/              -/              -/       
                       -               -               -               -        
5                      0/              0/              -/              -/       
                       -               -               -               -        
6                   1850/              0/              -/              -/       
                       -               -               -               -        
7                      0/              0/              -/              -/       
                       -               -               -               -        
-----------------------------------------------------------------------------    
Table 15-15  Description of the display qos queue statistics command output

Item

Description

Queue

Queue index.

Passed(Packets/Bytes)

Statistics on forwarded packet or bytes. If the information is displayed as -, the statistics on this item cannot be collected.

Pass Rate(pps/bps)

Rate of forwarded packets, in pps or bit/s. This item indicates the average rate of packets that are forwarded since the last time the display qos queue statistics command is run to query traffic statistics. If the information is displayed as -, the statistics on this item cannot be collected.

Dropped(Packets/Bytes)

Statistics on discarded packets or bytes. If the information is displayed as -, the statistics on this item cannot be collected.

Drop Rate(pps/bps)

Rate of discarded packets, in pps or bit/s. This item indicates the average rate of packets that are discarded since the last time the display qos queue statistics command is run to query traffic statistics. If the information is displayed as -, the statistics on this item cannot be collected.

display qos queue-profile

Function

The display qos queue-profile command displays information about queue profiles.

Format

display qos queue-profile [ queue-profile-name ]

Parameters

Parameter

Description

Value

queue-profile-name

Specifies the name of a queue profile. If this parameter is not specified, brief information about all queue profiles is displayed.

The value is a string of 1 to 31 case-sensitive characters without spaces.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

On the device, a maximum of 32 queue profiles can be configured. Before or after configuring queue profiles, you can use the display qos queue-profile command to view the number of configured queue profiles and all the configuration of the specified queue profile.

Example

# Display all the queue profile indexes and names.

<Huawei> display qos queue-profile
Index                      Queue-profile name
-----------------------------------------------------------------
0	                         qp1
1	                         qp2
2	                         qp3
----------------------------------------------------------------
  Total  32  Used  3

# Display the detailed configuration of the queue profile qp1.

<Huawei> display qos queue-profile qp1
Queue-profile:qp1
Queue   Schedule   Weight  Length(Bytes/Packets)  GTS(CIR/CBS)
--------------------------------------------------------------------------------------------------
0        DRR       10       -/-                    -/-
1        DRR       10       -/-                    -/-
2        DRR       10       -/-                    -/-
3        DRR       10       -/-                    -/-
4        DRR       10       -/-                    -/-
5        PQ        -        -/-                    -/-
6        PQ        -        -/-                    -/-
7        PQ        -        -/-                    64/10000
Table 15-16  Description of the display qos queue-profile command output

Item

Description

Index

Queue profile index.

Queue-profile name

Queue profile name.

Total

Maximum number of queue profiles that can be configured on the device.

Used

Number of configured queue profiles.

Queue

Queue index.

Schedule

Scheduling mode:
  • DRR
  • PQ
  • WFQ
  • WRR
To set the scheduling mode, run the schedule command.

Weight

Queue weight.

Length(Bytes/Packets)

Queue length, which can be the number of bytes or the number of packets.

GTS(CIR/CBS)

Traffic shaping rate, which can be the CIR or CBS value. To configure GTS, run the queue gts command.

dscp discard-percentage

Function

The dscp discard-percentage command sets WRED parameters for packets with a specified DSCP priority, including the upper and lower drop thresholds and the maximum drop probability.

The undo dscp command restores the default values of WRED parameters for packets with a specified DSCP priority.

By default, the lower drop threshold is 30%, the upper drop threshold is 100%, and the maximum drop probability is 10%.

Format

dscp { dscp-value1 [ to dscp-value2 ] } &<1-10> low-limit low-limit-percentage high-limit high-limit-percentage discard-percentage discard-percentage

undo dscp [ dscp-value1 [ to dscp-value2 ] ] &<1-10>

Parameters

Parameter

Description

Value

dscp-value1

Specifies the start DSCP priority.

The value can be the DiffServ code, ranging from 0 to 63; the value can also be the name of the DSCP service type, such as af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, cs1-cs7, default, and ef.

The service types are as follows:

  • af11: 10
  • af12: 12
  • af13: 14
  • af21: 18
  • af22: 20
  • af23: 22
  • af31: 26
  • af32: 28
  • af33: 30
  • af41: 34
  • af42: 36
  • af43: 38
  • cs1: 8
  • cs2: 16
  • cs3: 24
  • cs4: 32
  • cs5: 40
  • cs6: 48
  • cs7: 56
  • default: 0
  • ef: 46

dscp-value2

Specifies the end DSCP priority.

The value can be the DiffServ code, ranging from 0 to 63; the value can also be the name of the DSCP service type, such as af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, cs1-cs7, default, and ef.

The service types are as follows:

  • af11: 10
  • af12: 12
  • af13: 14
  • af21: 18
  • af22: 20
  • af23: 22
  • af31: 26
  • af32: 28
  • af33: 30
  • af41: 34
  • af42: 36
  • af43: 38
  • cs1: 8
  • cs2: 16
  • cs3: 24
  • cs4: 32
  • cs5: 40
  • cs6: 48
  • cs7: 56
  • default: 0
  • ef: 46

low-limit-percentage

Specifies the lower drop threshold. When the percentage of the packet count in a queue to the queue length reaches this value, packets start to be discarded.

The value is an integer that ranges from 0 to 100. The default value is 30.

high-limit-percentage

Specifies the upper drop threshold. When the percentage of the packet count in a queue to the queue length reaches this value, all the packets are discarded.

The value is an integer that ranges from low-limit-percentage to 100. The default value is 100.

discard-percentage

Specifies the maximum drop probability.

The value is an integer that ranges from 1 to 100. The default value is 10.

Views

Drop profile view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

By default, the device uses the tail drop method and discards data packets at the end of a queue when congestion occurs. The tail drop method causes global Transmission Control Protocol (TCP) synchronization and reduces link usage.

WRED is a random drop method based on packet priorities. It has the following advantages:
  • WRED discards packets based on packet priorities, so the drop probability of packets with higher priorities is low.
  • WRED sets the upper and lower drop thresholds and the maximum drop probability and discards packets randomly, which prevents global TCP synchronization.
The drop probability varies according to the queue length, as shown in Figure 15-1.
  • When the queue length is smaller than the lower drop threshold, no packet is discarded.
  • When the queue length is greater than the upper drop threshold, all packets are discarded.
  • When the queue length is between the lower drop threshold and the upper drop threshold, incoming packets are discarded randomly. The drop probability cannot be greater than the maximum drop probability.
Figure 15-1  WRED drop probability

Follow-up Procedure

Perform either of the following operations as required:

  • Apply the drop profile to a queue profile.

    Run the queue drop-profile command in the queue profile view to bind the drop profile to each queue, and then run the qos queue-profile (interface view) command to bind the queue profile to an interface.

  • Apply the drop profile to a traffic policy.

    Run the drop-profile (traffic behavior view) command to bind the drop profile to a traffic behavior, bind the traffic behavior and traffic classifier to the traffic policy, and then apply the traffic policy to an interface.

Precautions

When congestion occurs, packets with the maximum drop probability are discarded first.

The dscp discard-percentage and ip-precedence discard-percentage command cannot be used in the same drop profile view. If the drop profile based on IP priorities is used, you must run the wred dscp command.

If you run the dscp discard-percentage command with the same DSCP priority in the same drop profile view, only the latest configuration takes effect.

Example

# In the drop profile drop-profile1, set the upper and lower drop thresholds to 80% and 50% and the maximum drop probability to 30% for packets with DSCP priority 3.

<Huawei> system-view
[Huawei] drop-profile drop-profile1
[Huawei-drop-profile-drop-profile1] wred dscp
[Huawei-drop-profile-drop-profile1] dscp 3 low-limit 50 high-limit 80 discard-percentage 30

ip-precedence discard-percentage

Function

The ip-precedence discard-percentage command sets WRED parameters for packets with a specified IP precedence, including the upper and lower drop thresholds and the maximum drop probability.

The undo ip-precedence command restores the default values of WRED parameters for packets with a specified IP precedence.

By default, the lower drop threshold is 30%, the upper drop threshold is 100%, and the maximum drop probability is 10%.

Format

ip-precedence { ip-precedence-value1 [ to ip-precedence-value2 ] } &<1-10> low-limit low-limit-percentage high-limit high-limit-percentage discard-percentage discard-percentage

undo ip-precedence [ ip-precedence-value1 [ to ip-precedence-value2 ] ] &<1-10>

Parameters

Parameter

Description

Value

ip-precedence-value1

Specifies the start IP precedence.

The value can be an integer or a name. The integer ranges from 0 to 7. The mappings between names and numbers are as follows:
  • network: 7
  • internet: 6
  • critical: 5
  • flash-override: 4
  • flash: 3
  • immediate: 2
  • priority: 1
  • routine: 0

ip-precedence-value2

Specifies the end IP precedence.

The value can be an integer or a name. The integer ranges from 0 to 7. The mappings between names and numbers are as follows:
  • network: 7
  • internet: 6
  • critical: 5
  • flash-override: 4
  • flash: 3
  • immediate: 2
  • priority: 1
  • routine: 0

low-limit-percentage

Specifies the lower drop threshold. When the percentage of the packet count in a queue to the queue length reaches this value, packets start to be discarded.

The value is an integer that ranges from 0 to 100. The default value is 30.

high-limit-percentage

Specifies the upper drop threshold. When the percentage of the packet count in a queue to the queue length reaches this value, all the packets are discarded.

The value is an integer that ranges from low-limit-percentage to 100. The default value is 100.

discard-percentage

Specifies the maximum drop probability.

The value is an integer that ranges from 1 to 100. The default value is 10.

Views

Drop profile view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

By default, the device uses the tail drop method and discards data packets at the end of a queue when congestion occurs. The tail drop method causes global Transmission Control Protocol (TCP) synchronization and reduces link usage.

WRED is a random drop method based on packet priorities. It has the following advantages:
  • WRED discards packets based on packet priorities, so the drop probability of packets with higher priorities is low.
  • WRED sets the upper and lower drop thresholds and the maximum drop probability and discards packets randomly, which prevents global TCP synchronization.
The drop probability varies according to the queue length, as shown in Figure 15-2.
  • When the queue length is smaller than the lower drop threshold, no packet is discarded.
  • When the queue length is greater than the upper drop threshold, all packets are discarded.
  • When the queue length is between the lower drop threshold and the upper drop threshold, incoming packets are discarded randomly. The drop probability cannot be greater than the maximum drop probability.
Figure 15-2  WRED drop probability

Follow-up Procedure

Apply the drop profile to a queue profile or traffic policy:

  • Apply the drop profile to a queue profile.

    Run the queue drop-profile command in the queue profile view to bind the drop profile to each queue, and then run the qos queue-profile (interface view) command to bind the queue profile to an interface.

  • Apply the drop profile to a traffic policy.

    Run the drop-profile (traffic behavior view) command to bind the drop profile to a traffic behavior, bind the traffic behavior and traffic classifier to the traffic policy, and then apply the traffic policy to an interface.

Precautions

When congestion occurs, packets with the maximum drop probability are discarded first.

The dscp discard-percentage and ip-precedence discard-percentage command cannot be used in the same drop profile view. If the drop profile based on DSCP priorities is used, you must run the wred ip-precedence command.

If you run the ip-precedence discard-percentage command with the same precedence in the same drop profile view, only the latest configuration takes effect.

Example

# In the drop profile drop-profile1, set the upper and lower drop thresholds to 80% and 50% and the maximum drop probability to 30% for packets with IP precedence 3.

<Huawei> system-view
[Huawei] drop-profile drop-profile1
[Huawei-drop-profile-drop-profile1] wred ip-precedence
[Huawei-drop-profile-drop-profile1] ip-precedence 3 low-limit 50 high-limit 80 discard-percentage 30

drop-profile (system view)

Function

The drop-profile command creates a drop profile and enters the drop profile view, or enters the existing drop profile view.

The undo drop-profile command deletes a drop profile.

By default, the drop profile default exists.

Format

drop-profile drop-profile-name

undo drop-profile drop-profile-name

Parameters

Parameter

Description

Value

drop-profile-name

Specifies the name of a drop profile.

The value is a string of 1 to 31 case-sensitive characters without spaces.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

By default, the device uses the tail drop method and discards data packets at the end of a queue when congestion occurs. The tail drop method causes global Transmission Control Protocol (TCP) synchronization and reduces link usage. The Weighted Random Early Detection (WRED) can solve the problem.

A drop profile defines WRED parameters for queues and is used to implement congestion avoidance for queues bound to the drop profile. The drop-profile command creates a drop profile and displays the drop profile view.

Follow-up Procedure

  1. Set WRED parameters in the drop profile.

    Run the dscp discard-percentage or ip-precedence discard-percentage command in the drop profile view to set WRED parameters for packets with a specified DSCP priority or IP precedence.

  2. Apply the drop profile.

    • Apply the drop profile to a queue profile.

      Run the queue drop-profile command in the queue profile view to bind the drop profile to each queue, and then run the qos queue-profile (interface view) command to bind the queue profile to an interface.

    • Apply the drop profile to a traffic policy.

      Run the drop-profile (traffic behavior view) command to bind the drop profile to a traffic behavior, bind the traffic behavior and traffic classifier to the traffic policy, and then apply the traffic policy to an interface.

Precautions

In addition to one reserved drop profile, a maximum of 63 drop profiles can be configured on the device.

On the device, a drop profile can be bound to queue profiles only on WAN-side interfaces. LAN-side interfaces do not support the drop profile configuration.

On the device, a drop profile can be bound to queue profiles only on WAN-side interfaces. LAN-side interfaces do not support the drop profile configuration.

If a drop profile is not applied to an interface, you can directly modify or delete the drop profile. If a drop profile has been applied to an interface:
  • When you modify the configuration of the drop profile, the modification is synchronized to the interface and takes effect immediately if the interface supports this configuration. If the interface does not support this configuration, the system displays a configuration failure message.
  • If the drop profile has been bound to a queue profile, to delete the drop profile, run the undo qos queue-profile command in the interface view to unbind the queue profile from the interface, run the undo queue drop-profile command in the queue profile view to unbind the drop profile from the queue profile, and run the undo drop-profile command to delete the drop profile.
  • If the drop profile has been bound to a traffic behavior, to delete the drop profile, run the undo traffic-policy command in the interface view to unbind the traffic policy containing the traffic behavior from the interface, run the undo drop-profile command in the traffic behavior view to unbind the drop profile from the traffic behavior, and run the undo drop-profile command to delete the drop profile.

Example

# Create a drop profile named hello-world.

<Huawei> system-view
[Huawei] drop-profile hello-world
[Huawei-drop-profile-hello-world]

drop-profile (traffic behavior view)

Function

The drop-profile command binds a drop profile to a traffic behavior for Assured Forwarding (AF) queues or Best-Effort (BE) queues in Weighted Fair Queuing (WFQ) mode.

The undo drop-profile command unbinds a drop profile from a traffic behavior for AF queues or BE queues in WFQ mode.

By default, no traffic behavior is bound to a drop profile. All queues use tail drop.

Format

drop-profile drop-profile-name

undo drop-profile

Parameters

Parameter

Description

Value

drop-profile-name

Specifies the name of a drop profile.

The value is a string of 1 to 31 case-sensitive characters without spaces.

Views

Traffic behavior view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After a drop profile is bound to a traffic behavior, bind the traffic behavior and traffic classifier to a traffic policy and apply the traffic policy to an interface so that WRED parameters in the drop profile take effect on the interface.

Prerequisites

A drop profile has been created by using the drop-profile (system view) command.

Precautions

A queue profile can only be bound to a traffic behavior in a traffic policy on the outbound WAN-side interface of the device.

A queue profile can only be bound to a traffic behavior in a traffic policy on the outbound WAN-side interface of the device.

When a traffic behavior is bound to a drop profile, the default queue length is 64 packets and cannot be set.

On the device, a traffic behavior can be bound to a drop profile for only AF queues and BE queues in WFQ mode. Tail drop is supported for only EF and LLQ queues.

When you bind a drop profile to or unbind a drop profile from a traffic behavior in a traffic policy that has been applied to an interface, the modification is synchronized to the interface and takes effect immediately if the interface supports this configuration. If the interface does not support this configuration, the system displays a configuration failure message.

If you run the drop-profile command multiple times in the same traffic behavior view, only the latest configuration takes effect.

Example

# Bind the drop profile dp1 to the traffic behavior database where the WFQ mode is used and the number of queues is 16.

<Huawei> system-view
[Huawei] traffic behavior database
[Huawei-behavior-database] queue wfq queue-number 16
[Huawei-behavior-database] drop-profile dp1

qos queue-profile (interface view)

Function

The qos queue-profile command applies a queue profile to an interface.

The undo qos queue-profile command deletes a queue profile from an interface.

By default, an interface is not bound to any queue profile.

Format

qos queue-profile queue-profile-name

undo qos queue-profile

NOTE:
  • Layer 2 interfaces on the device do not support the qos queue-profile (interface view) command.

Parameters

Parameter

Description

Value

queue-profile-name

Specifies the name of a queue profile.

The value is a string of 1 to 31 case-sensitive characters without spaces.

Views

Interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

A queue profile is a set of queue parameters that determine the scheduling mode between queues, length, weight, and traffic shaping rate of queues. After an interface is bound to a queue profile, different services can be provided for queues on the interface.

After a queue profile is created, bind the queue profile to an interface so that the scheduling modes, lengths, weights, and traffic shaping rates of queues take effect on the interface.

Prerequisites

A queue profile has been created by using the qos queue-profile (system view) command.

Precautions

WAN interfaces and LAN interfaces of the device support different scheduling modes.

When you modify the configuration of the queue profile bound to an interface, the modification is synchronized to the interface and takes effect immediately if the interface supports this configuration. If the interface does not support this configuration, the system displays a configuration failure message.

Example

# Create a queue profile named hello-world, set the length of queue 0 to 4096 bytes, retain default values for other parameters, and apply the queue profile to Eth0/0/1.

<Huawei> system-view
[Huawei] qos queue-profile hello-world
[Huawei-qos-queue-profile-hello-world] queue 0 length bytes 4096
[Huawei-qos-queue-profile-hello-world] quit
[Huawei] interface ethernet 0/0/1
[Huawei-Ethernet0/0/1] qos queue-profile hello-world
[Huawei-Ethernet0/0/1] quit

qos queue-profile (system view)

Function

The qos queue-profile command creates a queue profile and displays its view, or directly displays the view of the existing queue profile.

The undo qos queue-profile command deletes a queue profile.

By default, no queue profile is configured.

Format

qos queue-profile queue-profile-name

undo qos queue-profile queue-profile-name

Parameters

Parameter

Description

Value

queue-profile-name

Specifies the name of a queue profile.

The value is a string of 1 to 31 case-sensitive characters without spaces.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The qos queue-profile (system view) command is used to create a queue profile. The queue profile is a set of queue parameters that determine the scheduling mode, lengths, weights, and traffic shaping rates of queues. After a queue profile is bound to an interface, different services can be provided for queues on the interface.

Follow-up Procedure

The qos queue-profile (interface view) command binds a queue profile to an interface.

Precautions

A maximum of 32 queue profiles can be configured on the device.

When you modify the configuration of the queue profile bound to an interface, the modification is synchronized to the interface and takes effect immediately if the interface supports this configuration. If the interface does not support this configuration, the system displays a configuration failure message.

To delete the queue profile bound to an interface, run the undo qos queue-profile command in the interface view to unbind the queue profile from the interface. Then run the undo qos queue-profile queue-profile-name command in the system view to delete the queue profile.

NOTE:
  • Only the scheduling mode can be set in a queue profile bound to a Layer 2 FE interface and Layer 2 GE interface of the device.
  • Layer 2 interface of the AR515GW-LM9–D does not support to bind a queue profile.

Example

# Create a queue profile named hello-world.

<Huawei> system-view
[Huawei] qos queue-profile hello-world
[Huawei-qos-queue-profile-hello-world]

queue af

Function

The queue af command configures Assured Forwarding (AF) for packets of a certain type and sets the assured minimum bandwidth.

The undo queue af command cancels AF for packets of a certain type.

By default, AF is not configured for packets of a certain type.

Format

queue af bandwidth { bandwidth | [ remaining ] pct percentage }

undo queue af

Parameters

Parameter

Description

Value

remaining

Specifies the remaining bandwidth of an interface. If this parameter is specified:

pct = AF queue bandwidth/(Actual available bandwidth of the interface - EF queue bandwidth)

If this parameter is not specified:

pct = AF queue bandwidth/Actual available bandwidth of the interface

-

bandwidth

Specifies the assured minimum bandwidth.

The value is an integer that ranges from 8 to 4294967295, in kbit/s.

pct percentage

Specifies the percentage of the minimum bandwidth to the available bandwidth on an interface.

The value is an integer that ranges from 1 to 100.

Views

Traffic behavior view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The device provides the following types of queues for packets matching user-defined traffic classifiers:
  • Assured Forwarding (AF) queues
  • Expedited Forwarding (EF) queues
  • Best Effort (BE) queues
  • Low-latency (LLQ) queues

AF ensures a low drop probability of packets when the rate of outgoing service traffic does not exceed the minimum bandwidth. It is applied to services of heavy traffic whose bandwidth needs to be ensured.

You can specify remaining to configure the percentage of the remaining available bandwidth to provide fine-grained bandwidth allocation. For example, an EF queue is configured and assigned 95% of the actual available bandwidth of the interface. The remaining 5% bandwidth needs to be allocated to two AF queues. One AF queue occupies 10% of the remaining bandwidth, and the other occupies 90% of the remaining bandwidth. You can specify remaining.

Follow-up Procedure

Create a traffic classifier and a traffic policy, bind the traffic classifier to the traffic behavior in the traffic policy, and then apply the traffic policy.

Precautions

AF can only be configured in a traffic behavior of a traffic policy on the outbound WAN-side interface of the device.

An interface can be bound to only a traffic policy containing queue af or a queue profile.

A maximum of 64 AF queues are allowed in a traffic behavior of a traffic policy.

If multiple traffic behaviors in a traffic policy all define queue af, configure the percentage of the actual available bandwidth of the interface or percentage of the remaining bandwidth. If the percentage of the remaining bandwidth is configured, the sum of the percentage cannot exceed 100.

If AF, EF, LLQ are configured in traffic behaviors bound to a traffic policy, the sum of bandwidth values for AF, EF, LLQ queues must be smaller than or equal to the available bandwidth of the interface to which the traffic policy is applied. The available bandwidth is as follows:
  • If the qos gts or qos gts adaptation-profile command is not used on an interface:
    • The available bandwidth of a physical interface is the actual bandwidth of the physical interface. If the qos lr command is used on the physical interface, the available bandwidth is the actual bandwidth of the interface multiplied by the configured percentage of the rate for sending packets to the interface bandwidth.
    • The available bandwidth of a tunnel interface is 1 Gbit/s.
    • The available bandwidth of a logical interface such as the Eth-Trunk formed by binding multiple interfaces or sub-interfaces is the total bandwidth of bound interfaces or sub-interfaces.
    • The available bandwidth of the dialer interface is the actual bandwidth of a bound physical interface or the sum of bandwidth of multiple bound physical interfaces.
  • If the qos gts or qos gts adaptation-profile command is used on an interface, the available bandwidth is the CIR value.
NOTE:
  • If the queue af command has been used in a traffic behavior, you cannot use the queue ef, queue llq, or queue wfq command in the traffic behavior.

  • When you run the queue af command to configure the minimum bandwidth for AF queues in different traffic behaviors of the same traffic policy, use either the bandwidth or bandwidth percentage.
  • When a virtual template interface is bound to L2TP services, the percentage of the minimum bandwidth to the available bandwidth cannot be set on the virtual template interface.
  • If a traffic policy containing the traffic behavior is applied to an interface, the trust command does not take effect on the interface.

If you run the queue af command multiple times in the same traffic behavior view, only the latest configuration takes effect.

Example

# Configure AF for the traffic behavior database and set the minimum bandwidth to 20000 kbit/s.

<Huawei> system-view
[Huawei] traffic behavior database
[Huawei-behavior-database] queue af bandwidth 20000

queue drop-profile

Function

The queue drop-profile command binds a drop profile to a queue in a queue profile.

The undo queue drop-profile command unbinds a drop profile from a queue in a queue profile.

By default, a drop profile is not bound to any queue. All queues use tail drop.

Format

queue { start-queue-index [ to end-queue-index ] } &<1-10> drop-profile drop-profile-name

undo queue { start-queue-index [ to end-queue-index ] } &<1-10> drop-profile

Parameters

Parameter

Description

Value

start-queue-index [ to end-queue-index ]

Specifies the index of a queue bound to a drop profile.
  • start-queue-index specifies the index of the first queue bound to a drop profile. The value is an integer that ranges from 0 to 7.
  • end-queue-index specifies the index of the last queue bound to a drop profile. The value is an integer that ranges from 0 to 7.
end-queue-index must be greater than start-queue-index. If to end-queue-index is not specified, only the queue specified by start-queue-index is bound to a drop profile.

-

drop-profile-name

Specifies the name of a drop profile.

The value is a string of 1 to 31 case-sensitive characters without spaces.

Views

Queue profile view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

By default, the device uses the tail drop method and discards data packets at the end of a queue when congestion occurs. The tail drop method causes global Transmission Control Protocol (TCP) synchronization and reduces link usage. The Weighted Random Early Detection (WRED) can solve the problem.

A drop profile defines WRED parameters. The queue drop-profile command binds a queue to a drop profile. You can bind the drop profile to a queue profile and apply the queue profile to the interface to implement congestion avoidance for queues bound to the drop profile.

Prerequisites

A drop profile has been created by using the drop-profile (system view) command.

WFQ has been configured by using the schedule command.

Precautions

Drop profiles can be bound to only queues using WFQ on WAN-side interfaces of the device.

When you bind a drop profile to or unbind a drop profile from a queue in a queue profile that has been applied to an interface, the modification is synchronized to the interface and takes effect immediately if the interface supports this configuration. If the interface does not support this configuration, the system displays a configuration failure message.

When running the schedule command to modify or delete the scheduling mode of a queue, you must delete the drop profile bound to the queue.

If you run the queue drop-profile command multiple times in the same queue profile view, only the latest configuration takes effect.

Example

# Bind the drop profile dp1 to queues 2 and 3 in the queue profile qp1.

<Huawei> system-view
[Huawei] qos queue-profile qp1
[Huawei-qos-queue-profile-qp1] schedule wfq 2 to 3
[Huawei-qos-queue-profile-qp1] queue 2 to 3 drop-profile dp1

queue ef

Function

The queue ef command configures Expedited Forwarding (EF) for packets of a certain type and sets the maximum bandwidth.

The undo queue ef command cancels EF for packets of a certain type.

By default, EF is not configured for packets of a certain type.

Format

queue ef bandwidth { bandwidth [ cbs cbs-value ] | pct percentage [ cbs cbs-value ] }

undo queue ef

Parameters

Parameter

Description

Value

bandwidth

Specifies the maximum bandwidth for EF queues.

The value is an integer that ranges from 8 to 4294967295, in kbit/s.

cbs cbs-value

Specifies the committed burst size (CBS).

The value is an integer that ranges from 32 to 4294967295, in bytes.

By default, the CBS value is 25 times the value of bandwidth.

pct percentage

Specifies the percentage of the maximum bandwidth to the available bandwidth on an interface.

The value is an integer that ranges from 1 to 100.

Views

Traffic behavior view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The device provides the following types of queues for packets matching user-defined traffic classifiers:
  • Assured Forwarding (AF) queues
  • Expedited Forwarding (EF) queues
  • Best Effort (BE) queues
  • Low-latency (LLQ) queues

After packets matching a rule enter EF queues, they are scheduled in Strict Priority (SP) mode. Packets in other queues are scheduled only after all the packets in EF queues are scheduled.

EF is applied to the services requiring the low delay, low drop probability, assured bandwidth, and occupying low bandwidth, for example, voice packets.

NOTE:

After the maximum bandwidth of EF queues is set, if there is traffic in other queues, EF queues can obtain the maximum bandwidth specified by bandwidth. If there is no traffic in other queues, EF queues can obtain the maximum bandwidth of the interface to ensure that high-priority packets are forwarded.

Follow-up Procedure

Create a traffic classifier and a traffic policy, bind the traffic classifier to the traffic behavior in the traffic policy, and then apply the traffic policy.

Precautions

EF can only be configured in a traffic behavior of a traffic policy on the outbound WAN-side interface of the device.

An interface can be bound to only a traffic policy containing queue ef or a queue profile.

If AF, EF, LLQ are configured in traffic behaviors bound to a traffic policy, the sum of bandwidth values for AF, EF, LLQ queues must be smaller than or equal to the available bandwidth of the interface to which the traffic policy is applied. When you use the bandwidth percentage to set the maximum bandwidth, the available bandwidth is as follows:
  • If the qos gts or qos gts adaptation-profile command is not used on an interface:
    • The available bandwidth of a physical interface is the actual bandwidth of the physical interface. If the qos lr command is used on the physical interface, the available bandwidth is the actual bandwidth of the interface multiplied by the configured percentage of the rate for sending packets to the interface bandwidth.
    • The available bandwidth of a tunnel interface is 1 Gbit/s.
    • The available bandwidth of a logical interface such as the Eth-Trunk formed by binding multiple interfaces or sub-interfaces is the total bandwidth of bound interfaces or sub-interfaces.
    • The available bandwidth of the dialer interface is the actual bandwidth of a bound physical interface or the sum of bandwidth of multiple bound physical interfaces.
  • If the qos gts or qos gts adaptation-profile command is used on an interface, the available bandwidth is the CIR value.
NOTE:
  • If the queue ef command has been used in a traffic behavior, you cannot use the queue af, queue llq, queue wfq, gts (traffic behavior view), or gts adaptation-profile command in the traffic behavior.

  • When you run the queue ef command to configure the maximum bandwidth for EF queues in different traffic behaviors of the same traffic policy, use either the bandwidth or bandwidth percentage.

  • When a virtual template interface is bound to L2TP services, the percentage of the maximum bandwidth to the available bandwidth cannot be set on the virtual template interface.
  • If a traffic policy containing the traffic behavior is applied to an interface, the trust command does not take effect on the interface.

  • A maximum of four EF and LLQ queues are allowed in a traffic behavior of a traffic policy. Packets in EF or LLQ queues are scheduled in SP mode. Packets in AF queues and BE queues are scheduled only after packets in EF or LLQ queues are scheduled. Packets in EF or LLQ queues are scheduled in SP mode according to the sequence in which queues were configured. Packets in the queue that was configured first are scheduled first.

If you run the queue ef command multiple times in the same traffic behavior view, only the latest configuration takes effect.

Example

# Configure EF for the traffic behavior database, and set the maximum bandwidth to 200 kbit/s and CBS value to 5000 bytes.

<Huawei> system-view
[Huawei] traffic behavior database
[Huawei-behavior-database] queue ef bandwidth 200 cbs 5000

queue length

Function

The queue length command sets the length of a queue.

The undo queue length command restores the default length of a queue.

Table 15-17 lists the default lengths of queues.
Table 15-17  Default lengths of queues in different scheduling modes

Scheduling Mode

Default Queue length

PQ

  • WAN-side interfaces: 128000 bytes or 64 packets
  • LAN-side interfaces: 5120 bytes or 20 packets

DRR

LAN-side interfaces: 5120 bytes or 20 packets

WRR

LAN-side interfaces: 5120 bytes or 20 packets

WFQ

131072 bytes or 64 packets

Format

queue { start-queue-index [ to end-queue-index ] } &<1-10> length { bytes bytes-value | packets packets-value }*

undo queue { start-queue-index [ to end-queue-index ] } &<1-10> length [ bytes | packets ]*

Parameters

Parameter

Description

Value

start-queue-index [ to end-queue-index ]

Specifies the index of a queue.
  • start-queue-index specifies the index of the first queue. The value is an integer that ranges from 0 to 7.
  • end-queue-index specifies the index of the last queue. The value is an integer that ranges from 0 to 7.
If to end-queue-index is not specified, the queue length is configured for only the queue specified by start-queue-index.

-

bytes bytes-value

Specifies the maximum number of bytes that can be buffered in a queue.

The value is an integer that ranges from 2048 to 2097152.

packets packets-value

Specifies the maximum number of packets that can be buffered in a queue.

The value is an integer that ranges from 1 to 1024.

Views

Queue profile view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The queue length affects queue traffic shaping, congestion management, and congestion avoidance. When the number of packets in a queue reaches the maximum value or the total number of bytes in a queue reaches the maximum value, the queue does not receive packets. Instead, the queue discards the excess packets.

A longer queue buffers more packets but introduces a longer delay. If congestion occurs on a network intermittently, a longer queue prevents unnecessary packet loss. If congestion always occurs on a network, increasing the queue length cannot solve the problem. To solve this problem, increase the bandwidth.

Follow-up Procedure

Run the qos queue-profile (interface view) command to bind the queue profile to an interface.

Precautions

When you modify the queue length in the queue profile bound to an interface, the modification is synchronized to the interface automatically if the interface supports this configuration. If the interface does not support this configuration, the system displays a configuration failure message.

NOTE:
  • A queue profile that defines the queue length using the queue length command cannot be applied to Layer 2 FE interfaces and Layer 2 GE interfaces.
  • When a queue profile is applied to a LAN-side interface, the queue length can be set to an integer in the range of 1 to 25. If the queue length on the device is set to be larger than 25, the system displays the following error message:
    Error: The queue length of this profile exceeds the upper limit.

If you run the queue length command multiple times in the same queue profile view, only the latest configuration takes effect.

Example

# Create a queue profile named hello-world and set the length of queues 0 and 1 to 4096 bytes.

<Huawei> system-view
[Huawei] qos queue-profile hello-world
[Huawei-qos-queue-profile-hello-world] queue 0 to 1 length bytes 4096

queue-length

Function

The queue-length command sets the maximum length of a queue in a traffic behavior.

The undo queue-length command restores the default length of a queue.

By default, a queue can store a maximum of 131072 bytes or 64 packets.

Format

queue-length { bytes bytes-value | packets packets-value }*

undo queue-length

Parameters

Parameter

Description

Value

bytes bytes-value

Specifies the maximum number of bytes buffered in a queue.

The value is an integer that ranges from 2048 to 2097152.

packets packets-value

Specifies the maximum number of packets buffered in a queue.

The value is an integer that ranges from 1 to 1024.

Views

Traffic behavior view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The queue-length command is used to set the maximum length of a queue. The queue length affects queue traffic shaping, congestion management, and congestion avoidance. If the number of packets in a queue reaches the maximum value, the queue directly discards the packets. A longer queue buffers more packets but introduces a longer delay. If congestion occurs on a network intermittently, buffering more packets prevents unnecessary packet loss. If congestion always occurs on a network, increasing the queue length cannot solve the problem. You need to increase the bandwidth.

Prerequisites

The queue scheduling mode has been configured using the queue ef, queue af or queue wfq command.

Precautions

The queue length and drop method can only be configured in a traffic behavior of a traffic policy on the outbound WAN interface of the device.

The queue length and drop method can only be configured in a traffic behavior of a traffic policy on the outbound WAN interface of the device.

If you run the queue-length command multiple times in the same traffic behavior view, only the latest configuration takes effect.

Example

# Configure AF in the traffic behavior database, set the minimum assured bandwidth to 200 kbit/s, and set the queue length to 16 packets.

<Huawei> system-view
[Huawei] traffic behavior database
[Huawei-behavior-database] queue af bandwidth 200
[Huawei-behavior-database] queue-length packets 16

queue llq

Function

The queue llq command configures low latency queuing (LLQ) for packets of a certain type and set the maximum bandwidth.

The undo queue llq command cancels the configuration.

By default, LLQ is not configured for packets of a certain type.

Format

queue llq bandwidth { bandwidth [ cbs cbs-value ] | pct percentage [ cbs cbs-value ] }

undo queue llq

Parameters

Parameter

Description

Value

bandwidth

Specifies the maximum bandwidth for LLQ queues.

The value is an integer that ranges from 8 to 4294967295, in kbit/s.

cbs cbs-value

Specifies the committed burst size (CBS).

The value is an integer that ranges from 32 to 4294967295, in bytes.

By default, the CBS value is 25 times the value of bandwidth.

pct percentage

Specifies the percentage of the maximum bandwidth to the available bandwidth on an interface.

The value is an integer that ranges from 1 to 100.

Views

Traffic behavior view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The device provides the following types of queues for user-defined traffic classifiers:
  • Assured Forwarding (AF) queues
  • Expedited Forwarding (EF) queues
  • Best Effort (BE) queues
  • Low Latency queuing (LLQ) queues

LLQ queues are special type of EF queues and has shorter delay.

Follow-up Procedure

Create a traffic classifier and a traffic policy, bind the traffic classifier to the traffic behavior in the traffic policy, and then apply the traffic policy.

Precautions

LLQ can only be configured in a traffic behavior of a traffic policy on the outbound WAN-side interface of the device.

A traffic policy containing a traffic behavior and a drop profile cannot be used on an interface.

You cannot use the queue-length command to set the length for LLQ queues.

A low drop probability is ensured only when the traffic rate of LLQ queues falls below the maximum bandwidth.

If AF, EF, LLQ are configured in traffic behaviors bound to a traffic policy, the sum of bandwidth values for AF, EF, LLQ queues must be smaller than or equal to the available bandwidth of the interface to which the traffic policy is applied. When you use the bandwidth percentage to set the maximum bandwidth, the available bandwidth is as follows:
  • If the qos gts or qos gts adaptation-profile command is not used on an interface:
    • The available bandwidth is the actual physical bandwidth of a physical interface. If the qos lr command is used on the physical interface, the available bandwidth is the actual bandwidth of the interface multiplied by the configured percentage of the rate for sending packets to the interface bandwidth.
    • The available bandwidth of a tunnel interface is 1 Gbit/s.
    • The available bandwidth of a logical interface such as the Eth-Trunk, that is bundled by multiple interfaces or sub-interfaces is the total bandwidth of all bundled interfaces or sub-interfaces.
    • The available bandwidth of the dialer interface is the actual bandwidth of a bound physical interface or the sum of bandwidth of multiple bound physical interfaces.
  • If the qos gts or qos gts adaptation-profile command is used on an interface, the available bandwidth is the CIR value.
NOTE:
  • If the queue llq command has been used in a traffic behavior, you cannot use the queue ef, queue af, queue wfq, gts (traffic behavior view), or gts adaptation-profile command in the traffic behavior.
  • When a virtual template interface is bound to L2TP services, the percentage of the maximum bandwidth to the available bandwidth cannot be set on the virtual template interface.
  • If a traffic policy containing the traffic behavior is applied to an interface, the trust command does not take effect on the interface.
  • A maximum of four EF and LLQ queues are allowed in a traffic behavior of a traffic policy. Packets in EF or LLQ queues are scheduled in SP mode. Packets in AF queues and Weighted Fair Queuing (WFQ) queues are scheduled only after packets in EF or LLQ queues are scheduled. Packets in EF or LLQ queues are scheduled in SP mode according to the sequence in which queues were configured. Packets in the queue that was configured first are scheduled first.

If you run the queue llq command multiple times in the same traffic behavior view, only the latest configuration takes effect.

Example

# Configure LLQ for the traffic behavior database and set the maximum bandwidth to 1000 kbit/s.

<Huawei> system-view
[Huawei] traffic behavior database
[Huawei-behavior-database] queue llq bandwidth 1000

queue weight

Function

The queue weight command sets the weight of a queue.

The undo queue weight command restores the default weight of a queue.

By default, the weight of a queue is 10.

Format

queue { start-queue-index [ to end-queue-index ] } &<1-10> weight weight-value

undo queue { start-queue-index [ to end-queue-index ] } &<1-10> weight

Parameters

Parameter

Description

Value

start-queue-index [ to end-queue-index ]

Specifies the index of a queue.
  • start-queue-index specifies the index of the first queue. The value is an integer that ranges from 0 to 7.
  • end-queue-index specifies the index of the last queue. The value is an integer that ranges from 0 to 7.
If to end-queue-index is not specified, the weight is configured for only the queue specified by start-queue-index.

-

weight weight-value

Specifies the queue weight.

The value is an integer that ranges from 1 to 100.

Views

Queue profile view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Packets in queues are scheduled unevenly according to different service requirements. When Deficit Round Robin (DRR), Weighted Round Robin (WRR), or Weighted Fair Queuing (WFQ) scheduling is used, packets in queues are scheduled based on queue weights. Packets in queues with a greater weight are scheduled more times.

Prerequisites

A scheduling mode has been configured by using the schedule command.

Follow-up Procedure

Run the qos queue-profile (interface view) command to bind the queue profile to an interface.

Precautions

If PQ scheduling is used, packets in queues with lower priorities are processed only after all the packets in queues with higher priority are processed. Therefore, the weight cannot be set for these queues.

When you modify the weight in the queue profile bound to an interface, the modification is synchronized to the interface automatically if the interface supports this configuration. If the interface does not support this configuration, the system displays a configuration failure message.

NOTE:
  • A queue profile that defines the queue weight using the queue weight command cannot be applied to Layer 2 FE interfaces Layer 2 GE interfaces.

If you run the queue weight command multiple times in the same queue profile view, only the latest configuration takes effect.

Example

# Create a queue profile named hello-world and set the scheduling mode of queues 0 to 3 to WRR, the weight of queues 0 and 1 to 20, and the weight of queues 2 and 3 to 30.

<Huawei> system-view
[Huawei] qos queue-profile hello-world
[Huawei-qos-queue-profile-hello-world] schedule wrr 0 to 3
[Huawei-qos-queue-profile-hello-world] queue 0 to 1 weight 20
[Huawei-qos-queue-profile-hello-world] queue 2 to 3 weight 30

queue wfq

Function

Using the queue wfq command configures the device to send packets matching the default traffic classifier to BE queues in WFQ mode and sets the number of queues.

The undo queue wfq command cancels the configuration.

By default, the device is not configured to send packets matching the default traffic classifier to BE queues in WFQ mode.

Format

queue wfq [ queue-number total-queue-number ]

undo queue wfq

Parameters

Parameter

Description

Value

queue-number total-queue-number

Specifies the number of BE queues in WFQ mode.

If this parameter is not specified, one BE queue is used.

The value is 8, 16, 32, or 64.

Views

Traffic behavior view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The device provides the following types of queues for user-defined traffic classifiers:
  • AF queues
  • EF queues
  • BE queues
  • LLQ queues

After a traffic policy containing AF and EF is applied to an interface, AF, LLQ, and EF queues occupy some bandwidth of the interface and other packets enter BE queues. The device schedules packets in BE queues in WFQ mode and evenly allocates bandwidth to BE queues according to the IP precedence, and source and destination IP addresses. When a greater number of queues is set, WFQ allocates bandwidth more evenly but more resources are occupied.

WFQ is applied to the services insensitive to the delay and packet loss, for example, Internet access services.

Follow-up Procedure

Create a traffic policy, and bind the traffic classifier and the traffic behavior to the traffic policy, and apply the traffic policy to the interface.

Precautions

A traffic policy containing BE can be only be applied to the outbound direction on a WAN-side interface.

A traffic policy containing BE and a queue profile cannot be applied to an interface simultaneously.

If the traffic policy bound to the traffic behavior containing queue wfq is applied to an interface:
  • If the trust command is not used (the interface priority is trusted), priorities of packets entering the same interface are changed to the same value. Packets still enter queues according to the WFQ algorithm, but the packets are scheduled evenly.
  • If the trust command is used, packet priorities are changed. Packets still enter queues, but are scheduled based on changed priorities because the WFQ algorithm allocates bandwidth based on packet priorities.
NOTE:
  • If the queue wfq command has been used in a traffic behavior, you cannot use the queue ef, queue af, or queue llq command in the traffic behavior.

  • BE queues in WFQ mode use the remaining bandwidth of AF, LLQ, and EF queues; therefore, the traffic behavior must be bound to the default traffic classifier defined by the system. The remaining bandwidth is obtained by subtracting the minimum bandwidth and the maximum bandwidth from the interface bandwidth. In addition, the binding between the default traffic classifier and the traffic behavior must be configured last in the traffic policy so that all the packets in BE queues match this traffic classifier.

If you run the queue wfq command in the same traffic classifier view multiple times, only the latest configuration takes effect.

Example

# Configure WFQ for the default traffic classifier bound to the traffic behavior database and set the number of queues to 16.

<Huawei> system-view
[Huawei] traffic behavior database
[Huawei-behavior-database] queue wfq queue-number 16

reset qos queue statistics

Function

The reset qos queue statistics command clears queue-based traffic statistics on an interface.

Format

reset qos queue statistics interface interface-type interface-number [ queue queue-index ]

reset qos queue statistics interface virtual-template vt-number virtual-access va-number [ queue queue-index ]

Parameters

Parameter

Description

Value

interface interface-type interface-number

Clears queue-based traffic statistics on a specified interface.
  • interface-type specifies the type of the interface.

  • interface-number specifies the number of the interface.

-

virtual-template vt-number

Displays queue-based traffic statistics on a specified virtual template interface. vt-number specifies the number of the virtual template interface.

The value is an integer that ranges from 0 to 1023.

virtual-access va-number

Displays queue-based traffic statistics on a specified virtual access interface. va-number specifies the number of the virtual access interface.

The value is an integer that ranges from 0 to 1023.

queue queue-index

Displays statistics on the queue with a specified index.

The value is an integer that ranges from 0 to 7.

Views

User view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

To collect queue-based statistics within a certain period, run the reset qos queue statistics command to clear the existing statistics first.

Precautions

Queue-based statistics cannot be restored after you clear them. Therefore, exercise caution when you run the command.

Example

# Clear queue-based traffic statistics on Eth0/0/1.
<Huawei> reset qos queue statistics interface ethernet 0/0/1

schedule

Function

The schedule command configures a scheduling mode between queues in a queue profile.

The undo schedule command restores the default scheduling mode between queues in a queue profile.

By default, an interface is not bound to any queue profile; all the queues on the LAN side use WRR; Ethernet WAN interfaces do not use queue scheduling, and other WAN interfaces use WFQ.

Format

In the queue profile bound to WAN-side interfaces:

schedule { pq start-queue-index [ to end-queue-index ] | wfq start-queue-index [ to end-queue-index ] }*

undo schedule

In the queue profile bound to LAN-side interfaces:

schedule { pq start-queue-index [ to end-queue-index ] | drr start-queue-index [ to end-queue-index ] | wrr start-queue-index [ to end-queue-index ] }*

undo schedule

Parameters

Parameter

Description

Value

pq

Indicates PQ scheduling.

-

drr

Indicates Deficit Round Robin (DRR) scheduling.

-

wrr

Indicates Weighted Round Robin (WRR) scheduling.

-

wfq

Indicates Weighted Fair Queuing (WFQ) scheduling.

-

start-queue-index [ to end-queue-index ]

Specifies the index of a queue.
  • start-queue-index specifies the index of the first queue.
  • end-queue-index specifies the index of the last queue.
If to end-queue-index is not specified, the scheduling mode is configured for only the queue specified by start-queue-index.

start-queue-index and end-queue-index are integers that range from 0 to 7. A larger value indicates a higher priority of a queue.

NOTE:
When a queue profile applies to a Layer 2 FE interface or Layer 2 GE interface of the device, start-queue-index is an integer that ranges from 0 to 3. A larger value indicates a higher priority of a queue.

Views

Queue profile view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

When congestion occurs on a network intermittently, congestion management needs to be performed to provide high QoS for delay-sensitive services. Congestion management is implemented by using queue scheduling technologies.

When the network is congested, you can configure a scheduling mode for a queue so that the delay and jitter of various service packets can be adjusted in the following manners: (item list) The packets of delay-sensitive services, such as the video service and the voice service, can be processed preferentially. Among the delay-insensitive services, such as the email service, the packets with the same priority are processed equally and the packets with different priorities are processed based on their weights.

Follow-up Procedure

Run the qos queue-profile (interface view) command to bind the queue profile to an interface.

Precautions

When you modify the scheduling mode in the queue profile bound to an interface, the modification is synchronized to the interface automatically if the interface supports this configuration. If the interface does not support this configuration, the system displays a configuration failure message.

WAN-side and LAN-side interfaces of the device support different scheduling modes. When the schedule command used in the queue profile view is not bound to any interface, all scheduling modes can be configured. If the schedule command is used in the queue profile bound to an interface, the system displays an error message when you configure a scheduling mode denied by the interface. Table 1 shows the scheduling modes supported by LAN-side interfaces and WAN-side interfaces.

Table 15-18  Scheduling modes supported by each interface
Interface Scheduling Mode
LAN interface
  • PQ
  • DRR
  • WRR
  • PQ+DRR
  • PQ+WRR
WAN interface
  • PQ
  • WFQ
  • PQ+WFQ
The mixed scheduling mode indicates that some queues use PQ scheduling and some queues use other scheduling modes. PQ scheduling can be configured for one queue with the highest priority or multiple queues with consecutive higher priorities.
  • When a queue uses PQ scheduling, other queues whose priorities are higher than the priority of this queue also use PQ scheduling.

  • When a queue uses non-PQ scheduling, other queues whose priorities are lower than the priority of this queue also use this scheduling mode.

A queue can use only one scheduling mode. If you set multiple scheduling modes for a queue, only the latest configuration takes effect.

Example

# Create a queue profile named hello-world and set the scheduling mode of queues 0 to 3 to WRR.

<Huawei> system-view
[Huawei] qos queue-profile hello-world
[Huawei-qos-queue-profile-hello-world] schedule wrr 0 to 3

wred

Function

The wred command configures a WRED drop profile based on DSCP or IP priorities.

By default, a WRED drop profile based on IP priorities is used.

Format

wred { dscp | ip-precedence }

Parameters

Parameter

Description

Value

dscp

Indicates that a WRED drop profile based on DSCP priorities is used.

-

ip-precedence

Indicates that a WRED drop profile based on IP precedences is used.

-

Views

Drop profile view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

A drop profile defines WRED parameters for queues and is used to implement congestion avoidance for queues bound to the drop profile.

The device supports a WRED drop profile based on DSCP or IP priorities:
  • The value of an IP priority ranges from 0 to 7.
  • The value of a DSCP priority ranges from 0 to 63.
  • Eight DSCP priorities correspond to one IP priority.
WRED based on DSCP priorities differentiates services more refinedly.

Follow-up Procedure

Run the dscp discard-percentage or ip-precedence discard-percentage command to configure a WRED drop profile based on DSCP priorities or IP precedences.

Precautions

If WRED parameters have been configured in the drop profile:

  • If the priority specified by the wred command is different from the priority used by the WRED drop profile, the WRED drop profile uses the priority specified by the wred command and default values of WRED parameters are restored: The lower drop threshold is 30%, the upper drop threshold is 100%, and the maximum drop probability is 10%.
  • If the priority specified by the wred command is the same as the priority used by the WRED drop profile, default values of WRED parameters are not restored.

Example

# Configure a WRED drop profile based on DSCP priorities and set default WRED parameters.

<Huawei> system-view
[Huawei] drop-profile drop-profile1
[Huawei-drop-profile-drop-profile1] wred dscp
Translation
Download
Updated: 2019-05-29

Document ID: EDOC1000097293

Views: 48517

Downloads: 102

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next