xStack Gigabit Layer 3 Switch Command Line Interface Manual
DGS-3324SRi:4#show bandwidth_control 1:1-1:10
Command: show bandwidth_control 1:1-1:10
Bandwidth Control Table
Port RX Rate (Mbit/sec) TX_RATE (Mbit/sec)
---- ------------------------ ----------------------
1:1 no_limit 10
1:2 no_limit 10
1:3 no_limit 10
1:4 no_limit 10
1:5 no_limit 10
1:6 no_limit 10
1:7 no_limit 10
1:8 no_limit 10
1:9 no_limit 10
1:10 no_limit 10
DGS-3324SRi:4#
config scheduling
Purpose
Used to configure traffic scheduling for each of the Switch’s
hardware priority classes.
Syntax
config scheduling <class_id 0-6> {max_packet <value 0-15>}
Description
The Switch contains seven hardware classes of service per
device. The Switch’s default settings draw down seven hardware
classes of service in order, from the highest priority class (Class 6)
to the lowest priority class (Class 0). Starting with the highest
priority class (Class 6), the highest priority class will transmit all of
the packets and empty its buffer before allowing the next lower
priority class to transmit its packets. The next highest priority class
will empty before proceeding to the next class and so on. Lower
priority classes are allowed to transmit only if the higher priority
classes in the buffer are completely emptied. Packets in the higher
priority classes are always emptied before any in the lower priority
classes.
The default settings for QoS scheduling employ this strict priority
scheme to empty priority classes.
The
config scheduling
command can be used to specify the
weighted round-robin (
WRR
) rotation by which these seven
hardware priority classes of service are reduced. To use a
weighted round-robin (
WRR
) scheme, the
max_packets
parameters must not have a value of zero (
0
). (See
Combination
Queue
below.)
The
max_packet
parameter allows you to specify the maximum
number of packets a given priority class can transmit per weighted
round-robin (
WRR
) scheduling cycle. This provides for a
controllable CoS behavior while allowing for other classes to
empty as well. A value between 0 and 15 packets can be specified
per priority queue.
106
