Defining a traffic behavior
To define a traffic behavior, create the traffic behavior first and then configure QoS attributes in traffic behavior view.
Configure AF and the minimum guaranteed bandwidth
When you configure AF and the minimum guaranteed bandwidth, follow these guidelines:
You can apply this traffic behavior only to the outgoing traffic of an interface or ATM PVC.
You cannot configure the queue ef command together with the queue af command in the same traffic behavior.
To reference both the queue ef command and the queue af command in a policy, you must configure them in the same unit (either bandwidth or percentage). If not, your referencing attempts will fail.
To configure AF and the minimum guaranteed bandwidth:
Step | Command | Remarks |
---|---|---|
1. Enter system view. | system-view | N/A |
2. Create a traffic behavior and enter traffic behavior view. | traffic behavior behavior-name | The specified behavior name cannot be the name of any system-defined behavior. |
3. Configure AF and the minimum guaranteed bandwidth. | queue af bandwidth { bandwidth | pct percentage } | N/A |
Configuring EF and the maximum bandwidth
When you configure EF and the maximum bandwidth, follow these guidelines:
You cannot configure the queue ef command together with the any of the commands queue af, queue-length, and wred for a traffic behavior.
The default class cannot be associated with a traffic behavior including EF.
To reference both the queue ef command and the queue af command in a policy, you must configure them in the same unit (either bandwidth or percentage). If not, your referencing attempts will fail.
To configure EF and the maximum bandwidth:
Step | Command | Remarks |
---|---|---|
1. Enter system view. | system-view | N/A |
2. Create a traffic behavior and enter traffic behavior view. | traffic behavior behavior-name | The specified traffic behavior name cannot be the name of any system-defined behavior. |
3. Configure EF and the maximum bandwidth. | queue ef bandwidth { bandwidth [ cbs burst ] | pct percentage [ cbs-ratio ratio] } | N/A |
Configuring WFQ
To configure WFQ:
Step | Command | Remarks |
---|---|---|
1. Enter system view. | system-view | N/A |
2. Create a traffic behavior and enter traffic behavior view. | traffic behavior behavior-name | The specified traffic behavior name cannot be the name of any system-defined behavior. |
3. Configure WFQ. | queue wfq [ queue-number total-queue-number ] | N/A |
You can associate the traffic behavior that contains a WFQ action only with the default class.
Configuring the maximum queue size
Configure the maximum queue size and use tail drop.
To configure the maximum queue size:
Step | Command | Remarks |
---|---|---|
1. Enter system view. | system-view | N/A |
2. Create a traffic behavior and enter traffic behavior view. | traffic behavior behavior-name | The specified traffic behavior name cannot be the name of any system-defined behavior. |
3. Set the maximum queue size. | queue-length queue-length | N/A |
Check that the queue af command or the queue wfq command has been configured before you configure the queue-length command. Executing the undo queue af command or the undo queue wfq command cancels also the queue-length command.
Enabling WRED
When you enable WRED, follow these guidelines:
Before enabling WRED, configure the queue af command or queue wfq command.
The wred command and the queue-length command are mutually exclusive.
When WRED is disabled, other WRED configurations under it are deleted.
The WRED configuration in QoS policies overrides the WRED configuration directly configured on interfaces.
To use WRED drop:
Step | Command | Remarks |
---|---|---|
1. Enter system view. | system-view | N/A |
2. Create a traffic behavior and enter traffic behavior view. | traffic behavior behavior-name | The specified traffic behavior name cannot be the name of any system-defined behavior. |
3. Use WRED drop. | wred [ dscp | ip-precedence ] |
|
Configuring the exponent for WRED to calculate the average queue size
Before configuring the wred weighting-constant command, make sure the queue af command or the queue wfq command has been configured and the wred command has been used to enable WRED.
To configure the exponent for WRED to calculate the average queue size:
Step | Command | Remarks |
---|---|---|
1. Enter system view. | system-view | N/A |
2. Create a traffic behavior and enter traffic behavior view. | traffic behavior behavior-name | The specified traffic behavior name cannot be the name of any system-defined behavior. |
3. Configure the exponent for WRED to calculate the average queue size. | wred weighting-constant exponent | The default exponent is 9. |
Configuring the lower limit, upper limit, and drop probability denominator for each DSCP value in WRED
To perform this configuration, make sure DSCP-based WRED has been enabled with the wred dscp command.
Disabling WRED also removes the wred dscp command configuration.
Removing the queue af or queue wfq command configuration also removes the WRED drop-related parameters.
To configure the lower limit, upper limit, and drop probability denominator for a DSCP value in WRED:
Step | Command | Remarks |
---|---|---|
1. Enter system view. | system-view | N/A |
2. Create a traffic behavior and enter traffic behavior view. | traffic behavior behavior-name | The specified traffic behavior name cannot be the name of any system-defined behavior. |
3. Configure the lower limit, upper limit and drop probability denominator for a DSCP value in WRED. | wred dscp dscp-value low-limit low-limit high-limit high-limit [ discard-probability discard-prob ] | N/A |
dscp-value: DSCP value in the range of 0 to 63, which can also be any of the following keywords: ef, af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, cs1, cs2, cs3, cs4, cs5, cs6, cs7, and default.
Configuring the lower limit, upper limit, and drop probability denominator for each IP precedence value in WRED
To perform this configuration, make sure IP precedence-based WRED has been enabled with the wred ip-precedence command.
Disabling WRED also removes the wred ip-precedence command configuration
Removing the queue af or queue wfq command configuration also removes the WRED drop-related parameters.
To configure the lower limit, upper limit, and drop probability denominator for an IP precedence value in WRED:
Step | Command | Remarks |
---|---|---|
1. Enter system view. | system-view | N/A |
2. Create a traffic behavior and enter traffic behavior view. | traffic behavior behavior-name | The specified traffic behavior name cannot be the name of any system-defined behavior. |
3. Configure the lower limit, upper limit and drop probability denominator for an IP precedence value in WRED. | wred ip-precedence precedence low-limit low-limit high-limit high-limit [ discard-probability discard-prob ] | N/A |