HP 6120XG HP ProCurve Series 6120 Blade Switches Advanced Traffic Management G - Page 244

Configuring Traffic Groups Within a Traffic Template

Page 244 highlights

Quality of Service (QoS): Managing Bandwidth More Effectively QoS Queue Configuration You should always check the traffic template status using the show qos traffictemplate command to make sure that the template is valid. Invalid templates cannot be applied to ports. A traffic template will be invalid if the priorities are not mapped to one of the queues, for example, if you delete a priority from a queue and do not reassign it to another queue. If a template has been applied, it is considered to be in use and cannot be deleted. The show qos queue-config command displays the name of the currently assigned traffic template. If a template is not assigned to the switch ports and it is not a default template, it can be deleted. Configuring Traffic Groups Within a Traffic Template When in the traffic template context, you can modify traffic groups within that template by changing which priorities are assigned to queues, as well as setting other attributes. Syntax: [no] map-traffic-group [name ] [priority >] Allows configuration of traffic groups with a traffic template. The no form of the command removes a priority from the currently mapped queue. : ranges from 1 to the number of active queues, which can vary from 1 to 8 queues. name : Optional, a name that can be assigned to help identify the purpose of a particular traffic group. Maximum length is 40 characters. priority : Specifies which priorities are assigned to this queue. For example, priority 0-3 means that this traffic group maps priorities 0,1,2, and 3 to the specified queue. All priorities (between 0-7) must be mapped to a queue. Priority values cannot be repeated, for example, priority 2, 2, 4 is invalid. Moving a Priority From One Traffic Group to Another Typically, when modifying a traffic template, priorities are being reassigned to different queues. When moving a priority from one traffic group to another, you must first delete that priority from the traffic group it is currently mapped to (no map-traffic-group priority ) and then add it the desired traffic group. 5-68

  • 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
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288

5-68
Quality of Service (QoS): Managing Bandwidth More Effectively
QoS Queue Configuration
You should always check the traffic template status using the
show qos traffic-
template
command to make sure that the template is valid. Invalid templates
cannot be applied to ports. A traffic template will be invalid if the priorities
are not mapped to one of the queues, for example, if you delete a priority from
a queue and do not reassign it to another queue.
If a template has been applied, it is considered to be in use and cannot be
deleted. The
show qos queue-config
command displays the name of the cur-
rently assigned traffic template. If a template is not assigned to the switch
ports and it is not a default template, it can be deleted.
Configuring Traffic Groups Within a Traffic Template
When in the traffic template context, you can modify traffic groups within that
template by changing which priorities are assigned to queues, as well as setting
other attributes.
Moving a Priority From One Traffic Group to Another
Typically, when modifying a traffic template, priorities are being reassigned
to different queues. When moving a priority from one traffic group to another,
you must first delete that priority from the traffic group it is currently mapped
to (
no map-traffic-group <
queue-num
> priority <
priority-num
>
) and then add it the
desired traffic group.
Syntax:
[no] map-traffic-group <queue-num> [name <
namestring
>]
[priority <0, ..., 7>>]
Allows configuration of traffic groups with a traffic template.
The
no
form of the command removes a priority from the currently
mapped queue.
<queue-num>:
ranges from 1 to the number of active queues, which
can vary from 1 to 8 queues.
name <
namestring
>:
Optional, a name that can be assigned to help
identify the purpose of a particular traffic group. Maximum
length is 40 characters.
priority <0,...,7>:
Specifies which priorities are assigned to this
queue. For example, priority 0-3 means that this traffic group
maps priorities 0,1,2, and 3 to the specified queue. All priorities
(between 0-7) must be mapped to a queue.
Priority values cannot be repeated, for example,
priority 2, 2, 4
is
invalid.