Netgear CSM4532 Software Administration Manual - Page 233

CoS Queuing Function and Behavior

Page 233 highlights

queues of the port. If a delay is necessary, packets are held in the queue until the scheduler authorizes the queue for transmission. As queues become full, packets have no place to be held for transmission and get dropped by the device. The drop precedence of a packet is an indication of whether the packet is more or less likely to be dropped during times of queue congestion. Often referred to as packet coloring, a low drop precedence (green) allows the packet to be transmitted under most circumstances, a higher drop precedence (yellow) subjects the packet to dropping when bursts become excessive, while the highest drop precedence (red) discards the packet whenever the queue is congested. In some hardware implementations, the queue depth can be managed using tail dropping or a weighted random early discard, or WRED, technique. These methods often use customizable threshold parameters that are specified on a per-drop-precedence basis. The switch supports Differentiated Services (DiffServ), which allows traffic to be classified into streams and given certain QoS treatment in accordance with defined per-hop behaviors. However, the DiffServ feature does not offer direct configuration of the hardware COS queue resources. The COS Queuing feature allows the switch administrator to directly configure certain aspects of device queuing to provide the desired QoS behavior for different types of network traffic when the complexities of DiffServ are not required. The priority of a packet arriving at an interface can be used to steer the packet to the appropriate outbound COS queue through a mapping table. With the CoS queuing feature, COS queue characteristics such as minimum guaranteed bandwidth, transmission rate shaping, etc. can be configured at the queue (or port) level. With support for the multistage scheduling architecture, the COS queue feature provides a method to configure Traffic Class Groups (TCGs) to extend the COS queue management. Multiple COS queues can be mapped to a single TCG. Each TCG can have a configured minimum guaranteed bandwidth allocation and a scheduling algorithm similar to the COS queue configuration. The TCG scheduling and bandwidth enforcement occurs after the COS queue scheduling and bandwidth enforcement is performed. Therefore all COS queues mapped to the same TCG share the scheduling and bandwidth properties of the TCG. 9.4.1. CoS Queuing Function and Behavior Like CoS mapping, CoS queuing uses the concept of trusted and untrusted ports. CoS queuing builds on includes user-configurable settings that affect hardware queue operation. 9.4.1.1. Trusted Port Queue Mappings A trusted port is one that takes at face value a certain priority designation within arriving packets. Specifically, a port may be configured to trust one of the following packet fields: • 802.1p User Priority • IP Precedence • IP DSCP Packets arriving at the port ingress are inspected and their trusted field value is used to designate the COS queue that the packet is placed when forwarded to the appropriate egress port. A mapping table associates the trusted field value with the desired COS queue. NETGEAR M4500 Series Switches Software Administration Manual 233

  • 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
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251

NETGEAR M4500 Series Switches Software Administration Manual
233
queues of the port. If a delay is necessary, packets are held in the queue until the scheduler authorizes the
queue for transmission. As queues become full, packets have no place to be held for transmission and get
dropped by the device.
The drop precedence of a packet is an indication of whether the packet is more or less likely to be dropped
during times of queue congestion. Often referred to as packet coloring, a low drop precedence (green) allows
the packet to be transmitted under most circumstances, a higher drop precedence (yellow) subjects the
packet to dropping when bursts become excessive, while the highest drop precedence (red) discards the
packet whenever the queue is congested. In some hardware
implementations,
the queue depth can be
managed using tail dropping or a weighted random early discard, or WRED, technique. These methods often
use customizable threshold parameters that are specified on a per-drop-precedence basis.
The switch supports Differentiated Services (DiffServ), which allows traffic to be classified into streams and
given certain QoS treatment in accordance with defined per-hop behaviors. However, the DiffServ feature
does not offer direct configuration of the hardware COS queue resources.
The COS Queuing feature allows the switch
administrator
to directly configure certain aspects of device queuing
to provide the desired QoS behavior for different types of network traffic when the complexities of DiffServ
are not required. The priority of a packet arriving at an interface can be used to steer the packet to the
appropriate outbound COS queue through a mapping table. With the CoS queuing feature, COS queue
characteristics
such as minimum guaranteed bandwidth, transmission rate shaping, etc. can be configured at
the queue (or port) level.
With support for the multistage scheduling architecture, the COS queue feature provides a method to
configure Traffic Class Groups (TCGs) to extend the COS queue management. Multiple COS queues can be
mapped to a single TCG. Each TCG can have a configured minimum guaranteed bandwidth allocation and a
scheduling algorithm similar to the COS queue configuration. The TCG scheduling and bandwidth enforcement
occurs after the COS queue scheduling and bandwidth enforcement is performed. Therefore all COS queues
mapped to the same TCG share the scheduling and bandwidth properties of the TCG.
9.4.1.
CoS Queuing Function and Behavior
Like CoS mapping, CoS queuing uses the concept of trusted and untrusted ports. CoS queuing builds on
includes user-configurable settings that affect hardware queue operation.
9.4.1.1.
Trusted Port Queue Mappings
A trusted port is one that takes at face value a certain priority designation within arriving packets. Specifically, a
port may be configured to trust one of the following packet fields:
802.1p User Priority
IP Precedence
IP DSCP
Packets arriving at the port ingress are inspected and their trusted field value is used to designate the COS
queue that the packet is placed when forwarded to the appropriate egress port. A mapping table associates
the trusted field value with the desired COS queue.