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

Applying a Traffic Template, Example of Valid Traffic Template with Remapped Queue

Page 246 highlights

Quality of Service (QoS): Managing Bandwidth More Effectively QoS Queue Configuration ProCurve(cfg-tcgt-example)# map-traffic-group 2 priority 0 ProCurve(cfg-tcgt-example)# show qos traffic-template example TRAFFIC-TEMPLATE: example Status : Valid -------1 2 3 4 ------------1,2 3,0 4,5 6,7 background-tcg best-effort-tcg controlled-load-tcg control-tcg Figure 5-35. Example of Valid Traffic Template with Remapped Queue After modifying a traffic template, you must apply it to the switch to activate the new mapping. See "Applying a Traffic Template", below. Applying a Traffic Template After creating a traffic template with the desired options, you must apply it to the module or switch (in the global config context). Traffic templates must be applied to the entire switch, so enter all or the entire range of ports. Syntax: interface policy traffic-template Applies the specified traffic template to the module or switch and forces a write memory and reboot. All ports in the module or switch (1-N) must be specified, or just enter the parameter "all". ProCurve(config)# int all ProCurve(eth-1-24)# policy traffic-template example This command will modify the current running configuration, will execute 'write memory' to replace the startup configuration, then reboot. Continue? [y/n] y The traffic template named "example" is applied to all the ports in the module or switch. Figure 5-36. Example of Applying a Traffic Template to a Switch Traffic templates can only be applied by rebooting the switch. If you enter "n", the traffic template is not applied. 5-70

  • 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-70
Quality of Service (QoS): Managing Bandwidth More Effectively
QoS Queue Configuration
Figure 5-35.
Example of Valid Traffic Template with Remapped Queue
After modifying a traffic template, you must apply it to the switch to activate
the new mapping. See “Applying a Traffic Template”, below.
Applying a Traffic Template
After creating a traffic template with the desired options, you must apply it to
the module or switch (in the global config context). Traffic templates must be
applied to the entire switch, so enter
all
or the entire range of ports.
Figure 5-36.
Example of Applying a Traffic Template to a Switch
Traffic templates can only be applied by rebooting the switch. If you enter “
n
”,
the traffic template is not applied.
ProCurve(cfg-tcgt-example)# map-traffic-group 2 priority 0
ProCurve(cfg-tcgt-example)# show qos traffic-template example
TRAFFIC-TEMPLATE:
example
Status
:
Valid
--------
-------------
--------------------
1
1,2
background-tcg
2
3,0
best-effort-tcg
3
4,5
controlled-load-tcg
4
6,7
control-tcg
Syntax:
interface <1-totalnumports | all> policy traffic-template <
namestring
>
Applies the specified traffic template to the module or switch and
forces a write memory and reboot. All ports in the module or switch
(1-N) must be specified, or just enter the parameter “
all
”.
ProCurve(config)# int all
ProCurve(eth-1-24)# policy traffic-template example
This command will modify the current running configuration,
will execute ‘write memory’ to replace the startup configu-
ration, then reboot.
Continue? [y/n] y
The traffic template named “example”
is applied to all the ports in the module or switch.