D-Link DES-3010G Reference Manual - Page 78

config scheduling, config scheduling <class_id 0-3> {weight <value 1-55}, weight

Page 78 highlights

DES-3010F / DES-3010G / DES-3018 / DES-3026 Layer 2 Switch CLI Reference Manual The QoS commands in the Command Line Interface (CLI) are listed (along with the appropriate parameters) in the following table. Command config scheduling show scheduling config 802.1p user_priority show 802.1p user_priority config 802.1p default_priority show 802.1p default_priority config scheduling_mechanism show scheduling_mechanism config bandwidth_control show bandwidth_control Parameters weight [ | all] {} [strict | weight_fair] [] {rx_rate [no_limit | ] | tx_rate [no_limit ]} {} Each command is listed, in detail, in the following sections. config scheduling Purpose Syntax Description Used to configure traffic scheduling for each of the Switch's QoS queues. config scheduling {weight

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147

DES-3010F / DES-3010G / DES-3018 / DES-3026 Layer 2 Switch CLI Reference Manual
The QoS commands in the Command Line Interface (CLI) are listed (along with the appropriate parameters) in the following
table.
Command
Parameters
config scheduling
<class_id 0-3> weight <value 1-55>
show scheduling
config 802.1p user_priority
<priority 0-7> <class_id 0-3>
show 802.1p user_priority
config 802.1p default_priority
[<portlist> | all] <priority 0-7>
show 802.1p default_priority
{<portlist>}
config scheduling_mechanism
[strict | weight_fair]
show scheduling_mechanism
config bandwidth_control
[<portlist>] {rx_rate [no_limit | <value 64-1024000>] |
tx_rate [no_limit <value 64-1024000>]}
show bandwidth_control
{<portlist>}
Each command is listed, in detail, in the following sections.
config scheduling
Purpose
Used to configure traffic scheduling for each of the Switch’s QoS
queues.
Syntax
config scheduling <class_id 0-3> {weight <value 1-55}
Description
The Switch contains four hardware priority classes of service per
device. The Switch’s default settings draw down the four hardware
classes of service in order, from the highest class (Class 3) to the
lowest class (Class 0). Starting with the highest priority class of
service (Class 3), the highest priority class of service will transmit all
of the packets and empty its buffer before allowing the next lower
priority class of service to transmit its packets. The next highest
priority class of service will empty before proceeding to the next
class of service and so on. Lower priority classes of service are
allowed to transmit only if
the higher priority classes of service in the
buffer are completely emptied. Packets in the higher priority classes
of service are always emptied before any in the lower priority
classes of service regardless of latency or volume of the lower
priority classes of service.
The default settings for QoS scheduling employ this strict priority
scheme to empty priority classes of service.
The
config scheduling
command can be used to specify the round
robin rotation by which these four hardware priority classes of
service are reduced.
The
weight
parameter allows you to specify the maximum number
of packets a given priority classes of service can transmit before
allowing the next lowest priority queue to begin transmitting its
packets. A value between 0 and 55 packets can be specified. For
example, if a value of 5 is specified, then the highest priority class of
service (queue 3) will be allowed to transmit 5 packets. Then the
next lower priority class of service (queue 2) will be allowed to
transmit 5 packets, and so on, until all of the classes of service have
transmitted 5 packets. The process will then repeat.
76