Qos commands affected by priority queues, Priority-based rate shaping, Weighted random early discard (wred) – Brocade Multi-Service IronWare QoS and Traffic Management Configuration Guide (Supporting R05.6.00) User Manual
Page 171: Qos commands affected by priority, Queues
Multi-Service IronWare QoS and Traffic Management Configuration Guide
157
53-1003037-02
QoS commands affected by priority queues
4
QoS commands affected by priority queues
•
Priority-based Rate Shaping
•
Weighted Random Early Discard (WRED)
•
Weighted-based Scheduling and Mixed Strict Priority
•
CPU Copy Queue
•
Traffic Manager Statistics
Priority-based rate shaping
If the user specifies a priority of 4-7 when the max-tm-queues parameter is configured using 4
queues, the qos shaper priority command is accepted, but a warning message is displayed.
The following example displays the qos shaper priority command configured with a priority 4
shaper.
Brocade(config-if-eth-16/1)# qos shaper priority 4 1000000
Warn: current max TM queues is 4-configuration of priority 4-7 will not have any
effect.
NOTE
If a priority 5 shaper is already configured, and the max-tm-queues parameter changes from 8 to 4
queues and is reloaded, then the priority 5 shaper configuration line is still displayed. The priority
shaper 5 will not take effect.
Weighted Random Early Discard (WRED)
When WRED is enabled for a queue type of any forwarding queue, it will receive a warning message
that is similar to when the priority-based rate shaping command is configured. Refer to
on page 157 for more information.
The following example displays enabling WRED for the forwarding queues with a queue type of 6.
Brocade(config)#qos queue-type 6 wred enable
Warn: current max TM queues is 4-configuration of queue-type 4-7 will not have any
effect.
NOTE
If the system-init max-tm-queues 4 command is configured, the user is able to configure similar
WRED parameters, such as Average weight, Max Instantaneous queue size, Drop Precedence, etc.
for all priorities. The default values of all WRED parameters (refer to
on page 148) is only
effective when queue-type 0-3 is used.
Weighted-based scheduling and
mixed strict priority
When the max-tm-queues parameter is configured with 8 or 4 queues, the qos scheduler weighted
command and qos scheduler mixed command will still take the same number of weight values, but
the unnecessary priority values are ignored.