Dell S5148F-ON OS10 Enterprise Edition User Guide Release 10.3.2E-R2 - Page 444

Strict priority queuing

Page 444 highlights

Honor DSCP priority on ingress traffic OS10(config)# policy-map policy-trust OS10(conf-pmap-qos)# class class-trust OS10(conf-pmap-c-qos)# trust diffserv View policy-map OS10(conf-pmap-c-qos)# do show policy-map Service-policy (qos) input: policy-trust Class-map (qos): class-trust trust diffserv Strict priority queuing OS10 uses queues for egress QoS policy-types. You can enable priorities to dequeue all packets from the assigned queue before servicing any other queues. When more than one queue is assigned strict priority, the highest number queue receives the highest priority. You can configure strict priority to any number of queues. By default, all queues schedule traffic per WDRR. You can use the priority command to assign the priority to a single unicast queue-this configuration supersedes the bandwidth percent configuration. A queue with priority enabled can starve other queues for the same egress interface. Consider the following when enabling priority queueing in S5148F-ON: • In a port, one H2 node and three H1 nodes are supported. The H1 node holds 8 unicast queues for data traffic, 8 unicast queues for control traffic, and 8 multicast queues for data traffic. • The H1 nodes mapped to data traffic are scheduled with DWRR and weight of 50 each. The H1 node mapped to control traffic is scheduled with strict priority. • The weights corresponding to each traffic class are applied at queue levels for both unicast and multicast queues. • The bandwidth distribution might go to a minimum of 50, based on the traffic flow in a port. This is determined by the weight of a particular traffic class and traffic type. • The bandwidth sharing based on ETS happens only between same type of queues. • You can enable strict priority queuing only for the same type of traffic. Create class-map 1 Create a class-map, and configure a name for the class-map in CONFIGURATION mode. class-map type queuing class-map-name 2 Configure a match criteria in CLASS-MAP mode. match queue queue-id Define a policy-map 1 Define a policy-map, and create a policy-map name CONFIGURATION mode. policy-map type queuing policy-map-name 2 Create a QoS class and configure a name for the policy-map in POLICY-MAP mode. class class-map-name 3 Set the scheduler as the strict priority in POLICY-MAP-CLASS-MAP mode. priority Apply policy-map 1 You can now apply the policy-map to the interface (INTERFACE mode) or all interfaces-SYSTEM-QOS mode. system qos OR interface ethernet node/slot/port[:subport] 2 Enter the output service-policy in SYSTEM-QOS mode or INTERFACE mode. service-policy {output} type {queuing} policy-map-name 444 Quality of service

  • 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
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416
  • 417
  • 418
  • 419
  • 420
  • 421
  • 422
  • 423
  • 424
  • 425
  • 426
  • 427
  • 428
  • 429
  • 430
  • 431
  • 432
  • 433
  • 434
  • 435
  • 436
  • 437
  • 438
  • 439
  • 440
  • 441
  • 442
  • 443
  • 444
  • 445
  • 446
  • 447
  • 448
  • 449
  • 450
  • 451
  • 452
  • 453
  • 454
  • 455
  • 456
  • 457
  • 458
  • 459
  • 460
  • 461
  • 462
  • 463
  • 464
  • 465
  • 466
  • 467
  • 468
  • 469
  • 470
  • 471
  • 472
  • 473
  • 474
  • 475
  • 476
  • 477
  • 478
  • 479
  • 480
  • 481
  • 482
  • 483
  • 484
  • 485
  • 486
  • 487
  • 488
  • 489
  • 490
  • 491
  • 492
  • 493
  • 494
  • 495
  • 496
  • 497
  • 498
  • 499
  • 500
  • 501
  • 502
  • 503
  • 504
  • 505
  • 506
  • 507
  • 508
  • 509
  • 510
  • 511
  • 512
  • 513
  • 514
  • 515
  • 516
  • 517
  • 518
  • 519
  • 520
  • 521
  • 522
  • 523
  • 524
  • 525
  • 526
  • 527
  • 528
  • 529
  • 530
  • 531
  • 532
  • 533
  • 534
  • 535
  • 536
  • 537
  • 538
  • 539
  • 540
  • 541
  • 542
  • 543
  • 544
  • 545
  • 546
  • 547
  • 548
  • 549
  • 550
  • 551
  • 552
  • 553
  • 554
  • 555
  • 556
  • 557
  • 558
  • 559
  • 560
  • 561
  • 562
  • 563
  • 564
  • 565
  • 566
  • 567
  • 568
  • 569
  • 570
  • 571
  • 572
  • 573
  • 574
  • 575
  • 576
  • 577
  • 578
  • 579
  • 580
  • 581
  • 582
  • 583
  • 584
  • 585
  • 586
  • 587

Honor DSCP priority on ingress
traffic
OS10(config)# policy-map policy-trust
OS10(conf-pmap-qos)# class class-trust
OS10(conf-pmap-c-qos)# trust diffserv
View policy-map
OS10(conf-pmap-c-qos)# do show policy-map
Service-policy (qos) input: policy-trust
Class-map (qos): class-trust
trust diffserv
Strict priority queuing
OS10 uses queues for egress QoS policy-types. You can enable priorities to dequeue all packets from the assigned queue before servicing
any other queues. When more than one queue is assigned strict priority, the highest number queue receives the highest priority. You can
configure
strict priority to any number of queues. By default, all queues schedule
traffic
per WDRR.
You can use the
priority
command to assign the priority to a single unicast queue—this
configuration
supersedes the
bandwidth
percent
configuration.
A queue with priority enabled can starve other queues for the same egress interface.
Consider the following when enabling priority queueing in S5148F-ON:
In a port, one H2 node and three H1 nodes are supported. The H1 node holds 8 unicast queues for data
traffic,
8 unicast queues for
control
traffic,
and 8 multicast queues for data
traffic.
The H1 nodes mapped to data
traffic
are scheduled with DWRR and weight of 50 each. The H1 node mapped to control
traffic
is
scheduled with strict priority.
The weights corresponding to each
traffic
class are applied at queue levels for both unicast and multicast queues.
The bandwidth distribution might go to a minimum of 50, based on the
traffic
flow
in a port. This is determined by the weight of a
particular
traffic
class and
traffic
type.
The bandwidth sharing based on ETS happens only between same type of queues.
You can enable strict priority queuing only for the same type of
traffic.
Create class-map
1
Create a class-map, and
configure
a name for the class-map in CONFIGURATION mode.
class-map type queuing
class-map-name
2
Configure
a match criteria in CLASS-MAP mode.
match queue
queue-id
Define
a policy-map
1
Define
a policy-map, and create a policy-map name CONFIGURATION mode.
policy-map type queuing
policy-map-name
2
Create a QoS class and
configure
a name for the policy-map in POLICY-MAP mode.
class
class-map-name
3
Set the scheduler as the strict priority in POLICY-MAP-CLASS-MAP mode.
priority
Apply policy-map
1
You can now apply the policy-map to the interface (INTERFACE mode) or all interfaces—SYSTEM-QOS mode.
system qos
OR
interface ethernet
node/slot/port[:subport]
2
Enter the output service-policy in SYSTEM-QOS mode or INTERFACE mode.
service-policy {output} type {queuing}
policy-map-name
444
Quality of service