Download Print this page

Nokia 7210 SAS OS Quality Of Service Manual

Service access switch.
Hide thumbs
   
1
2
Table of Contents
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

Advertisement

7210 SAS OS Quality of Service Guide7210 SAS-M7210 SAS-T7210 SAS-
Mxp7210 SAS-S7210 SAS-SxRelease 9.0.R8
7210 SERVICE ACCESS SWITCH
7210 SAS OS Quality of Service Guide
7210 SAS-M
7210 SAS-T
7210 SAS-Mxp
7210 SAS-S
7210 SAS-Sx
Release 9.0.R8
3HE11482AAAHTQZZA
Issue: 01
September 2017
Nokia — Proprietary and confidential.
Use pursuant to applicable agreements.

Advertisement

   Related Manuals for Nokia 7210 SAS OS

   Summary of Contents for Nokia 7210 SAS OS

  • Page 1

    7210 SAS OS Quality of Service Guide7210 SAS-M7210 SAS-T7210 SAS- Mxp7210 SAS-S7210 SAS-SxRelease 9.0.R8 7210 SERVICE ACCESS SWITCH 7210 SAS OS Quality of Service Guide 7210 SAS-M 7210 SAS-T 7210 SAS-Mxp 7210 SAS-S 7210 SAS-Sx Release 9.0.R8 3HE11482AAAHTQZZA Issue: 01 September 2017 Nokia —...

  • Page 2

    © 2013, 2016, 2017 Nokia. Contains proprietary/trade secret information which is the property of Nokia and must not be made available to, or copied or used by anyone outside Nokia without its written authorization. Not to be used or disclosed except in accordance with...

  • Page 3: Table Of Contents

    Table of Contents Preface..............................15 About This Guide..............................15 Audience ...............................16 List of Technical Publications ........................16 Technical Support ............................17 Getting Started............................19 In This Chapter ..............................19 Alcatel-Lucent 7210 SAS-Series Services Configuration Process ..............19 QoS Policies ............................21 In This Chapter ..............................21 QoS Overview ..............................21 Overview of QoS Policies on 7210 SAS-M and 7210 SAS-T in Access-uplink mode ........22 Overview of QoS Policies on 7210 SAS-M and 7210 SAS-T in network mode ..........25...

  • Page 4: Table Of Contents

    Table of Contents Service Egress QoS Policies on 7210 SAS-Mxp....................67 Access Egress QoS Policies on 7210 SAS-M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE Access Egress QoS Policies on 7210 SAS-Mxp ....................75 Access Egress QoS policy for SAP-based queuing mode on 7210 SAS-Mxp ...........75 Access Egress QoS policy for Port-based Queuing mode on 7210 SAS-Mxp ...........76 Buffer Pools on 7210 SAS-M and 7210 SAS-T ....................78 Buffer pool allocation - Per port MBS pool (7210 SAS-M and 7210 SAS-T) ..........78...

  • Page 5: Table Of Contents

    Table of Contents Modifying Port Level Egress-Rate Command .....................113 Removing Port Level Egress-Rate Command ....................113 Default Egress-Rate Values ........................114 Port Level Egress-Rate Command Reference ....................115 Command Hierarchies..........................115 Configuration Commands ........................115 Show Commands ...........................115 Command Descriptions ..........................116 Configuration Commands ........................116 Show Commands ...........................116 Frame Based Accounting ........................

  • Page 6: Table Of Contents

    Table of Contents Copying and Overwriting Network Policies ....................159 Editing QoS Policies............................160 Network QoS Policy Command Reference ......................161 Command Hierarchies..........................161 Configuration Commands ........................161 Configuration Commands (for 7210 SAS-M network mode operation) ..........161 Configuration Commands in 7210 SAS-T and 7210 SAS-Sx/S 1/10GE configured in network mode...162 Configuration Commands for 7210 SAS-Mxp ..................163 Configuration Commands in Access-uplink Mode .................164 Operational Commands (for network mode or access-uplink mode of operation) .........165...

  • Page 7: Table Of Contents

    Table of Contents Use of the keyword “multipoint” for default meter “11” ................231 Service Ingress Meter Selection Rules ....................234 Service Ingress Policy Configuration Considerations ................236 Resource Allocation for Service Ingress QoS policies ................237 Computation of resources used per SAP ingress policy ...............240 Basic Configurations............................244 Create Service Ingress QoS Policies ......................244 Service Ingress QoS Policy .........................244...

  • Page 8: Table Of Contents

    Table of Contents Configuration Commands for 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE network mode ..............................341 Operational Commands .........................341 Show Commands ...........................341 Configuration Commands..........................342 Generic Commands ..........................342 Access Egress Queue QoS Policy Commands ..................351 Access Egress QoS Policies for 7210 SAS-Mxp ................359 In This Section..............................359 Overview................................359 Access Egress QoS policy for SAP-based queuing mode on 7210 SAS-Mxp ..........360...

  • Page 9: Table Of Contents

    Table of Contents QoS Port Scheduler Policy Command Reference ....................401 Command Hierarchies..........................401 Port Scheduler Policy Configuration Commands ...................401 Operational Commands .........................401 Show Commands ...........................401 Command Descriptions ..........................402 Configuration Commands ........................402 Operational Commands .........................402 Port Scheduler Policy Commands ......................403 Show Commands ...........................405 Schedulers on 7210 SAS-Mxp ......................

  • Page 10: Table Of Contents

    Table of Contents Queue Management Policies......................445 In This Section..............................445 Overview................................445 Basic Configurations ...........................446 Service Management Tasks ..........................446 Creating a Queue Management Policy .......................446 Editing QoS Policies............................447 Queue Management Policy Command Reference ...................449 Command Hierarchies..........................449 Configuration Commands for 7210 SAS-Mxp ..................449 Show Commands ...........................449 Operational Commands .........................449 Command Descriptions ..........................451...

  • Page 11: Table Of Contents

    List of Figures QoS Policies ............................21 Figure 1 7210 SAS Traffic Types Operating in Network Mode ..............36 Figure 2 7210 SAS-M Traffic Types for Access Uplink Mode ..............37 Figure 3 Traffic Queuing Model for Forwarding Classes................62 Figure 4 RED Slope Characteristics ......................87 Schedulers on 7210 SAS-Mxp ......................

  • Page 12

    List of Figures 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 13

    List of Tables Getting Started............................19 Table 1 Configuration Process ........................19 QoS Policies ............................21 Table 2 QoS Policy Types and Descriptions for 7210 SAS-M, T devices in Access-uplink mode .....24 Table 3 QoS Policy Types and Descriptions for 7210 SAS-M, T devices in network mode ......27 Table 4 QoS Policy Types and Descriptions for 7210 SAS-Mxp devices ..........31 Table 5...

  • Page 14

    List of Tables Table 34 Default Slope Policy Definition (for 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS- Sx 10/ 100GE configured in Network mode) ....................92 Table 35 Default values for the default slope policy for 7210 SAS-Mxp ............94 Table 36 Minimum and Maximum Bandwidth Meters Example ..............95 Table 37 Forwarding Classes ........................99...

  • Page 15: Preface

    Preface About This Guide This guide describes Quality of Service (QoS) provided by the 7210 SAS-M, T, Sx/S 1/ 10GE,Sx 10/100GE, and Mxp presents examples to configure and implement various protocols and services. On 7210 SAS devices, not all the CLI commands are supported on all the platforms and in all the modes.

  • Page 16: Audience

    About This Guide On 7210 SAS devices, not all the CLI commands are supported on all the platforms and in all the modes. In many cases, the CLI commands are mentioned explicitly in this document. In other cases, it is implied and easy to know the CLIs that are not supported on a particular platform.

  • Page 17: Technical Support

    Preface • 7210 SAS-M, T, X, R6, R12, Mxp, Sx OS OAM and Diagnostic Guide This guide describes how to configure features such as service mirroring and Operations, Administration and Management (OAM) tools. • 7210 SAS-M,T, Mxp, Sx Quality of Service Guide This guide describes how to configure Quality of Service (QoS) policy management.

  • Page 18

    About This Guide 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 19: Getting Started

    Getting Started In This Chapter This chapter provides process flow information to configure Quality of Service (QoS) policies and provision services. This guide provides information to configure QoS policies in both network mode and access- uplink mode. Unless otherwise noted, many of the qos policies are applicable to both network mode and access-uplink mode.

  • Page 20

    Alcatel-Lucent 7210 SAS-Series Services Configuration Process Table 1: Configuration Process (Continued) Area Task Chapter (Continued) • Access egress Access Egress QoS Policies on 7210 SAS-M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS- Sx 10/100GE • Access egress for 7210 Access Egress QoS Policies for SAS-Mxp 7210 SAS-Mxp...

  • Page 21: Qos Policies

    The operational theory of a service tunnel is that the encapsulation of the data between the two Nokia service routers appear like a Layer 2 path to the service data although it is really traversing an IP or IP/MPLS core. The tunnel from one edge device to the other edge device is provisioned with an encapsulation and the services are mapped to the tunnel that most appropriately supports the service needs.

  • Page 22: Overview Of Qos Policies On 7210 Sas-m And 7210 Sas-t In Access-uplink Mode

    QoS Overview The 7210 SAS supports eight forwarding classes internally named: Network-Control, High- 1, Expedited, High-2, Low-1, Assured, Low-2 and Best-Effort. The forwarding classes are discussed in more detail in Forwarding Classes. 7210 SAS devices use QoS policies to control how QoS is handled at distinct points in the service delivery model within the device.

  • Page 23

    QoS Policies • Port scheduler (for access port and access-uplink port egress) • Slope Policies Service ingress QoS policies are applied to the customer-facing Service Access Points (SAPs). Traffic that enters through the SAP is classified to map it to a Forwarding Class (FC). Forwarding class is associated with meters/policier on ingress.

  • Page 24

    QoS Overview One service ingress QoS policy can be applied to a specific SAP. Access egress policy can be applied to an access port. One access egress QoS policy can be applied to the access port. One network QoS policy can be applied to a access-uplink port when operating in access- uplink mode.

  • Page 25: Overview Of Qos Policies On 7210 Sas-m And 7210 Sas-t In Network Mode

    QoS Policies Table 2: QoS Policy Types and Descriptions for 7210 SAS-M, T devices in Access-uplink mode (Continued) Policy Type Device Applied at… Description Page Operating Mode Network Queue Access-uplink Access-uplink • Defines forwarding class mappings to mode port network queues and queue characteristics for the queues.

  • Page 26

    QoS Overview Service ingress QoS policies are applied to the customer-facing Service Access Points (SAPs). Traffic that enters through the SAP is classified to map it to a Forwarding Class (FC). Forwarding class is associated with meters/policier on ingress. The mapping of traffic to meters can be based on combinations of customer QoS marking (IEEE 802.1p bits), IP and MAC criteria.

  • Page 27

    QoS Policies One service ingress QoS policy can be applied to a specific SAP Access egress policy can be applied to an access port. One access egress QoS policy can be applied to the access port. One network QoS policy can be applied to a specific IP interface or network port based on the type of network QoS policy.

  • Page 28: Overview Of Qos Policies On 7210 Sas-mxp In Network Mode

    QoS Overview Table 3: QoS Policy Types and Descriptions for 7210 SAS-M, T devices in network mode (Continued) Policy Type Device Applied at… Description Page Operating Mode Network (of Network mode IP interface • Used for classification/marking of type’ip- MPLS packets. interface’) •...

  • Page 29

    QoS Policies These policies allow user to configure the following: • Classification rules for how traffic is mapped to forwarding classes • Forwarding class association with meters and meter parameters used for policing (rate-limiting). • Queuing parameters for shaping • QoS marking/interpretation There are several types of QoS policies: •...

  • Page 30

    QoS Overview An access egress policy is applied on the physical port as opposed to the logical port (SAP) for SAP egress policy. It applies to all the SAPs on the given port. An access egress policy defines how to remark the forwarding class to packet header bits (For example: IEEE 802.1p bits in the L2 VLAN header, and others.).

  • Page 31

    QoS Policies Table 4: QoS Policy Types and Descriptions for 7210 SAS-Mxp devices Policy Type Device Applied at… Description Page Operating Mode Service Ingress Network mode SAP ingress • Defines up to 16 forwarding class meters and meter parameters for traffic classification.

  • Page 32: Overview Of Qos Policies On 7210 Sas-sx/s 1/10ge And 7210 Sas-sx 10/100ge

    QoS Overview Table 4: QoS Policy Types and Descriptions for 7210 SAS-Mxp devices (Continued) Policy Type Device Applied at… Description Page Operating Mode Slope Network mode Access ports, • Enables or disables the high-slope, low- Network ports slope, and non-TCP parameters within and Hybrid the egress pool.

  • Page 33

    QoS Policies Service ingress QoS policies are applied to the customer-facing Service Access Points (SAPs). Traffic that enters through the SAP is classified to map it to a Forwarding Class (FC). Forwarding class is associated with meters/policier on ingress. The mapping of traffic to meters can be based on combinations of customer QoS marking (IEEE 802.1p bits), IP and MAC criteria.

  • Page 34

    QoS Overview • Network queue policies are supported for queue configuration of egress queues on hybrid ports. These egress queues are shared by traffic sent out of SAPs and network IP interfaces configured on hybrid port. • Network qos (type == ip-interface) policies are supported for network IP interfaces on hybrid ports.

  • Page 35

    QoS Policies Table 5: QoS Policy Types and Descriptions for 7210 SAS-Sx/S 1/10GE and 7210 SAS0Sx 10/100GE devices Policy Type Device Applied at… Description Page Operating Mode Service Ingress Network mode SAP ingress • Defines up to 16 forwarding class meters and meter parameters for traffic classification.

  • Page 36: Service And Network Qos Policies

    QoS Overview Table 5: QoS Policy Types and Descriptions for 7210 SAS-Sx/S 1/10GE and 7210 SAS0Sx 10/100GE devices (Continued) Policy Type Device Applied at… Description Page Operating Mode Port scheduler Network mode Access ports, • Defines the parameters for the port Network ports scheduler.

  • Page 37: Network Qos Policies In Network Mode

    QoS Policies Figure 2: 7210 SAS-M Traffic Types for Access Uplink Mode Access Uplink Access 7210 SAS M Switch Processing Unit/ Ethernet Access Switch Service Ingress Access Uplink Egress Access Egress Access Uplink Ingress The 7210 SAS uses the following QoS policies applied to a SAP or a network port or an access port or an access-uplink port to define queuing, queue attributes, policer/meter attributes and QoS marking interpretation.

  • Page 38: Ip-interface' Type Network Qos Policy

    QoS Overview 'ip-interface' type Network QoS policy Network QoS policies (ip-interface type) define ingress forwarding class meters and maps traffic to those meters for IP interfaces. When a network QoS policy is created, it always has two meters defined that cannot be deleted, one for all the unicast traffic and one for all the multipoint traffic.

  • Page 39

    QoS Policies Default network QoS policy 2 is applied to all IP interfaces which do not have another network QoS policy explicitly assigned. The network QoS policy applied at network egress (for example, on an IP interface) determines how or whether the profile state is marked in packets transmitted into the service core network.

  • Page 40: Port" Type Network Qos Policy

    QoS Overview Table 7: Default Network QoS Policy (type = ip-interface) EXP to FC Mapping EXP Value FC Ingress Profile “port” Type Network QoS Policy Network QoS policy of type port defines ingress forwarding class meters and maps traffic to those meters for only IP traffic received on network and hybrid ports.

  • Page 41

    QoS Policies • At least one default unicast forwarding class meter. The parameters that can be configured for a meter are discussed in Meter Parameters on page 25. Optional network QoS policy elements include: • Additional unicast meters up to a total of 8. •...

  • Page 42: Network Qos Policies For Access-uplink Mode

    QoS Overview Table 9: Default Network QoS Policy of Type Port - Dot1p/DSCP to FC Mapping Dot1p/DSCP Value FC Ingress Profile Network QoS Policies for Access-uplink Mode Network QoS policies define ingress forwarding class meters and maps traffic to those meters for access uplink ports.

  • Page 43

    QoS Policies • Egress forwarding class to Dot1p value mappings for each forwarding class. • A default ingress forwarding class and in-profile/out-of-profile state. • At least one default unicast forwarding class meter. The parameters that can be configured for a meter are discussed in Meter/Policer Parameters.

  • Page 44: Network Queue Policies In Network Mode

    QoS Overview Table 10: Default Network QoS Policy used for Egress Marking on Access-uplink Ports (Continued) FC-ID FC Name FC Label DiffServ Egress Dot1p Name Marking In-Profile Out-of- Profile Best Effort 000-0 000-0 For network ingress, Table 11 lists the default mapping of Dot1p values to forwarding class and profile state for the default network QoS policy.

  • Page 45

    QoS Policies • On 7210 SAS-M,T, and Mxp, 8 queues are allocated and 8 FC are mapped to these 8 queues. The FC to queue mapping is as given in the Table 38, Forwarding Class to Queue-ID Map for 7210 SAS-M, 7210 SAS-T, and 7210 SAS-Mxp, on page 101.

  • Page 46: Network Queue Policies In Access-uplink Mode

    QoS Overview Table 12: Default Network Queue Policy Definition (for 7210 SAS-M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, and 7210 SAS-Mxp configured in Network mode) (Continued) Forwarding Class Queue Definition (Continued) • PIR = 100% High-2 (h2) Queue 5 •...

  • Page 47

    QoS Policies Table 13: Default Network Queue Policy Definition (for 7210 SAS-M and 7210 SAS-T configured in access uplink mode) Forwarding Class Queue Definition • PIR = 100% Network-Control (nc) Queue 8 • CIR = 10% • CBS = 7% •...

  • Page 48: Meter/policer Parameters

    QoS Overview Meter/Policer Parameters This section describes the meter parameters available for meter. Meters are available for use in both network mode and access-uplink mode with the following policies. In network mode of operation meter/policer is available with the following: •...

  • Page 49: Committed Information Rate For Meters

    QoS Policies Committed Information Rate for Meters The committed information rate (CIR) for a meter is the long term average rate at which traffic is considered as conforming traffic or in-profile traffic. The higher the rate, the greater the throughput user can expect. The user will be able to burst above the CIR and up to PIR for brief periods of time.

  • Page 50: Adaptation Rule For Meters

    QoS Overview Adaptation Rule for Meters The adaptation rule provides the QoS provisioning system with the ability to adapt the administrative rates provisioned for CIR and PIR, to derive the operational rates based on the underlying capabilities of the hardware. The administrative CIR and PIR rates are translated to actual operational rates enforced by the hardware meter.

  • Page 51: Committed Burst Size (for Meter/policers)

    QoS Policies Table 15: Administrative Rate Example (Continued) Administrative Rate Operation Rate Operation Rate Operation Rate (Min) (Max) (Closest) 118085 11808 11800 11808 46375 46376 46368 46376 If user has configured any value greater than 0 and less than 648 then operation rate configured on hardware would be 648 kbps irrespective of the constraint used.

  • Page 52: Meter Counters

    QoS Overview The operational MBS set by the system is adapted from the user configured value by using the minimum constraint. Meter Counters The 7210 SAS devices maintains the following counters for meters within the system for granular billing and accounting. Each meter maintains the following counters: •...

  • Page 53: Qos Overrides For Meters/policers

    QoS Policies • If the packet is pre-colored as in-profile (or also called as Green colored packets) then depending on the burst size of the packet meter can either mark it in-profile or out- profile. • If the packet is pre-colored as out-profile (also called as Yellow colored packets) then even if the packet burst is lesser than the current available CBS, it would not be marked as in-profile and remain as out-profile.

  • Page 54: Configuration Guidelines Of Qos Override

    QoS Overview Meter Override commands are supported on all types of access SAP. Configuration guidelines of QoS Override The configuration guidelines of QoS Override are: • QoS override commands can be used only for the meters or policers defined in the SAP ingress policy.

  • Page 55: Queue Parameters

    QoS Policies Queue Parameters This section describes the queue parameters available for queue. Queues are available for use in both network mode and access-uplink mode with the following policies. In network mode of operation queue is available with the following: •...

  • Page 56: Committed Information Rate For Queues

    QoS Overview Committed Information Rate for Queues The committed information rate (CIR) for a queue performs two distinct functions: 1. Minimum bandwidth guarantees — Egress Queue’s CIR setting provides the bandwidth which will be given to this queue as compared to other queues on the port competing for a share of the available link bandwidth.

  • Page 57: Peak Information Rate For Queues

    QoS Policies Peak Information Rate for Queues The peak information rate (PIR) defines the maximum rate at which packets are allowed to exit the queue. It does not specify the maximum rate at which packets may enter the queue; this is governed by the queue's ability to absorb bursts. The actual transmission rate of a egress queue depends on more than just its PIR.

  • Page 58

    QoS Overview The 7210 SAS uses a single rate step value of to define the granularity for both the CIR and PIR rates. The adaptation rule controls the method the system uses to choose the rate step based on the administrative rates defined by the rate command. For the supported CIR/PIR range values 0 to 1Gb, the same hardware rate is show in Table 16 or the supported CIR/PIR range values 0 to 10Gb for a 10-Gig Port, the same hardware rate...

  • Page 59

    QoS Policies Table 17: Supported Hardware Rates and CIR/PIR Values for 10-Gig Port for all platforms (Continued) Hardware Rate Steps Rate Range 8192kbps 8388608 – 10000000 kbps Table 18: Supported Hardware Rates and CIR/PIR Values for 7210 SAS-Mxp devices Hardware Rate Steps Rate Range (kbps) 0 - 16383 kbps 8 Kb/sec...

  • Page 60

    QoS Overview (MBS) for Queues The committed burst size and maximum burst size (CBS and MBS) parameters specify the amount of buffers reserved for a queue and up to how much of buffers a queue can contend for in the shared buffer space respectively that can be drawn from the reserved buffer portion of the queue’s buffer pool.

  • Page 61: Service Ingress Qos Policies

    QoS Policies Note: 1. On 7210 SAS-T, both in network mode and access-uplink mode the node can be operated with either per port MBS pool or per node MBS pool. In per port MBS pool mode, the maximum MBS per queue, assuming no other queues on the same port have any traffic is 33 Kbytes.

  • Page 62: Figure 3 Traffic Queuing Model For Forwarding Classes

    QoS Overview • The number of classification and meter resources to allocate for this policy. • Allocates resources from the ingress internal CAM resource pool for use for service ingress QoS policies. Additionally, allocate resources to the appropriate classification match criteria. •...

  • Page 63

    QoS Policies • Only Dot1p bits in the MAC header using the mac-criteria dot1p-only option • Supported IPv4 header fields using the ip-criteria any option • Only IPv4 DSCP in the IPv4 header using the ip-criteria dscp-only option • Supported IPv6 header fields using the ipv6-criteria any option •...

  • Page 64

    QoS Overview Table 20: Service Ingress QoS Policy IP Match Criteria for 7210 SAS-M, 7210 SAS-Sx/S 1/10GE, 7210 SAS- Sx 10/100GE, and 7210 SAS-Mxp network mode IP Criteria • IP DSCP value/mask and IP IP source and mask, IP destination and mask, Precedence value (available for SAPs IP protocol, TCP/UDP source port, TCP/UDP in VPLS, VLL, PBB Epipe I-SAP,...

  • Page 65

    QoS Policies Table 24: Service Ingress QoS Policy IPv6 Match Criteria in 7210 SAS-M and 7210 SAS-T access-uplink mode IPv6 Criteria • IP DSCP value/mask and IP Precedence IPv6 128-bit source and mask, IPv6 128-bit value (available for SAPs in VPLS, and destination and mask, IP protocol/next-header, VLL services) TCP/UDP source port, TCP/UDP destination...

  • Page 66

    QoS Overview Table 27: MAC Match Criteria Frame Type Dependencies (Continued) Frame Format Source MAC Dest MAC IEEE 802.1p Value Etype Value ethernet-II Service ingress QoS policy ID 1 is reserved for the default service ingress policy. The default policy cannot be deleted or changed. The default service ingress policy is implicitly applied to all SAPs which do not explicitly have another service ingress policy assigned.

  • Page 67: Hierarchical Ingress Policing

    QoS Policies Hierarchical Ingress Policing Hierarchical ingress policing allows the users to specify the amount of traffic admitted into the system per SAP. It also allows the user to share the available bandwidth per SAP among the different FCs of the SAP. For example, user can allow the packets classified as Internet data to use the entire SAP bandwidth when other forwarding classes do not have traffic.

  • Page 68

    QoS Overview • Per-service egress subrate capabilities especially for multipoint services. • More granular, fairer scheduling per-service into the access network. • Per-service statistics for forwarded and discarded service packets. The sub-rate capabilities and per-service scheduling control are required to make multiple services per physical port possible.

  • Page 69

    QoS Policies Note: On 7210 SAS-Mxp, the users have an option to use either port-based egress queuing and • shaping or SAP-based egress queuing and shaping for SAPs configured on access ports or hybrid ports. The command, “configure>system>resource-profile> qos>port- scheduler-mode”, lets the user select the mode to be used for SAPs configured on all the ports of the node (in other words, this is a per node setting).

  • Page 70

    QoS Overview Table 29: Default SAP Egress Policy ID 1 Definition for 7210 SAS-Mxp Item Definition Queue 1-8 1 (one) queue defined for each traffic class Queue 8 • CIR=0 • PIR=max (line rate) • Cir-Level 1 • Pir-Weight 1 •...

  • Page 71

    QoS Policies Table 29: Default SAP Egress Policy ID 1 Definition for 7210 SAS-Mxp (Continued) Item Definition Queue 3 • CIR = 0 • PIR = max (line rate) • Cir-Level 1 • Pir-Weight 1 • Queue-Management Policy: default Queue 2 •...

  • Page 72

    QoS Overview • On 7210 SAS-M and 7210 SAS-T are 8 queues always available per access port and all forwarding classes traffic is mapped into these separate 8 queue as per Forwarding Class to Queue-ID Map, For more information, see Forwarding Class to Queue-ID Map for 7210 SAS-M, 7210 SAS-T, and 7210 SAS-Mxp.

  • Page 73

    QoS Policies • In network mode, if the packet was received over a service transport tunnel on a network port, the forwarding class is typically determined by in the MPLS LSP EXP bits. • For 7210 SAS-M and 7210 SAS-T in access uplink mode, if the packet was received on a access-uplink port, the forwarding class is determined by the Dot1p bits in the outer tag of the QinQ encapsulation.

  • Page 74

    QoS Overview Table 30: Default Access Egress Policy ID 1 Definition for 7210 SAS-M and 7210 SAS-T Characteristic Item Definition Assured (af) Queue 3 • CIR = 0 • PIR = max (line rate) • CBS = default (values derived for optimal buffer usage) Low-2 (l2) Queue 2...

  • Page 75: Access Egress Qos Policies On 7210 Sas-mxp

    QoS Policies Access Egress QoS Policies on 7210 SAS-Mxp On 7210 SAS-Mxp, the users have an option to use either port-based egress queuing and shaping or SAP-based egress queuing and shaping for SAPs configured on access ports or hybrid ports. The command, “configure>system>resource-profile> qos>port-scheduler- mode”, lets the user select the mode to be used for SAPs configured on all the ports of the node (in other words, this is a per node setting).

  • Page 76: Access Egress Qos Policy For Port-based Queuing Mode On 7210 Sas-mxp

    QoS Overview • If remark policy type is dscp, then all traffic sent out of L2 SAPs and L3 SAPs configured on that port will have its IP DSCP bits marked (assuming L2 SAPs are carrying IP traffic). • If remark policy type is of type dot1p-dscp, then all traffic sent out of L2 SAPs and L3 SAPs configured on that port will have its IP DSCP bits (assuming L2 SAPs are carrying IP traffic) and Dot1p bits marked.

  • Page 77

    QoS Policies When port-scheduler-mode is enabled, software uses 8 egress queues per access port or hybrid port and all the SAPs configured on the port will share the 8 egress queues for traffic sent out of that port. When port-scheduler-mode is enabled, the queue parameters for the access port egress queues are defined using the access egress policies.

  • Page 78: Buffer Pools On 7210 Sas-m And 7210 Sas-t

    QoS Overview • Specify remark policy that defines IEEE 802.1p priority value remarking based on forwarding class. On 7210 SAS-Mxp, when port-based queuing is used, the FC to queue map is fixed and the queue's priority is determined by the queue number, with higher queue number having the higher priority.

  • Page 79: Buffer Pool Allocation - Per Node Mbs Pool On 7210 Sas-t

    QoS Policies Buffer pool allocation - Per Node MBS pool on 7210 SAS-T In the per node MBS pool mode, each of the queue on a port, is allocated a CBS amount of committed buffers. The remaining amount of buffers is allocated towards the MBS pool that is available for sharing among all the queues across all the ports of the node.

  • Page 80: Decommissioning Ports With Per Port Mbs Pool

    QoS Overview Decommissioning Ports with Per port MBS pool To allow operators better control over which ports get larger portion of queue buffers, the operator is provided with an option to use per-port MBS pool (like what is available on 7210 SAS-M) and decommission ports.

  • Page 81: Configuration Guidelines For Use Of 'decommission' Commands On 7210 Sas-m And 7210 Sas-t Devices

    QoS Policies The users have an option to specify the groups of ports which receives the credit of queue buffers freed up using the decommission command. With this option, the user can specify a port or group of ports which receives the credit of queue buffers. For example, it is possible for the user to configure decommissioning of 4 fixed copper ports and allocate the freed queue buffers to the remaining copper ports in the system or decommission 5 fiber ports and allocate the freed up queue buffers to the 10G XFP ports, and so on.

  • Page 82: Buffer Pools On 7210 Sas-sx/s 1/10ge And 7210 Sas-sx 10/100ge Devices

    15 port 1/2/1,1/2/2 to 1/1/2 entry 23 port 1/1/5 to 1/1/3 ---------------------------------------------- A:7210SAS>config>system>res-prof>decom# Note: For more information on the decommission CLI commands, see the “7210 SAS OS Basics System User Guide”. Buffer Pools on 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE devices The 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE has 4MB of packets buffers and it supports only a single mode of operation, per node MBS pool, in this release.

  • Page 83: Buffer Pools On 7210 Sas-mxp

    QoS Policies NOTE: The system internal ports, such as internal loopback port used for mirroring, port loopback with mac-swap, and others are allocated with some buffers. Additionally, some buffers are reserved for system internal use (for example: CPU queues, etc.). The amount of buffers remaining after allocating buffers for system internal use is available for allocation towards MBS buffers for all egress queues and per node MBS pool.

  • Page 84

    QoS Overview Slope Policies for 7210 SAS-M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE devices Note: On 7210 SAS-Mxp, the queue management policies are used to configure the WRED slopes. The available buffer space is partitioned into buffer pools. The buffers for a queue are allocated from the available buffer pool as described in the section on Buffer Pools on 7210 SAS-M and 7210...

  • Page 85

    QoS Policies RED Slopes In Network and Access-uplink Mode Operation and Configuration On 7210 SAS platforms RED slopes support is as follows: • On 7210 SAS-M (network mode and access-uplink mode) each queue provides user an option to configure high-priority RED slope a non-TCP RED slope, and a low- priority RED slope -OR- use 2 slopes - high-priority RED slope and a low-priority RED slope per queue.

  • Page 86

    QoS Overview When a queue depth exceeds the queue’s CBS, packets received on that queue must contend with other queues exceeding their CBS for shared buffers. To resolve this contention, the buffer pool uses two RED slopes to determine buffer availability on a packet by packet basis. A packet that was either classified as high priority or considered in-profile is handled by the high-priority RED slope.

  • Page 87: Figure 4 Red Slope Characteristics

    QoS Policies Figure 4: RED Slope Characteristics Max-Avg Probability Max-Prob Start-Avg 100% Average Utilization OSSG020 A RED slope itself is a graph with an X (horizontal) and Y (vertical) axis. The X-axis plots the percentage of shared buffer average utilization, going from 0 to 100 percent. The Y-axis plots the probability of packet discard marked as 0 to 1.

  • Page 88: Tuning The Shared Buffer Utilization Calculation

    QoS Overview Tuning the Shared Buffer Utilization Calculation The 7210 SAS allows tuning the calculation of the Shared Buffer Average Utilization (SBAU) after assigning buffers for a packet entering a queue as used by the RED slopes to calculate a packet’s drop probability. It implements a time average factor (TAF) parameter in the buffer policy which determines the contribution of the historical shared buffer utilization and the instantaneous Shared Buffer Utilization (SBU) in calculating the SBAU.

  • Page 89

    QoS Policies Table 32: TAF Impact on Shared Buffer Average Utilization Calculation (Continued) Equates Shared Buffer Shared Buffer Average Instantaneous Utilization Portion Utilization Portion 1/4 (0.25) 3/4 (0.75) 1/8 (0.125) 7/8 (0.875) 1/16 (0.0625) 15/16 (0.9375) 1/32 (0.03125) 31/32 (0.96875) 1/64 (0.015625) 63/64 (0.984375) 1/128 (0.0078125)

  • Page 90: Slope Policy Parameters

    QoS Overview Slope Policy Parameters The elements required to define a slope policy are: • A unique policy ID. • On 7210 SAS-M, choose whether the three slopes per queue must be used or two slopes must be used. • On 7210 SAS-T, 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE, only two slopes per queue is available.

  • Page 91

    QoS Policies Table 33: Default Slope Policy Definition (for 7210 SAS-M configured in Network mode) (Continued) Parameter Description Setting start-avg 70% utilization max-avg 90% utilization max-prob Low (RED) slope Administrative state Shutdown start-avg 50% utilization max-avg 75% utilization max-prob 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 92

    QoS Overview Table 33: Default Slope Policy Definition (for 7210 SAS-M configured in Network mode) (Continued) Parameter Description Setting Non-TCP (RED) slope Administrative State Shutdown start-avg 50% utilization max-avg 75% utilization max-prob Table 34: Default Slope Policy Definition (for 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS- Sx 10/ 100GE configured in Network mode) Parameter Description...

  • Page 93: Queue Management Policies For 7210 Sas-mxp

    QoS Policies Table 34: Default Slope Policy Definition (for 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS- Sx 10/ 100GE configured in Network mode) (Continued) Parameter Description Setting Queue Management Policies for 7210 SAS-Mxp Queue management policies allows the user to define the queue buffer and WRED slope parameters.

  • Page 94

    QoS Overview Table 35: Default values for the default slope policy for 7210 SAS-Mxp Parameter Description Setting Policy ID Queue management policy default (for default queue management policy) Committed Burst size Default (in kilobytes) Maximum Burst size Default (in kilobytes) High (RED) slope Administrative state Shutdown...

  • Page 95

    QoS Policies Scheduler Modes Note: For 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE, please refer to the Chapter onSchedulers on 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE. The scheduling modes interact with the minimum and maximum bandwidth CoS queue and maximum bandwidth egress port shaping specifications.

  • Page 96

    QoS Overview • Round robin scheduling across CoS queues — The round robin scheduler mode provides round robin arbitration across the CoS queues. The scheduler visits each backlogged CoS queue, servicing a single packet at each queue before moving on to the next one.

  • Page 97: Schedulers On 7210 Sas-mxp

    QoS Policies bandwidth is available before scheduling the queues in the PIR loop. If multiple queues are configured as strict, the higher-priority strict queues are serviced first before the lower priority strict queues in both the CIR and the PIR loop. The weights configured for the queues are only considered during the PIR loop.

  • Page 98: Remark Policy On 7210 Sas-t, 7210 Sas-sx/s 1/10ge, 7210 Sas-sx 10/100ge, And 7210 Sas-mxp (network Mode)

    QoS Overview Remark Policy on 7210 SAS-T, 7210 SAS-Sx/S 1/ 10GE, 7210 SAS-Sx 10/100GE, and 7210 SAS-Mxp (Network mode) This policy allows the user to define the forwarding class to egress marking values. Based on the packet encapsulation used to send out the service packets, the remark policy allows the user to define and associate appropriate policies to service egress and network egress QoS policies.

  • Page 99: Forwarding Classes

    QoS Policies Forwarding Classes 7210 SAS devices support multiple forwarding classes and class-based queuing, so the concept of forwarding classes is common to all of the QoS policies. Each forwarding class (also called Class of Service (CoS)) is important only in relation to the other forwarding classes.

  • Page 100

    QoS Overview Note that Table 37 presents the default definitions for the forwarding classes. The forwarding class behavior, in terms of ingress marking interpretation and egress marking, can be changed by a Network QoS Policies in Network Mode. All forwarding class queues support the concept of in-profile and out-of-profile.

  • Page 101: Forwarding-class To Queue-id Map On 7210 Sas-m, 7210 Sas-t, And 7210 Sas-mxp

    QoS Policies Forwarding-Class To Queue-ID Map on 7210 SAS-M, 7210 SAS-T, and 7210 SAS-Mxp There are 8 forwarding classes supported on 7210 SAS devices. Each of these FC is mapped to a specific queue. By mapping FC to different queues the differential treatment is imparted to various classes of traffic.

  • Page 102

    QoS Overview 10GE and 7210 SAS-Sx 10/100GE There are 8 forwarding classes supported on the device. Each of these FC is mapped to two queues, one used for unicast traffic mapped to the FC and another used for multicast/BUM traffic mapped to the FC. By mapping FC to different queues the differential treatment is imparted to various classes of traffic.

  • Page 103: Qos Policy For Hybrid Port On 7210 Sas-m And 7210 Sas-t

    QoS Policies QoS Policy for Hybrid port on 7210 SAS-M and 7210 SAS-T An overview of qos policy support on hybrid ports is described below. For more details refer to the following chapters. • Network queue policies are supported for queue configuration of egress queues on hybrid ports.

  • Page 104: Qos Policy For Hybrid Port On 7210 Sas-mxp

    QoS Overview • Network qos (type == ip-interface) policies are supported for network IP interfaces on hybrid ports. The behavior is similar to the existing behavior for network IP interfaces on network ports. It supports per IP interface ingress classification and policing, and egress marking (only EXP marking for MPLS traffic).

  • Page 105: Qos Policy Entities

    QoS Policies • Service Egress policies are supported for queue configuration of per SAP egress queues for SAPs configured on hybrid ports. These egress queues are used by traffic sent out of SAPs configured on hybrid port. For traffic sent out of SAPs configured in L2 services, Dot1p can be marked per SAP using the service egress policy.

  • Page 106: Configuration Notes

    Configuration Notes • Epipe — Only SAP ingress policies are supported on an Epipe service access point (SAP). • VPLS — Only SAP ingress policies are supported on a VPLS SAP. • VPRN — Only SAP ingress policies are supported on a VPRN SAP. •...

  • Page 107: Discard Eligibility Indicator (dei) Based Classification And Marking

    Discard Eligibility Indicator (DEI) based Classification and Marking In This Section This section provides information about the Discard Eligibility Indicator (DEI) feature that describes the requirements for DEI based classification and marking for 7210 platforms. Topics in this section include: •...

  • Page 108

    DEI based Classification The following support is available for DEI classification: • Under the port configuration, a command is provided to enable DEI based classification, allowing user an option to enable/disable use of DEI for ingress classification on a per port basis. Initial profile (also known as color) is based on DEI/ CFI bit.

  • Page 109: Dei Based Marking

    Discard Eligibility Indicator (DEI) based Classification and Marking DEI based marking DEI based marking is supported on access ports, access-uplink ports and network ports. DEI bit can be used to mark the packet to carry the profile, assigned by an operator’s trusted node at the ingress to the carrier’s network, to the subsequent nodes in the network.

  • Page 110: Configuration Guidelines

    Configuration Guidelines • All the ports under a LAG should have the same configuration for DEI classification (enable/disable). If the LAG configuration changes, the port configuration also will be updated accordingly. Port configuration under the LAG cannot be changed. • While enabling DEI based policing on a port, if it is a hybrid port, then the network port ingress qos policy must use only dot1p mappings for classification and all the configured profiles must be 'use_dei' (not 'in' or 'out').

  • Page 111: Port Level Egress Rate-limiting

    Port Level Egress Rate-Limiting In This Section This section provides information to configure port level egress-rate using the command line interface. Topics in this section include: • Overview • Basic Configurations • Command Descriptions Overview Egress port rate limiting allows the device to limit the traffic that egresses through a port to a value less than the available link bandwidth.

  • Page 112: Effect Of Port Level Rate-limiting On Network Queue Functionality

    Basic Configurations • The port scheduler distributes the available maximum egress bandwidth based on the CIR/PIR configuration parameters provisioned for the queues. • Provides support for a burst parameter to control the amount of burst the egress port can generate. •...

  • Page 113: Modifying Port Level Egress-rate Command

    Port Level Egress Rate-Limiting • On 10G port, if Egress port Rate Limiter (ERL) configured is more than 8Gig it is recommended to configure burst value higher than 80kbits to avoid packet drops. The following displays the egress-rate configuration for a port: *A:Dut-1>config>port# info ---------------------------------------------- ethernet...

  • Page 114: Default Egress-rate Values

    Basic Configurations ---------------------------------------------- *A:Dut-1>config>port# Default Egress-Rate Values By default no egress-rate is configured for a port. 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 115: Port Level Egress-rate Command Reference

    Port Level Egress Rate-Limiting Port Level Egress-Rate Command Reference Command Hierarchies Configuration Commands config — port — ethernet — egress-rate sub-rate [max-burst size-in-kbits] — no egress-rate Show Commands show — port [port-id] 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 116: Command Descriptions

    Port Level Egress-Rate Command Reference Command Descriptions Configuration Commands egress-rate Syntax egress-rate sub-rate [max-burst size-in-kbits] no egress-rate Context config>port>ethernet Description This command configures maximum rate and corresponding burst value for a port. The egress-rate is configured as kbps while max-burst is configured as kilo-bits while max-burst should be between 64 and 16384 or default.

  • Page 117

    Port Level Egress Rate-Limiting Ethernet Interface =============================================================================== Description : 10/100/Gig Ethernet SFP Interface : 1/1/23 Oper Speed : 100 mbps Link-level : Ethernet Config Speed : 1 Gbps Admin State : up Oper Duplex : full Oper State : up Config Duplex : full Physical Link...

  • Page 118

    Port Level Egress-Rate Command Reference Discards Unknown Proto Discards =============================================================================== =============================================================================== Ethernet-like Medium Statistics =============================================================================== Alignment Errors : Sngl Collisions FCS Errors Mult Collisions SQE Test Errors Late Collisions Excess Collisns Too long Frames Int MAC Tx Errs Symbol Errors Int MAC Rx Errs =============================================================================== *A:MTU-T2>config>port>ethernet#...

  • Page 119: Frame Based Accounting

    Frame Based Accounting In This Section This section provides information to configure frame-based accounting using the command line interface. Topics in this section include: • Overview • Basic Configurations • Configuration Commands Overview This feature when enabled let QoS policies to account for the Ethernet frame overhead (for example, it accounts for the IFG (inter-frame gap) and the preamble).

  • Page 120: Effects Of Enabling Ingress Frame Based Accounting On Ingress Meter Functionality

    Basic Configurations Effects of Enabling Ingress Frame Based Accounting on Ingress Meter Functionality To enable system-wide consistency in configuring QoS queue and meter rate parameters, the meters used on the system ingress might need to account for Ethernet frame overhead. Network ingress and service ingress meters account for Ethernet frame overhead.

  • Page 121: Enabling And Disabling Frame-based Accounting

    Frame Based Accounting The following displays the frame-based accounting configuration: *A:Dut-1>config>qos>frame-based-accounting# info detail ---------------------------------------------- no ingress-enable no egress-enable ---------------------------------------------- *A:Dut-1>config>qos>frame-based-accounting# Enabling and Disabling Frame-Based Accounting To enable frame-based-accounting for ingress, you can simply use the ingress-enable command and to enable frame-based-accounting on egress use the egress-enable command. To disable frame-based-accounting for ingress, execute the no ingress-enable command and to disable frame-based-accounting on egress, execute the no egress-enable command.

  • Page 122

    Basic Configurations 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 123: Frame Based Accounting Command Reference

    Frame Based Accounting Frame Based Accounting Command Reference Command Hierarchies Configuration Commands config — qos — frame-based-accounting — [no] egress-enable — [no] ingress-enable 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 124

    Frame Based Accounting Command Reference Command Descriptions Configuration Commands egress-enable Syntax [no] egress-enable Context config>qos>frame-based-accounting Description Platforms Supported: 7210 SAS-M, 7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE. This command enables the frame-based-accounting for access-egress, network-queue, port scheduler, SAP or Network Aggregate Rate and port-level egress-rate.

  • Page 125: Network Qos Policies

    Network QoS Policies In This Section This section provides information to configure network QoS policies using the command line interface. Topics in this section include: • Overview • Basic Configurations • Service Management Tasks Overview Overview of Network QoS policies in Network mode Network QoS policies are available for use with network IP interfaces, network port and hybrid port when operating the 7210 SAS device network mode.

  • Page 126: Overview Of Network Qos Policies In Access-uplink Mode

    Overview The following types of QoS mapping decisions are applicable on a network port when operating in network mode: • Ethernet Dot1P and IP DSCP value mapping (if defined) for use with IP packets • Default QoS mapping The default QoS mapping always exists on network port and every received packet will be mapped to this default if another explicitly defined matching entry does not exist.

  • Page 127: Network Qos Policy (ip-interface Type) Functionality

    Network QoS Policies The ingress component of the policy defines how the EXP, DSCP or Dot1p bits are mapped to internal forwarding class and profile state. The forwarding class and profile state define the Per Hop Behavior (PHB) or the QoS treatment through the 7210 SAS. From release 4.0, the profile mapping is defined using a new policy mpls-lsp-exp-profile-map.

  • Page 128: Basic Configurations

    Basic Configurations • LSPs setup using LDP uses a global mpls-lsp-exp-profile-map policy. By default, the system assigns a default mpls-lsp-exp-profile-map policy. User has an option to change the global policy to use. A new policy mpls-lsp-exp-profile-map policy allows the user to assign different profile value for MPLS EXP bits for MPLS packets received over different IP interface.

  • Page 129: Example For Network Qos Policy Of Type Ip-interface

    Network QoS Policies • Set the network-policy-type parameter to be ip-interface. • Include a description. The description provides a brief overview of policy features. • Egress Marking/ remarking - Specifies the egress LSP EXP marking map. Otherwise, the default values are applied. →...

  • Page 130

    Basic Configurations fc "ef" create meter 3 multicast-meter 5 exit lsp-exp 0 fc be lsp-exp 1 fc l2 lsp-exp 2 fc af lsp-exp 3 fc af lsp-exp 4 fc h2 lsp-exp 5 fc ef mpls-lsp-exp-profile 3 exit egress fc af exit fc be exit...

  • Page 131: Configuring Network Policy (type - Port) For Network Mode

    Network QoS Policies exit egress remarking remark 200 exit ---------------------------------------------- Configuring Network policy (type - port) for Network Mode To create an network QoS policy of type port when operating in network mode, define the following: • A network policy ID value. The system will not dynamically assign a value. •...

  • Page 132

    Basic Configurations network qos network-policy-id Use the following CLI syntax to create a network QoS policy: *A:dut-d>config>qos>network# info detail ---------------------------------------------- description "Default network-port QoS policy." scope template ingress default-action fc be profile out meter 1 create mode trtcm1 adaptation-rule cir closest pir closest rate cir 0 pir max mbs default kbits cbs default kbits...

  • Page 133: Default Network Policy Values Available In Network Mode

    Network QoS Policies Default Network Policy Values available in Network mode The default network policy for IP interfaces is identified as policy-id 2. Default policies cannot be modified or deleted. The following displays default network policy parameters: Table 40: Network Policy Defaults for Policy Type IP Interface Field Default description...

  • Page 134

    Basic Configurations Table 40: Network Policy Defaults for Policy Type IP Interface (Continued) Field Default lsp-exp-out-profile fc h11: lsp-exp-in-profile lsp-exp-out-profile fc h12: lsp-exp-in-profile lsp-exp-out-profile fc nc: lsp-exp-in-profile lsp-exp-out-profile Table 41: Default Network QoS Policy of Type IP Interface, LSP EXP to FC Mapping on Ingress LSP EXP Value 7210 FC...

  • Page 135

    Network QoS Policies This following output sample is of a default network port policy on 7210 SAS-M. *A:ALA>config>qos>network# info detail ---------------------------------------------- description "Default network-port QoS policy." scope template ingress default-action fc be profile out meter 1 create mode trtcm adaptation-rule cir closest pir closest rate cir 0 pir max mbs default cbs default...

  • Page 136

    Basic Configurations exit fc l1 dscp-in-profile af21 dscp-out-profile af22 dot1p-in-profile 3 dot1p-out-profile 2 exit fc l2 dscp-in-profile cs1 dscp-out-profile cs1 dot1p-in-profile 1 dot1p-out-profile 1 exit fc nc dscp-in-profile nc2 dscp-out-profile nc2 dot1p-in-profile 7 dot1p-out-profile 7 exit exit ---------------------------------------------- *A:ALA>config>qos>network# Default Network Interface policy for 7210 SAS-M devices in network mode. A:SAS-M>config>qos>network# info ---------------------------------------------- description "Default network QoS policy."...

  • Page 137: Resource Allocation For Network Qos Policy

    Network QoS Policies fc nc exit exit ---------------------------------------------- *A:SAS-M>config>qos>network# Default Network Port QoS policy for 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, and 7210 SAS-Mxp devices. *A:Dut-A>config>qos>network# info detail ---------------------------------------------- description "Default network-port QoS policy." scope template ingress default-action fc be profile out meter 1 create mode trtcm1 adaptation-rule cir closest pir closest...

  • Page 138

    Basic Configurations For every FC in use, the system allocates two classification entries in hardware, if the FC is configured to use both the unicast meter and the multicast meter or if the default meter 9 is configured in the policy. If multiple match criteria entries map to the same FC, then each of these are allocated two classification entries in hardware.

  • Page 139

    Network QoS Policies i=nc,h1,ef,h2,l1,af,l2,be Where, E(i) is the number of match- criteria entries that classify packets to FCi. For 7210 platforms, the maximum number of classification entries per policy can be 64 (including default). 2 is the number of classification entries that are required by FCi. Note: In the worst case, only 2 classification entries are used per FC in a network policy, as only two traffic-types are supported.

  • Page 140: Network Qos Policies Resource Usage Examples

    Basic Configurations Network QoS Policies Resource Usage Examples Note: In the examples below the profile configuration is not shown. In practice, user needs to configure the mpls-lsp-exp-profile policy and associate it with the network policy. Association of a profile policy with the network qos policy does not change the resource calculation methodology show below.

  • Page 141

    Network QoS Policies default-action fc be meter 1 create exit meter 2 create exit meter 9 multipoint create exit meter 12 multipoint create exit fc "af" create meter 2 multicast-meter 12 exit lsp-exp 2 fc af exit egress fc af exit fc be exit...

  • Page 142

    Basic Configurations fc "af" create meter 2 multicast-meter 12 exit fc "be" create meter 2 multicast-meter 12 exit lsp-exp 2 fc af exit egress fc af exit fc be exit fc ef exit fc h1 exit fc h2 exit fc l1 exit fc l2 exit...

  • Page 143

    Network QoS Policies lsp-exp 7 fc nc exit egress fc af exit fc be exit fc ef exit fc h1 exit fc h2 exit fc l1 exit fc l2 exit fc nc exit exit exit The number of Filter-Entries (TC) used is calculated, as follows: (2 * 1)nc + (2 * 1)h1 + (2 * 1)ef + (2 * 1)h2 + (2 * 0)l1 + (2 * 2)af + (2 * 1)l2 + (2 * 1)be = 16 The number of meters (TP) used are: 2 (Meters 1,9).

  • Page 144

    Basic Configurations exit lsp-exp 1 fc l2 lsp-exp 2 fc af lsp-exp 3 fc af lsp-exp 4 fc h2 lsp-exp 5 fc ef lsp-exp 6 fc h1 lsp-exp 7 fc nc exit egress fc af exit fc be exit fc ef exit fc h1 exit...

  • Page 145

    Network QoS Policies exit fc "be" create exit fc "ef" create exit fc "h1" create meter 3 exit fc "h2" create exit fc "l2" create exit fc "nc" create meter 3 exit lsp-exp 1 fc l2 lsp-exp 2 fc af lsp-exp 3 fc af lsp-exp 4 fc h2 lsp-exp 5 fc ef...

  • Page 146

    Basic Configurations default-action fc be meter 1 create mode trtcm adaptation-rule cir closest pir closest rate cir 0 pir max mbs default cbs default exit meter 9 multipoint create mode trtcm adaptation-rule cir closest pir closest rate cir 0 pir max mbs default cbs default exit...

  • Page 147

    Network QoS Policies exit The number of classification entries (TC) used is: 2. The number of meters (TP) used is: 2. Example 8 network 8 network-policy-type ip-interface create description “network-policy-8” ingress default-action fc nc meter 1 create exit meter 2 create exit meter 3 create exit...

  • Page 148: Network Qos Policy In Access Uplink Mode

    Basic Configurations fc be exit fc ef exit fc h1 exit fc h2 exit fc l1 exit fc l2 exit fc nc exit exit exit The number of classification entries (TC) used is calculated, as follows: (2 * 2)nc + (2 * 0)h1 + (2 * 1)ef + (2 * 0)h2 + (2 * 0)l1 + (2 * 1)af + (2 * 1)l2 + (0 * 0)be = 10 The numbers of meters (TP) used is: 6 (Meters 2, 3, 4, 7, 8, 12).

  • Page 149

    Network QoS Policies Network policy-id 1 exists as the default policy and is applied to access uplink ports.The network policy-id 1 cannot be modified or deleted. It defines the default Dot1p-to-FC mapping and default meters for unicast and multipoint meters for the ingress. For the egress, it defines eight forwarding classes and the packet marking criteria.

  • Page 150: Configuring Network Policy For Access-uplink Mode

    Basic Configurations Configuring Network policy for Access-uplink Mode To create an network QoS policy when operating in access-uplink mode, define the following: • A network policy ID value. The system will not dynamically assign a value. • Include a description. The description provides a brief overview of policy features. •...

  • Page 151

    Network QoS Policies mode trtcm1 adaptation-rule cir closest pir closest rate cir 0 pir max mbs default kbits cbs default kbits exit meter 9 multipoint create mode trtcm1 adaptation-rule cir closest pir closest rate cir 0 pir max mbs default kbits cbs default kbits exit dot1p 0 fc be profile out...

  • Page 152: Default Network Policy Values Available In Access-uplink Mode

    Basic Configurations Default Network Policy Values available in Access-uplink mode This following output sample is of a default network policy on 7210 SAS-M Access-uplink mode. >config>qos>network# info detail ---------------------------------------------- description "Default network-port QoS policy." scope template ingress default-action fc be profile out meter 1 create mode trtcm1 adaptation-rule cir closest pir closest...

  • Page 153

    Network QoS Policies no dot1p dot1p-in-profile 5 A:MTU>config>qos>network# This following output sample is of a default network port policy on 7210 SAS-T Access- uplink mode. *7210SAST>config>qos>network# info detail ---------------------------------------------- description "Default network-port QoS policy." scope template ingress default-action fc be profile out meter 1 create mode trtcm1 adaptation-rule cir closest pir closest...

  • Page 154

    Basic Configurations egress no remarking fc af dscp-in-profile af11 dscp-out-profile af12 no dot1p dot1p-in-profile 3 dot1p-out-profile 2 no de-mark exit fc be dscp-in-profile be dscp-out-profile be no dot1p dot1p-in-profile 0 dot1p-out-profile 0 no de-mark exit fc ef dscp-in-profile ef dscp-out-profile ef no dot1p dot1p-in-profile 5 dot1p-out-profile 5...

  • Page 155

    Network QoS Policies exit fc h2 dscp-in-profile af41 dscp-out-profile af41 no dot1p dot1p-in-profile 4 dot1p-out-profile 4 no de-mark exit fc l1 dscp-in-profile af21 dscp-out-profile af22 no dot1p dot1p-in-profile 3 dot1p-out-profile 2 no de-mark exit fc l2 dscp-in-profile cs1 dscp-out-profile cs1 no dot1p dot1p-in-profile 1 dot1p-out-profile 1...

  • Page 156: Dscp Marking Cpu Generated Traffic

    Basic Configurations exit ---------------------------------------------- *A:7210SAST>config>qos>network# DSCP Marking CPU Generated Traffic DSCP marking for CPU generated traffic is not configurable by the user. The default values are given in Table Note: BGP, RSVP, TLDP, OSPF, IS-IS, etc protocols are not supported on 7210 SAS devices configured in Access uplink mode.

  • Page 157: Default Dscp Mapping Table

    Network QoS Policies Table 42: DSCP and Dot1p Marking (Continued) Protocol IPv4 DSCP Dot1P Default DSCP DOT1P Marking Marking Values Values (Decim ICMP Res ICMP Unreach PIM (SSM) Trace route TACPLUS IGMP Note: DSCP and Dot1P values in the table are applicable when remarking is disabled at port level.

  • Page 158: Service Management Tasks

    Service Management Tasks Table 43: Default DSCP Mapping Table DSCP Name DSCP Value DSCP Value DSCP Value Label Decimal Hexadecimal Binary 0x2e 0b101110 af11 0x0a 0b001010 assured af12 0x0c 0b001100 assured af13 0x0e 0b001110 assured af21 0x12 0b010010 af22 0x14 0b010100 af23 0x16...

  • Page 159: Remove A Policy From The Qos Configuration

    Network QoS Policies You can replace the default policy with a non-default policy, but you cannot remove default policies from the configuration. When you remove a non-default policy, the policy association reverts to the appropriate default network policy. Remove a Policy from the QoS Configuration To delete a network policy, enter the following commands: CLI Syntax: config>qos# no network network-policy-id...

  • Page 160: Editing Qos Policies

    Service Management Tasks Editing QoS Policies You can change existing policies, except the default policies, and entries in the CLI. The changes are applied immediately to all network ports or IP interfaces or access uplink ports where the policy is applied. To prevent configuration errors use the copy command to make a duplicate of the original policy to a work area, make the edits, and then overwrite the original policy.

  • Page 161: Network Qos Policy Command Reference

    Network QoS Policies Network QoS Policy Command Reference • Configuration Commands (for 7210 SAS-M network mode operation) • Configuration Commands (for 7210 SAS-M network mode operation) • Configuration Commands in 7210 SAS-T and 7210 SAS-Sx/S 1/10GE configured in network mode •...

  • Page 162: Configuration Commands In 7210 Sas-t And 7210 Sas-sx/s 1/10ge Configured In Network Mode

    Network QoS Policy Command Reference — dscp-in-profile dscp-name — no dscp-in-profile — dscp-out-profile dscp-name — no dscp-out-profile — lsp-exp-in-profile lsp-exp-value — no lsp-exp-in-profile — lsp-exp-out-profile lsp-exp-value — no lsp-exp-out-profile — [no] remarking {use-dot1p|use-dscp|all} — ingress — default-action fc fc-name profile {in | out | use-dei} —...

  • Page 163: Configuration Commands For 7210 Sas-mxp

    Network QoS Policies — no remark — remark policy-id — remarking — no remarking — ingress — default-action fc fc-name profile {in | out | use-dei} — dot1p dot1p-priority fc fc-name profile {in | out| use-dei} — no dot1p dot1p-priority —...

  • Page 164: Configuration Commands In Access-uplink Mode

    Network QoS Policy Command Reference — no multicast-meter — dscp dscp-name fc fc-name profile {in | out} — no dscp dscp-name — lsp-exp lsp-exp-value fc fc-name — no lsp-exp lsp-exp-value — meter meter-id [multipoint] [create] — no meter meter-id — adaptation-rule [cir adaptation-rule] [pir adaptation-rule] —...

  • Page 165: Operational Commands (for Network Mode Or Access-uplink Mode Of Operation)

    Network QoS Policies — multicast-meter meter-id — no multicast-meter — meter meter-id [multipoint] [create] — no meter meter-id — adaptation-rule [cir adaptation-rule] [pir adaptation-rule] — no adaptation-rule — size-in-kbits — no — size-in-kbits — no — mode {trtcm1 | trtcml2 | srtcm} —...

  • Page 166

    Network QoS Policy Command Reference Command Descriptions Configuration Commands Generic Commands description Syntax description description-string no description Context config>qos>network policy-id Description Platforms Supported: 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-M (both access-uplink and network mode) and 7210 SAS-T (access-uplink and network mode). This command creates a text description stored in the configuration file for a configuration context.

  • Page 167

    Network QoS Policies The copy command is used to create new policies using existing policies and also allows bulk modifications to an existing policy with the use of the overwrite keyword. Parameters network src-pol dst-pol — Indicates that the source and destination policies are network policy IDs.

  • Page 168

    Network QoS Policy Command Reference Note: If remarking is enabled in access-egress policy, by default 'use-dot1p' is used. If no marking values are specified, then the default FC to Dot1p marking values are used. The no form of the command disables remarking. Default no remarking - Remarking is disabled by default.

  • Page 169

    Network QoS Policies → If 'all' is configured in the network policy of type ‘port’, then the Dot1p bits are marked in the packet header for all traffic (L2 and IPv4) sent out of both L2 and L3 SAPs and the IP DSCP bits are marked in the packet header for all IPv4 traffic sent out of only L3 SAPs configured on that hybrid port.

  • Page 170

    Network QoS Policy Command Reference See the Summary of remark policy and attachment points for 7210 SAS- T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE(Network mode), for different remark policies supported on the node and its use. The no form of the command removes the explicit association of the remark policy and associates the default remark policy.

  • Page 171

    Network QoS Policies This command configures the network policy scope as exclusive or template. The no form of this command sets the scope of the policy to the default of template. Default template Parameters exclusive — When the scope of a policy is defined as exclusive, the policy can only be applied to one interface.

  • Page 172

    Network QoS Policy Command Reference In network mode, Network policy-id 2 exists as the default policy that is applied to all IP interface by default. The network policy-id 2 cannot be modified or deleted. It defines the default LSP EXP-to-FC mapping and default meters for unicast traffic and optional multipoint meters for BUM traffic on the, ingress MPLS packets.

  • Page 173

    Network QoS Policies Context config>qos Description Platforms Supported: 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-Mxp, 7210 SAS-M (network mode), 7210 SAS-T (network mode). This command allows the user to create a new mpls-lsp-exp-profile-map policy. The policy specifies the profile to assign to the packet based on the MPLS LSP EXP bits value matched in the MPLS packet received on a network IP interface.

  • Page 174

    Network QoS Policy Command Reference Parameters lsp-exp-value — The 3-bit LSP EXP bit value, expressed as a decimal integer. Values 0 — 7 use-global-mpls-lsp-exp-profile Syntax use-global-mpls-lsp-exp-profile policy-id no use-global-mpls-lsp-exp-profile Context config>qos Description Platforms Supported: 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-Mxp, 7210 SAS-M (network mode), 7210 SAS-T (network mode).

  • Page 175

    Network QoS Policies When ‘no ldp-use-local-fc-enable’ is set, this policy is managed by the system. User is not allowed to modify it. The system assigns the same policy ID as the network policy ID. It is cannot be modified by the user.

  • Page 176

    Network QoS Policy Command Reference The egress component of the network QoS policy defines the queuing parameters associated with each forwarding class. There are eight queues per port on the egress. Each of the forwarding classes is associated with a queue on each access uplink port. This queue gets all the parameters defined within the default network QoS policy 1 until an explicit policy is defined for the network interface access uplink port.

  • Page 177

    Network QoS Policies Description Platforms Supported: 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-M (both access-uplink and network mode) and 7210 SAS-T (access-uplink and network mode). This command creates a class instance of the forwarding class. Once the fc-name is created, classification actions can be applied and it can be used in match classification criteria.

  • Page 178

    Network QoS Policy Command Reference Default default-action fc be profile out Parameters fc fc-name — Specify the forwarding class name. All packets with LSP EXP (only when devices is operating in network mode) or dot1p bits (for 7210 SAS-M and 7210 SAS-T in access uplink mode) that is not defined will be placed in this forwarding class.

  • Page 179

    Network QoS Policies Description Platforms Supported: 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-Mxp, 7210 SAS-M (both access-uplink and network mode), 7210 SAS-T (both access-uplink and network mode). This command explicitly sets the forwarding class or enqueuing priorityand profile of the packet when a packet is marked with a dot1p-priority specified.

  • Page 180

    Network QoS Policy Command Reference Multipoint meters are for traffic bound to multiple destinations. Within non-multipoint services, such as Epipe services, all traffic is considered unicast due to the nature of the service type. Multicast and broadcast-destined traffic in an Epipe service will not be mapped to a multipoint service meter. The no form of this command removes the meter-id from the Network ingress QoS policy and from any existing Ports using the policy.

  • Page 181

    Network QoS Policies The no form of this command sets the unicast (point-to-point) meter-id back to the default meter for the forwarding class (meter 1). Default meter 1 Parameters meter-id — Specifies the meter-id. The specified parameter must be an existing, non-multipoint meter defined in the config>qos>network>ingress context.

  • Page 182

    Network QoS Policy Command Reference Ingress traffic that matches the specified DSCP will be assigned to the corresponding forwarding class. Multiple commands can be entered to define the association of some or all sixty-four DiffServ code points to the forwarding class. For undefined code points, packets are assigned to the forwarding class specified under the default-action command.

  • Page 183

    Network QoS Policies Table 44: Default DSCP Names to DSCP Value Mapping Table (Continued) DSCP Name DSCP Value DSCP Value DSCP Value Decimal Binary Hexadecimal af11 0x0a 0b001010 af12 0x0c 0b001100 af13 0x0e 0b001110 default 0x00 0b000000 Table 45: Default Class Selector Code Points to DSCP Value Mapping Table DSCP Name DSCP Value DSCP Value...

  • Page 184

    Network QoS Policy Command Reference Note: DSCP values mapping to forwarding class ‘be’ can only be set to out-of-profile. Values in, out Default None, for every DSCP value defined, the profile must be indicated. If a DSCP value is not mapped, the default-action forwarding class and profile state will be used for that value.

  • Page 185

    Network QoS Policies no adaptation-rule Context config>qos>network>ingress>meter Description Platforms Supported: 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-Mxp, 7210 SAS-M (both access-uplink and network mode), 7210 SAS-T (both access-uplink and network mode). This command defines the method used by the system to derive the operational CIR and PIR settings when the meter is provisioned in hardware.

  • Page 186

    Network QoS Policy Command Reference This command provides a mechanism to override the default CBS for the meter. The committed burst size parameter specifies the maximum burst size that can be transmitted by the source while still complying with the CIR. If the transmitted burst is lower than the CBS value then the packets are marked as in-profile by the meter to indicate that the traffic is complying meter configured parameters.

  • Page 187

    Network QoS Policies mode Syntax mode mode no mode Context config>qos>network>ingress>meter Description Platforms Supported: 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-Mxp, 7210 SAS-M (both access-uplink and network mode), 7210 SAS-T (both access-uplink and network mode). This command defines the mode of the meter. The mode can be configured as Two Rate Three Color Marker (trTCM) or Single Rate Three Color Marker (srTCM).

  • Page 188

    Network QoS Policy Command Reference Note: The value of rates are represented in 1000 kilobits per second and bursts are represented as 1024 kilobits per second. Default rate 0 pir max — The max default specifies the amount of bandwidth in kilobits per second (thousand bits per second).

  • Page 189

    Network QoS Policies In network mode of operation, the system supports use of forwarding class mapping to EXP bits for IP interface, forwarding class mapping to DSCP and Dot1p bits for network ports. In access-uplink mode of operation it allows the user to specify the FC mapping to Dot1p bits for access-uplink ports. Syntax [no] fc fc-name Context...

  • Page 190

    Network QoS Policy Command Reference If the de-value is specifically mentioned in the command line it means this value is to be used for all the packets of this forwarding class regardless of their in/out of profile status. Parameters de-value — Specifies the DEI value to use for this forwarding class. Values 0 or 1 dot1p...

  • Page 191

    Network QoS Policies dot1p-in-profile Syntax dot1p-in-profile dot1p-priority no dot1p-in-profile Context config>qos>network>egress>fc Description Platforms Supported: 7210 SAS-M network mode, 7210 SAS-M access-uplink mode and 7210 SAS- T access-uplink mode. The command will add the capability to mark on an egress the in and out of profile status through a certain dot1p combination, similarly with the DEI options.

  • Page 192

    Network QoS Policy Command Reference dot1p-out-profile Syntax dot1p-out-profile dot1p-priority no dot1p-out-profile Context config>qos>network>egress>fc Description Platforms Supported: 7210 SAS-M network mode, 7210 SAS-M access-uplink mode and 7210 SAS- T access-uplink mode. The command will add the capability to mark on an egress the in and out of profile status via a certain dot1p combination, similarly with the DEI options.

  • Page 193

    Network QoS Policies queue Syntax queue queue-id create no queue Context config>qos>network Description Platforms Supported: 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-M (both access-uplink and network mode) and 7210 SAS-T (access-uplink and network mode). This command creates the context to modify Queue parameters associated with a particular queue. The no form of this command deletes the queue.

  • Page 194

    Network QoS Policy Command Reference dscp-out-profile Syntax dscp-out-profile dscp-name no dscp-out-profile Context config>qos>network >egress>fc fc-name Description Platforms Supported: 7210 SAS-M network mode, 7210 SAS-M and 7210 SAS-T Access-uplink mode. This command specifies the out-of-profile DSCP name for the forwarding class. When marking is set, the corresponding DSCP value is used to mark all IP packets with out-of-profile status, on the egress of this forwarding class queue.

  • Page 195: Show Commands

    Network QoS Policies Parameters lsp-exp-value — The 3-bit LSP EXP bit value, expressed as a decimal integer. Values 0 — 7 Default none lsp-exp-out-profile Syntax lsp-exp-out-profile lsp-exp-value no lsp-exp-out-profile Context config>qos>network policy-id>egress>fc fc-name Description Platforms Supported: 7210 SAS-M network mode. This command specifies the out-of-profile LSP EXP value for the forwarding class.

  • Page 196

    Network QoS Policy Command Reference Parameters policy-id — Displays information for the specific policy ID. Values 1 — 65535 Default all network policies detail — Includes information about ingress and egress EXP bit mappings and network policy interface associations. (for devices operating in Network mode) detail —...

  • Page 197

    Network QoS Policies Table 46: Show QoS Network Output Fields (Continued) Label Description Accounting Packet-based Specifies that the meters associated with this policy do not account for packet framing overheads (such as Ethernet the Inter Frame Gap (IFG) and the preamble), while accounting for the bandwidth to be used by this flow.

  • Page 198

    Network QoS Policy Command Reference Scope : Template Policy Type : port Accounting : packet-based Description : Default network-port QoS policy. ------------------------------------------------------------------------------- DSCP Forwarding Class Profile ------------------------------------------------------------------------------- af11 af12 af41 ------------------------------------------------------------------------------- Dot1p Bit Map Forwarding Class Profile ------------------------------------------------------------------------------- No Matching Entries ------------------------------------------------------------------------------- Meter Mode CIR Admin...

  • Page 199

    Network QoS Policies Out-of-Profile : af41 In-Profile : af41 - Dot1p Mapping Out-of-Profile : 4 In-Profile FC Value FC Name : ef - DSCP Mapping Out-of-Profile : ef In-Profile : ef - Dot1p Mapping Out-of-Profile : 5 In-Profile FC Value FC Name : h1 - DSCP Mapping...

  • Page 200

    Network QoS Policy Command Reference =============================================================================== QoS Network Policy =============================================================================== Network Policy (2) ------------------------------------------------------------------------------- Policy-id Remark : False Forward Class : be Profile : Out Attach Mode : mpls Config Mode : mpls Scope : Template Policy Type : IpInterface Accounting : packet-based Profile Policy : 1...

  • Page 201

    Network QoS Policies Out-of-Profile : 5 In-Profile FC Value FC Name : h1 - LSP EXP Bit Mapping Out-of-Profile : 6 In-Profile FC Value FC Name : nc - LSP EXP Bit Mapping Out-of-Profile : 7 In-Profile ------------------------------------------------------------------------------- Interface Association ------------------------------------------------------------------------------- Interface : system...

  • Page 202

    Network QoS Policy Command Reference TrTcm_CA 4000 closest 7000 closest 4000 7000 TrTcm_CA 4000 closest 7000 closest 4000 7000 TrTcm_CA 4000 closest 7000 closest 4000 7000 TrTcm_CA 4000 closest 7000 closest 4000 7000 TrTcm_CA 7000 closest 7000 closest 7000 7000 TrTcm_CA 4000 closest...

  • Page 203

    Network QoS Policies Table 47: Show QoS Network Output Fields (Continued) Label Description Description A text string that helps identify the policy’s context in the configuration file. Forward Class/ Specifies the forwarding class name. FC Name Profile Specifies the Dot1p marking for the packets which are out-of-profile, egressing on this queue.

  • Page 204

    Network QoS Policy Command Reference ------------------------------------------------------------------------------- af11 af12 af41 ------------------------------------------------------------------------------- Dot1p Bit Map Forwarding Class Profile ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Meter Mode CIR Admin CIR Rule PIR Admin PIR Rule CBS Admin MBS Admin ------------------------------------------------------------------------------- TrTcm1_CA closest closest ------------------------------------------------------------------------------- UCastM MCastM ------------------------------------------------------------------------------- No FC-Map Entries Found.

  • Page 205

    Network QoS Policies Out-of-Profile : af22 In-Profile : af21 - Dot1p Mapping Out-of-Profile : 2 In-Profile FC Value FC Name : h2 - DSCP Mapping Out-of-Profile : af41 In-Profile : af41 - Dot1p Mapping Out-of-Profile : 4 In-Profile FC Value FC Name : ef - DSCP Mapping...

  • Page 206

    Network QoS Policy Command Reference =============================================================================== *A:SAS-M-A0-2>show>qos# mpls-lsp-exp-profile-map Syntax mpls-lsp-exp-profile-map [policy-id] [detail] Context show>qos Description This command displays profile policy information. Parameters policy-id — Displays information for the specific policy ID. Values 1 — 65535 detail — Displays detail policy information. Output Table 48: Show QoS Network Output Fields Label...

  • Page 207

    Network QoS Policies =============================================================================== *A:7210SAS>show>qos# mpls-lsp-exp-profile-map 1 detail =============================================================================== QoS MPLS LSP EXP Profile Maps =============================================================================== ------------------------------------------------------------------------------- Profile Map-id Description : Default MPLS LSP EXP Profile Map policy ------------------------------------------------------------------------------- Profile ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Network Policy Associations ------------------------------------------------------------------------------- Network Policy Id ------------------------------------------------------------------------------- =============================================================================== *A:7210-SAS>show>qos# 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 208

    Network QoS Policy Command Reference 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 209: Network Queue Qos Policies

    Network Queue QoS Policies In This Section This section provides information to configure network queue QoS policies using the command line interface. Topics in this section include: • Overview • Basic Configurations • Default Network Queue Policy Values • Service Management Tasks Overview Network Queue policies define the network egress queue parameters.

  • Page 210

    Basic Configurations • On 7210 SAS-M (both access-uplink and network mode) it defines 8 forwarding classes and assigns 8 queues, one to each FC. • On 7210 SAS-T (both access-uplink and network mode) it defines 8 forwarding classes and assigns 8 queues, one to each FC. •...

  • Page 211: Applying Network Queue Policies

    Network Queue QoS Policies adaptation-rule [cir adaptation-rule] [pir adaptation-rule] *A:Dut-B>config>qos>network-queue# info detail ---------------------------------------------- description "Default network queue QoS policy." queue 1 rate cir 0 pir 100 adaptation-rule cir closest pir closest exit queue 2 rate cir 25 pir 100 adaptation-rule cir closest pir closest exit queue 3 rate cir 25 pir 100...

  • Page 212: Applying Network Queue Configuration In Network Mode

    Basic Configurations Applying Network Queue configuration in Network mode Use the following CLI syntax to apply a network queue policy to an Ethernet port in network mode of operation. The network-queue policy can only be applied on a network port. CLI Syntax: config>port# ethernet...

  • Page 213: Default Network Queue Policy Values

    Network Queue QoS Policies exit Default Network Queue Policy Values The default network queue policies are identified as policy-id default. The default policies cannot be modified or deleted for 7210 SAS-M and 7210 SAS-T (Access-uplink and Network modes), 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE devices. A:qos1# show qos network-queue default detail =============================================================================== QoS Network Queue Policy...

  • Page 214

    Default Network Queue Policy Values Port-id : 1/1/4 Port-id : 1/1/8 Port-id : 1/1/9 Port-id : 1/1/10 Port-id : 1/1/12 Port-id : 1/1/13 Port-id : 1/1/14 Port-id : 1/1/15 Port-id : 1/1/16 Port-id : 1/1/17 Port-id : 1/1/18 Port-id : 1/1/19 Port-id : 1/1/20 Port-id : 1/1/21 Port-id : 1/1/22...

  • Page 215

    Network Queue QoS Policies rate 10 pir 100 adaptation-rule cir closest pir closest exit ---------------------------------------------- *A:Dut-C>config>qos>network-queue# Default network Queue policy for 7210 SAS-Mxp The following displays default policy parameters for 7210 SAS-Mxp: *A:sim_dutc>config>qos>network-queue$ info detail ---------------------------------------------- no description queue 1 rate cir 0 pir 100 adaptation-rule cir closest pir closest queue-mgmt "default"...

  • Page 216

    Service Management Tasks Service Management Tasks This section discusses the following service management tasks: • Deleting Network Queue QoS Policies • Copying and Overwriting Network Queue QoS Policies • Editing Network Queue QoS Policies Deleting Network Queue QoS Policies A network queue policy is associated by default with all network ports (for devices operating in Network mode) and access uplink ports (for SAS-M and 7210 SAS-T in access uplink mode).

  • Page 217

    Network Queue QoS Policies echo "QoS Slope and Queue Policies Configuration" #-------------------------------------------------- ..network-queue "nq1-cbs" create queue 1 rate cir 0 pir 32 adaptation-rule cir max exit queue 2 exit queue 3 exit queue 4 exit queue 5 exit queue 6 rate cir 0 pir 4 exit queue 7...

  • Page 218: Editing Network Queue Qos Policies

    Service Management Tasks Editing Network Queue QoS Policies You can change existing policies, except the default policies, and entries in the CLI. The changes are applied immediately to all ports where the policy is applied. To prevent configuration errors use the copy command to make a duplicate of the original policy to a work area, make the edits, and then overwrite the original policy.

  • Page 219: Network Queue Qos Policy Command Reference

    Network Queue QoS Policies Network Queue QoS Policy Command Reference Command Hierarchies • Configuration Commands for 7210 SAS-M and 7210 SAS-T (network mode and access-uplink mode) • Configuration Commands for 7210 SAS-Mxp • Configuration Commands for 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE •...

  • Page 220: Configuration Commands For 7210 Sas-sx/s 1/10ge And 7210 Sas-sx 10/100ge

    Network Queue QoS Policy Command Reference — no weight Configuration Commands for 7210 SAS-Sx/S 1/10GE and 7210 SAS- Sx 10/100GE config — qos — network-queue policy-name [create] — description description-string — no description — queue queue-id — adaptation-rule [cir adaptation-rule] [pir adaptation-rule] —...

  • Page 221

    Network Queue QoS Policies Command Descriptions Configuration Commands Generic Commands description Syntax description description-string no description Context config>qos>network-queue Description Platforms Supported: 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-M (both access-uplink and network mode) and 7210 SAS-T (access-uplink and network mode). This command creates a text description stored in the configuration file for a configuration context.

  • Page 222: Network Queue Qos Policy Commands

    Network Queue QoS Policy Command Reference This command copies or overwrites existing network queue QoS policies to another network queue policy ID. The copy command is a configuration level maintenance tool used to create new policies using existing policies. It also allows bulk modifications to an existing policy with the use of the overwrite keyword. Parameters network-queue src-name dst-name —...

  • Page 223: Network Queue Qos Policy Queue Commands

    Network Queue QoS Policies Network Queue QoS Policy Queue Commands queue Syntax queue queue-id Context config>qos>network-queue Description Platforms Supported: 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-M (both access-uplink and network mode) and 7210 SAS-T (access-uplink and network mode). This command enables the context to configure a QoS network-queue policy queue.

  • Page 224

    Network Queue QoS Policy Command Reference This command defines the method used by the system to derive the operational CIR and PIR settings when the queue is provisioned in hardware. For the CIR and PIR parameters individually, the system attempts to find the best operational rate depending on the defined constraint. The no form of the command removes any explicitly defined constraints used to derive the operational CIR and PIR created by the application of the policy.

  • Page 225

    Network Queue QoS Policies Parameters strict — If a queue is configured in strict mode, the scheduler schedules the queue in order of their priority in the 2 passes, the CIR loop and the PIR loop. weighted — If a queue is configured in weighted mode, then the scheduler examines these queues in 2 passes - CIR loop and a PIR loop.

  • Page 226

    Network Queue QoS Policy Command Reference The no form of the command returns all queues created with the queue-id by association with the QoS policy to the default PIR and CIR parameters (100, 0). Parameters cir percent — Defines the percentage of the guaranteed rate allowed for the queue. When the rate command is executed, a valid CIR setting must be explicitly defined.

  • Page 227

    Network Queue QoS Policies Context show>qos Description Platforms Supported: 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-M (both access-uplink and network mode) and 7210 SAS-T (access-uplink and network mode). This command displays network queue policy information. Parameters network-queue-policy-name — The name of the network queue policy. Values Valid names consist of any string up to 32 characters long composed of printable, 7-bit ASCII characters.

  • Page 228

    Network Queue QoS Policy Command Reference *A:card-1# show qos network-queue nq1 detail =============================================================================== QoS Network Queue Policy =============================================================================== Network Queue Policy (nq1) ------------------------------------------------------------------------------- Policy : nq1 Accounting : packet-based Description : this is a network-queue policy ------------------------------------------------------------------------------- Queue CIR CIR Rule PIR Rule ------------------------------------------------------------------------------- 12.50...

  • Page 229

    Service Ingress QoS Policies In This Section This section provides information to configure SAP ingress QoS policies using the command line interface. Topics in this section include: • Overview → Resource Allocation for Service Ingress QoS policies → Create Service Ingress QoS Policies →...

  • Page 230: Default Sap Ingress Policy

    For information about the tasks and commands necessary to access the command line interface and to configure and maintain your 7210 SAS devices, refer to the CLI Usage chapter in the 7210 SAS OS Basic System Configuration Guide. Default SAP Ingress Policy The default policy 1, maps all traffic to default forwarding class 'be' and maps FC 'be' to meter 1.

  • Page 231: Resource Allocation For Sap Ingress Policy

    Service Ingress QoS Policies Resource Allocation for SAP ingress policy Use of Index file by SAP QoS Ingress policy 7210 uses an index file to store the map which indicates the QoS resource allocation to SAPs. This file is used on reboot to ensure that all the SAPs that were created successfully before reboot can be created again on a reboot.

  • Page 232

    Overview Note: When associating a meter with a FC for BUM traffic, the software does not validate if meter is a multipoint meter thus allowing user to use a single meter for unicast and BUM traffic. This implies efficient use of SAP ingress qos resources.From release 4.0R4 onwards when the "multipoint"...

  • Page 233

    Service Ingress QoS Policies *7210-SAS>config>qos# sap-ingress 12 *7210-SAS>config>qos>sap-ingress$ info ---------------------------------------------- configure> qos> sap-ingress 10 create meter 1 create exit meter 3 create exit default-fc be fc be meter 3 multicast-meter 3 exit fc af meter 3 exit exit ---------------------------------------------- Starting with the above policy, if the user now executes the command "configure qos sap- ingress <id>...

  • Page 234: Service Ingress Meter Selection Rules

    Overview In the above example, if the user executes "configure qos sap-ingress <id> fc be no unknown-meter", then meter "3" is used for all traffic types classified to FC “be”. But, if the default meter "11" is defined in the policy, then FC “be” uses meter “11” for BUM traffic. Service Ingress Meter Selection Rules The following are rules for meter selection by different traffic types under various configurations for VPLS services:...

  • Page 235

    Service Ingress QoS Policies The following describes the usage of meters when meter in a VPLS service “11” is defined in the policy: • If a FC is created without explicit meters, use the default meter “1” for unicast traffic and default meter “11”...

  • Page 236: Service Ingress Policy Configuration Considerations

    Overview • If a FC is created with an explicit unicast meter, use that meter for unicast traffic and use default meter “11” for multicast traffic. • If a FC is created with an explicit unicast meter and explicit multicast meter, use the unicast meter for unicast traffic and multicast meter for multicast traffic.

  • Page 237: Resource Allocation For Service Ingress Qos Policies

    Service Ingress QoS Policies validates that the amount of qos resources specfied with the command num-qos- classifiers is sufficient for the match criteria, forwarding class and service specified and the resources are available in hardware. On failure of the validation, the software disallows the association of the SAP ingress policy with the SAP.

  • Page 238

    Overview By default, the system allocates resources for SAP ingress QoS policies to maintain backward compatibility with release 4.0 and allocates resources for MAC criteria and IP criteria (by setting it to 'max'). Setting the value to ‘max’ allows each match criteria to use the available SAP ingress QoS resources on first-come-first-served model.

  • Page 239

    Service Ingress QoS Policies ipv6-criteria (128-bit) in the hardware. Software allocates entries from the ipv6- criteria pool if the SAP ingress QoS policy uses both ipv6-criteria (any or IPv6 DSCP) entries and ipv4-criteria (any or IPv4 DSCP) entries or if the SAP ingress QoS policy uses only IPv6 criteria (any or IPv6 DSCP) or if the SAP ingress QoS policy uses ipv4 criteria any and there are no resources available in the IPv4 criteria (as explained above).

  • Page 240: Computation Of Resources Used Per Sap Ingress Policy

    Overview → If there are no chunks available for accommodating a SAP that is associated with default or dot1p-only or a dscp-only SAP ingress policy, the software allocates resources against mac-criteria if the SAP is configured in a VLL or VPLS service.

  • Page 241

    Service Ingress QoS Policies The user is allowed to mix and match SAPs with different QoS resources (that is, using different values of TQ). The following determines the number of QoS resources to be allocated for an SAP: • Number of match-criteria entries used to identify the FC. •...

  • Page 242

    Overview • If a FC is in use and is created with an explicit unicast meter and explicit multicast meter, use the unicast meter for unicast traffic and multicast meter for all other kinds of traffic. This requires two classification entries in hardware. •...

  • Page 243

    Service Ingress QoS Policies where FCi (unicast), FCi (multicast), FCi (broadcast), and FCi (unknown-unicast) are set to a value of 1 if this FC uses classifier to identify traffic-type unicast, multicast, broadcast and unknown-unicast respectively. FCi (unicast), FCi (multicast), FCi (broadcast), and FCi (unknown-unicast) are set to a value of 0 if this FC does not use a classifier to identify this traffic-type.

  • Page 244

    Basic Configurations Basic Configurations A basic service ingress QoS policy must conform to the following: • Have a unique service ingress QoS policy ID. • Allocates number of classifier and meter resources needed for use • Have a QoS policy scope of template or exclusive. •...

  • Page 245: Service Ingress Qos Meter

    Service Ingress QoS Policies • On platforms where applicable, specify the appropriate classification criteria - IPv4/ IPv6 or MAC criteria or both IP and MAC criteria. You can define IPv4/IPv6, MAC- based and MAC and IP based SAP ingress policies to select the appropriate ingress meter and corresponding forwarding class for matched traffic.

  • Page 246: Service Ingress Ip Match Criteria

    Basic Configurations exit meter 5 create cbs 64 mbs 128 rate cir 1500 pir 1500 exit meter 6 create mode srtcm rate cir 2500 pir 2500 exit meter 7 create cbs 256 mbs 512 rate cir 100 pir 36 exit meter 8 create cbs 256 mbs 512...

  • Page 247: Service Ingress Mac Match Criteria

    Service Ingress QoS Policies 7210-SAS>config>qos>sap-ingress# info ---------------------------------------------- num-qos-classifiers 32 meter 1 create exit meter 11 multipoint create exit fc "h2" create exit ip-criteria any entry 16 create description "test" match exit action fc "be" exit exit ---------------------------------------------- 7210-SAS>config>qos>sap-ingress# 7210-SAS>config>qos>sap-ingress# info ---------------------------------------------- num-qos-classifiers 4 meter 1 create...

  • Page 248: Examples For Computation Of Resources Required For Service Ingress Qos Policy

    Basic Configurations meter 1 create exit meter 11 multipoint create exit mac-criteria dot1p-only entry 25 create match exit no action exit exit default-fc "h1" ---------------------------------------------- 7210-SAS>config>qos>sap-ingress# Examples for Computation of resources required for Service ingress QoS policy The resource calculation shown for VLL is also applicable for VPRN services. Example 1 sap-ingress 10 create description...

  • Page 249

    Service Ingress QoS Policies entry 2 create match dot1p 5 action fc l1 exit entry 3 create match dot1p 6 action fc h2 exit exit exit In the example above, assuming the policy is attached to a SAP in a VPLS service, compute the number of classification entries per FC as follows: FCnc = 0 + 0 + 0 + 0 = 0 FCh1 = 0 + 0 + 0 + 0 = 0...

  • Page 250

    Basic Configurations As can be seen here, using the same policy for Epipe SAP can lead to inefficient use of resources. Hence, it is recommended to create a different policy with the required number of resources (that is, with num-qos-classifiers 4) Example 1a (Default multipoint meter 11 is not used): sap-ingress 10 create description...

  • Page 251

    Service Ingress QoS Policies FCh2 = 1 + 0 + 0 + 0 = 1 Since this FC uses unicast meter for all traffic types, we need an entry to classify all traffic types to this FC explicitly. FCl1 = 1 + 0 + 0 + 0 = 1 FCaf = 1 + 0 + 0 + 0 = 1 FCl2 = 0 + 0 + 0 + 0 = 0 FCbe = 1 + 0 + 0 + 0 = 1...

  • Page 252

    Basic Configurations rate cir100 pir 100 exit meter 2 create rate cir 1 pir 20 exit scope template default-fc be fc be create meter 3 broadcast-meter 2 exit fc af create meter 3 broadcast-meter 2 exit fc l1 create meter 3 broadcast-meter 2 exit fc h2 create...

  • Page 253

    Service Ingress QoS Policies Using the above equation, to get the total classification entries used = 12 (since three explicit match criteria entries map to each of FC H2, L1, and AF along with a default classification rule for BE). The number of meters used = 3 (since FCs use only meter #2, meter #3 and meter #11).

  • Page 254

    Basic Configurations broadcast-meter 2 exit fc h2 create meter broadcast-meter 2 exit mac-criteria dot1p-only entry create match dot1p action fc af exit entry 2 create match dot1p 5 action fc l1 exit entry 3 create match dot1p action fc h2 exit exit In the example above, assuming the policy is attached to a SAP in a VPLS service,...

  • Page 255

    Service Ingress QoS Policies FCl2 = 0 + 0 + 0 + 0 = 0 FCbe = 1 + 0 + 0 + 0 = 1 Using the above equation, to get total classification entries used = 4 and Meters used = 1. As can be seen here, using the same policy for Epipe SAP can lead to inefficient use of resources.

  • Page 256

    Basic Configurations action fc af exit entry 2 create match dot1p 5 action fc l1 exit entry 3 create match dot1p 6 action fc h2 exit entry 4 create match dot1p 3 action fc h1 exit exit exit In the example above, assuming the policy is attached to a SAP in a VPLS service, the classification entries used per FC are: FCnc = 0 + 0 + 0 + 0 = 0 FCh1 = 1 + 1 + 1 + 1 = 4...

  • Page 257

    Service Ingress QoS Policies If the same policy were to be used for a SAP in an Epipe service, then since all traffic is classified to a unicast traffic type and since only unicast meters are used, the following results: FCnc = 0 + 0 + 0 + 0 = 0 FCh1 = 1 + 0 + 0 + 0 = 1 FCef = 0 + 0 + 0 + 0 = 0...

  • Page 258

    Basic Configurations unknown-meter 4 exit mac-criteria dot1p-only entry create match dot1p action fc af exit entry 2 create match dot1p 5 action fc l1 exit entry 3 create match dot1p action fc h2 exit entry 4 create match dot1p 3 action fc h1 exit exit...

  • Page 259

    Service Ingress QoS Policies Since no explicit meters are configured for FC be, it uses meter 1 for all traffic types and needs one entry is needed to identify these traffic types. Using the above equation, the total classification entries used = 12 and meters used = 5. The num-qos-classifiers can be set to 12 (the minimum value).

  • Page 260

    Basic Configurations exit scope template default-fc be af create meter 3 broadcast-meter 2 multicast-meter exit fc l1 create meter 3 broadcast-meter 2 exit fc h2 create meter 3 broadcast-meter 2 exit fc h1 create meter 5 broadcast-meter 4 multicast-meter unknown-meter exit fc ef create meter 6...

  • Page 261

    Service Ingress QoS Policies In the example above, assuming the policy is attached to a SAP in a VPLS service, compute the classification entries per FC as: FCnc = 1 + 1 + 1 + 0 = 3 Since this FC uses unicast, broadcast and multicast meter, three entries are needed to identify these traffic types explicitly.

  • Page 262

    Basic Configurations Using the above equation, the total classification entries used = 7 and meters used = 4. As can be seen here, using the same policy for Epipe SAP can lead to inefficient use of resources. Hence, it is recommended to create a different policy with the required number of resources (i.e.

  • Page 263

    Service Ingress QoS Policies meter 6 broadcast-meter 2 multicast-meter 8 exit fc nc create meter 6 broadcast-meter 2 multicast-meter 8 exit mac-criteria dot1p-only entry create match dot1p action fc af exit entry create match dot1p 5 action fc l1 exit entry create match dot1p...

  • Page 264

    Basic Configurations Since this FC uses unicast, broadcast and multicast meter, three entries are needed to identify these traffic types explicitly. Unknown-unicast traffic type is classified using the same entry as multicast traffic type and uses the same meter. FCh2 = 1 + 1 + 1 + 0 = 3 Since this FC uses unicast meter and broadcast meter, two entries are needed to identify these traffic types explicitly.

  • Page 265

    Service Ingress QoS Policies Example 5 sap-ingress 10 create description “example-policy-3” num-qos-classifiers 32 meter 1 create rate cir 100 pir 100 exit meter 11 multipoint create rate cir 1 pir 20 exit meter 3 create rate cir 100 pir 100 exit meter 2 create rate cir 1 pir 20...

  • Page 266

    Basic Configurations action fc af exit entry 2 create match dot1p 5 action fc l1 exit entry 3 create match dot1p 6 action fc h2 exit entry 4 create match dot1p 3 action fc h1 exit entry 5 create match dot1p 2 action fc ef exit entry 6 create...

  • Page 267

    Service Ingress QoS Policies FCaf = 1 + 1 + 1 + 0 = 3 Since this FC uses unicast, broadcast and multicast meter, three entries are needed to identify these traffic types explicitly. Unknown-unicast traffic type is classified using the same entry as multicast traffic type and uses the same meter.

  • Page 268

    Basic Configurations fc l1 create meter 3 multicast-meter 4 exit fc h2 create meter 3 exit mac-criteria dot1p-only entry 1 create match dot1p 7 action fc af exit entry 2 create match dot1p 5 action fc l1 exit entry 3 create match dot1p 6 action fc h2 exit...

  • Page 269

    Service Ingress QoS Policies FCef = 0 + 0 + 0 + 0 = 0 FCh2 = 1 + 0 + 0 + 0 = 1 FCl1 = 1 + 0 + 0 + 0 = 1 FCaf = 1 + 0 + 0 + 0 = 1 FCl2 = 0 + 0 + 0 + 0 = 0 FCbe = 1 + 0 + 0 + 0 = 1 Using the above equation, the total classification entries used = 4 and meters used = 2.

  • Page 270

    Basic Configurations Since this FC uses unicast, broadcast and multicast meter, three entries are needed to identify these traffic types explicitly. Unknown-unicast traffic type is classified using the same entry as multicast traffic type and uses the same meter. Using the above equation, the total classification entries used = 5 and meters used = 4. If the same policy were to be used for a SAP in an Epipe service, then since all traffic is classified to a unicast traffic type and since only unicast meters are used, the following: FCnc = 0 + 0 + 0 + 0 = 0...

  • Page 271

    Service Ingress QoS Policies exit In the example above, assuming the policy is attached to a SAP in a VPLS service, the following number of classification entries per FC: FCnc = 0 + 0 + 0 + 0 = 0 FCh1 = 0 + 0 + 0 + 0 = 0 FCef = 0 + 0 + 0 + 0 = 0 FCh2 = 0 + 0 + 0 + 0 = 0...

  • Page 272

    Basic Configurations Example 9 sap-ingress 10 create num-qos-classifiers 256 meter 1 create exit meter 11 multipoint create exit meter 3 create exit meter 4 create exit fc be create meter 1 broadcast-meter 11 mulitcast-meter exit fc af create meter 3 broadcast-meter 11 multicast-meter exit...

  • Page 273

    Service Ingress QoS Policies entry 10 create match dscp af11 action fc af exit entry 11 create match dscp cp11 action fc af exit entry 12 create match dscp af12 action fc af exit entry 13 create match dscp cp13 action fc af exit entry 14...

  • Page 274

    Basic Configurations exit entry 25 create match dscp cp25 action fc af exit entry 26 create match dscp af31 action fc af exit entry 27 create match dscp cp27 action fc af exit entry 28 create match dscp af32 action fc af exit entry 29 create...

  • Page 275

    Service Ingress QoS Policies action fc af exit entry 40 create match dscp cs5 action fc af exit entry 41 create match dscp cp41 action fc af exit entry 42 create match dscp cp42 action fc af exit entry 43 create match dscp cp43 action...

  • Page 276

    Basic Configurations Since this FC uses unicast meter, an entry is needed to identify these traffic types explicitly. Another entry is needed to classify broadcast, multicast and unknown-unicast traffic type to the same FC and use the default meter #11. FCl2 = 0 + 0 + 0 + 0 = 0 FCbe = 1 + 1 + 1 + 0 = 3 Since this FC uses unicast, broadcast and multicast meter, three entries are needed to identify...

  • Page 277

    Service Ingress QoS Policies meter 3 create exit meter 4 create exit meter 11 create exit fc be create meter 1 broadcast-meter 11 multicast-meter 4 exit fc af create meter 3 broadcast-meter 11 multicast-meter 4 exit default-fc be ip-criteria dscp-only entry 1 create match dscp cp1...

  • Page 278

    Basic Configurations exit entry 11 create match dscp cp11 action fc af exit entry 12 create match dscp af12 action fc af exit entry 13 create match dscp cp13 action fc af exit entry 14 create match dscp af13 action fc af exit entry 15 create...

  • Page 279

    Service Ingress QoS Policies action fc af exit entry 26 create match dscp af31 action fc af exit entry 27 create match dscp cp27 action fc af exit entry 28 create match dscp af32 action fc af exit entry 29 create match dscp cp29 action fc af...

  • Page 280

    Basic Configurations match dscp cs5 action fc af exit entry 41 create match dscp cp41 action fc af exit entry 42 create match dscp cp42 action fc af exit entry 43 create match dscp cp43 action fc af exit entry 44 create match dscp cp44 action fc af...

  • Page 281

    Service Ingress QoS Policies Since this FC uses unicast, broadcast and multicast meter, three entries are required to identify these traffic types explicitly. Unknown-unicast traffic type is classified using the same entry as multicast traffic type and uses the same meter. Additionally note that meter 11 is not defined to be multipoint meter, but is used as a normal unicast meter.

  • Page 282

    Basic Configurations Example 10 sap-ingress 10 create description “example-policy-1” num-qos-classifiers 4 meter 1 create rate cir 0 pir max exit meter 11 multipoint create rate cir 0 pir max exit scope template default-fc l2 fc l2 create meter 1 exit fc af create meter 1 exit...

  • Page 283

    Service Ingress QoS Policies FCl1 = 0 + 0 + 0 + 0 = 0 FCaf = 1 + 0 + 0 + 0 = 1 FCl2 = 1 + 0 + 0 + 0 = 1 FCbe = 0 + 0 + 0 + 0 = 0 Using the above equation, calculate the total classification entries used = 2 and meters used = 1.

  • Page 284: Applying Service Ingress Policies

    Basic Configurations FCh1 = 0 + 0 + 0 + 0 = 0 FCef = 0 + 0 + 0 + 0 = 0 FCh2 = 0 + 0 + 0 + 0 = 0 FCl1 = 0 + 0 + 0 + 0 = 0 FCaf = 0 + 0 + 0 + 0 = 0 FCl2 = 0 + 0 + 0 + 0 = 0 FCbe = 1 + 0 + 0 + 0 = 1...

  • Page 285: Vprn

    Service Ingress QoS Policies A:ALA-7>config>service# info ---------------------------------------------- vpls 700 customer 7 vpn 700 create description "test" shutdown exit sap 1/1/9:10 create ingress qos 100 exit exit exit ---------------------------------------------- A:ALA-7>config>service# VPRN The following output displays a VPRN service configuration. A:ALA-7>config>service# info ---------------------------------------------- vprn 1 customer 1 create autonomous-system 10000...

  • Page 286

    Service Management Tasks ---------------------------------------------- ies 1 customer 1 create interface "to-c1" create address 11.1.0.1/24 sap 1/1/10:100 create ingress qos 100 exit exit exit no shutdown exit ---------------------------------------------- A:ALA-7>config>service# Service Management Tasks This section discusses the following service management tasks: • Deleting QoS Policies •...

  • Page 287: Remove A Qos Policy From Service Sap(s)

    Service Ingress QoS Policies Remove a QoS Policy from Service SAP(s) The following Epipe service output examples show that the SAP service ingress reverted to policy-id “1” when the non-default policies were removed from the configuration. A:ALA-104>config>service>epipe# info detail ---------------------------------------------- description "Distributed Epipe service to west coast"...

  • Page 288

    Service Management Tasks meter 1 create exit meter 2 multipoint create exit meter 10 create rate cir 11000 exit meter 11 multipoint create exit exit sap-ingress 200 create description "Used on VPN sap" meter 1 create exit meter 2 multipoint create exit meter 10 create rate cir 11000...

  • Page 289: Service Sap Qos Policy Command Reference

    Service Ingress QoS Policies Service SAP QoS Policy Command Reference • Service Ingress QoS Policy Commands • Operational Commands • Show Commands Command Hierarchy Service Ingress QoS Policy Commands config — qos — [no] sap-ingress policy-id — default-fc fc [profile {in|out|use-dei}] —...

  • Page 290

    Service SAP QoS Policy Command Reference — src-port {eq} src-port-number — no src-port — renum [old-entry-id new-entry-id] — [no] ipv6-criteria [any | dscp-only] [IPv6 Match Criteria] — [no] entry entry-id [create] — action [fc fc-name][profile {in |out}] — no action —...

  • Page 291: Operational Commands

    Service Ingress QoS Policies — no rate — scope {exclusive | template} — no scope Operational Commands config — qos — copy sap-ingress src-pol dst-pol [overwrite] Show Commands show — qos — sap-ingress policy-id [detail | association | match-criteria] 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 292

    Service SAP QoS Policy Command Reference Command Descriptions Configuration Commands Generic Commands description Syntax description description-string no description Context config>qos>sap-ingress config>qos>sap-ingress>ip-criteria>entry config>qos>sap-ingress>mac-criteria>entry Description Platforms Supported: 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-M (both access-uplink and network mode) and 7210 SAS-T (access-uplink and network mode). This command creates a text description stored in the configuration file for a configuration context.

  • Page 293

    Service Ingress QoS Policies Context config>qos Description Platforms Supported: 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-M (both access-uplink and network mode) and 7210 SAS-T (access-uplink and network mode). This command copies existing QoS policy entries for a QoS policy-id to another QoS policy-id. The copy command is a configuration level maintenance tool used to create new policies using existing policies.

  • Page 294

    Service SAP QoS Policy Command Reference Context config>qos Description Platforms Supported: 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-M (both access-uplink and network mode) and 7210 SAS-T (access-uplink and network mode). This command is used to create or edit the ingress policy. The ingress policy defines the Service Level Agreement (SLA) enforcement service packets receive as they ingress a SAP.

  • Page 295

    Service Ingress QoS Policies scope Syntax scope {exclusive | template} no scope Context config>qos>sap-ingress Description Platforms Supported: 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-M (both access-uplink and network mode) and 7210 SAS-T (access-uplink and network mode). This command configures the Service Ingress QoS policy scope as exclusive or template. The no form of this command sets the scope of the policy to the default of template.

  • Page 296

    Service SAP QoS Policy Command Reference profile {in | out} — The profile assignment action is optional. When specified, packets matching the classification entry will be explicitly classifier to either in-profile or out-of-profile. The remove the profile action for an classification entry, the action command must be re-executed without the profile action defined.

  • Page 297

    This command is used to enter the context to create or edit policy entries that specify IP criteria DiffServ code point. 7210 SAS OS implementation will exit on the first match found and execute the actions in accordance with the accompanying action command. For this reason entries must be sequenced correctly from most to least explicit.

  • Page 298

    Service SAP QoS Policy Command Reference policy-id — -The policy-id that uniquely identifies the policy. Values 1 — 65535 ipv6-criteria Syntax [no] ipv6-criteria [any | dscp-only] policy-id Context config>qos>sap-ingress Description Platforms Supported: 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-M (both access-uplink and network mode) and 7210 SAS-T (access-uplink and network mode).

  • Page 299

    This command is used to enter the node to create or edit policy entries that specify MAC criteria. 7210 SAS OS implementation will exit on the first match found and execute the actions in accordance with the accompanying action command. For this reason entries must be sequenced correctly from most to least explicit.

  • Page 300

    Service SAP QoS Policy Command Reference The keyword 'ipv6' lets the user indicate that they plan to use the ipv6-criteria and the resources needed for this SAP ingress QoS policy must be allocated for the chunk allocated to IPv6 criteria. Default num-resources is set to a default value of 2 and no-ipv6 is use as the default keyword.

  • Page 301

    Service Ingress QoS Policies meter Syntax meter meter-id no meter Context config>qos>sap-ingress>fc Description Platforms Supported: 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-M (both access-uplink and network mode) and 7210 SAS-T (access-uplink and network mode). This command overrides the default unicast forwarding type meter mapping for fc fc-name. The specified meter-id must exist within the policy as a non-multipoint meter before the mapping can be made.

  • Page 302

    Service SAP QoS Policy Command Reference Parameters meter-id — Specifies an existing multipoint queue defined in the config>qos>sap-ingress context. Values 1— 32 Default queue-id — Specifies the queue-id for the queue. Values unknown-meter Syntax unknown-meter meter-id no unknown-meter Context config>qos>sap-ingress>fc Description Platforms Supported: 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-M (both access-uplink and network mode) and 7210 SAS-T (access-uplink and network mode).

  • Page 303

    Service Ingress QoS Policies Description Platforms Supported: 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-M (both access-uplink and network mode) and 7210 SAS-T (access-uplink and network mode). This mandatory command associates the forwarding class with specific IP or MAC criteria entry ID. The action command supports setting the forwarding class parameter.

  • Page 304

    Service SAP QoS Policy Command Reference config>qos>sap-ingress>mac-criteria Description Platforms Supported: 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-M (both access-uplink and network mode) and 7210 SAS-T (access-uplink and network mode). This command is used to create or edit an IP or MAC criteria entry for the policy. Multiple entries can be created using unique entry-id numbers.

  • Page 305

    Service Ingress QoS Policies Description Platforms Supported: 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-M (both access-uplink and network mode) and 7210 SAS-T (access-uplink and network mode). This command creates a context to configure match criteria for SAP QoS policy match criteria. When the match criteria have been satisfied the action associated with the match criteria is executed.

  • Page 306

    Service SAP QoS Policy Command Reference If more than one match criteria (within one match statement) are configured, then all criteria must be satisfied (AND function) before the action associated with the match is executed. A match context can consist of multiple match criteria, but multiple match statements cannot be entered per entry.

  • Page 307

    Service Ingress QoS Policies Parameters dscp-value — Specifies the DSCP value in either hexdecimal format, decimal format or binary format. Values [0..64] dscp-name — Specifies a dscp name that has been previously mapped to a value using the dscp- name command. The DiffServ code point can only be specified by its name. Values be, cp1, cp2, cp3, cp4, cp5, cp6, cp7, cs1, cp9, af11, cp11, af12, cp13, af13, cp15, cs2, cp17, af21, cp19, af22, cp21, af23, cp23,...

  • Page 308

    Service SAP QoS Policy Command Reference Parameters ip-address — The IP address of the destination IP or IPv6 interface. This address must be unique within the subnet and specified in dotted decimal notation. Values ipv4-prefix: a.b.c.d ipv4-prefix-length: 0 -- 32 ipv6-prefix: x:x:x:x:x:x:x:x (eight 16-bit pieces) x:x:x:x:x:x:d.d.d.d x: [0..FFFF]H...

  • Page 309

    Service Ingress QoS Policies Description Platforms Supported: 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-M (both access-uplink and network mode) and 7210 SAS-T (access-uplink and network mode). This command configures fragmented or non-fragmented IP packets as a SAP QoS policy match criterion.

  • Page 310

    Service SAP QoS Policy Command Reference mask — The mask to use for the match. src-ip Syntax src-ip {ip-address/mask | ip-address netmask} no src-ip Context config>qos>sap-ingress>ip-criteria>entry>match config>qos>sap-ingress>ipv6-criteria>entry>match Description Platforms Supported: 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-M (both access-uplink and network mode) and 7210 SAS-T (access-uplink and network mode). This command configures a source IP or IPv6 address range to be used as an SAP QoS policy match criterion.

  • Page 311

    Service Ingress QoS Policies mask — The subnet mask length, expressed as an integer or in dotted decimal notation. Values 0 — 32 netmask — Specify the subnet mask in dotted decimal notation. Values a.b.c.d (dotted quad equivalent of mask length) src-port Syntax src-port {eq} src-port-number...

  • Page 312

    Service SAP QoS Policy Command Reference Use the no form of this command to remove the dot1p value as the match criterion. Default None Parameters dot1p-value — Enter the IEEE 802.1p value in decimal. Values 0 — 7 dot1pmask — This 3-bit mask can be configured using the following formats: Format Style Format Syntax Example...

  • Page 313

    Service Ingress QoS Policies All packets with a source MAC OUI value of 00-03-FA subject to a match condition should be specified as: 0003FA000000 0x0FFFFF000000 Values 0x00000000000000 — 0xFFFFFFFFFFFF (hex) Default 0xFFFFFFFFFFFF (hex) (exact match) etype Syntax etype 0x0600..0xffff no etype Context config>qos>sap-ingress>mac-criteria>entry Description...

  • Page 314

    Service SAP QoS Policy Command Reference The no form of this command removes the source mac as the match criteria. Default none Parameters ieee-address — Enter the 48-bit IEEE mac address to be used as a match criterion. Values HH:HH:HH:HH:HH:HH or HH-HH-HH-HH-HH-HH where H is a hexadecimal digit ieee-address-mask —...

  • Page 315

    Service Ingress QoS Policies The multipoint meters are for multipoint-destined service traffic. Within non-multipoint services, such as Epipe services, all traffic is considered unicast due to the nature of the service type. Multicast and broadcast-destined traffic in an Epipe service will not be mapped to a multipoint service meter. When an ingress SAP QoS policy with multipoint meters is applied to an Epipe SAP, the multipoint meters are not created.

  • Page 316

    Service SAP QoS Policy Command Reference cir — Defines the constraints enforced when adapting the CIR rate defined within the meter rate command. The cir parameter requires a qualifier that defines the constraint used when deriving the operational CIR for the meter. When the cir parameter is not specified, the default constraint applies.

  • Page 317

    Service Ingress QoS Policies Context config>qos>sap-ingress>meter Description Platforms Supported: 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-M (both access-uplink and network mode) and 7210 SAS-T (access-uplink and network mode). This command is used to configure the meter to operate in either color-aware mode or color-blind mode.

  • Page 318

    Service SAP QoS Policy Command Reference Default 512kbits Parameters size — Specifies the size parameter is an integer expression of the number of kilobits reserved for the meter. For example, if a value of 100 KBits is desired, then enter the value 100. The bucket size is rounded off to the next highest 4096 bytes boundary.

  • Page 319

    Service Ingress QoS Policies trtcm2 — Implements the policing algorithm defined in RFC4115. Meters the packet stream and marks its packets either green, yellow, or red. A packet is marked red if it exceeds the PIR. Otherwise, it is marked either yellow or green depending on whether it exceeds or does not exceed the CIR.

  • Page 320

    Service SAP QoS Policy Command Reference The actual CIR rate is dependent on the meter’s adaptation-rule parameters and the hardware. Values 0 — 20000000, max pir pir-rate-in-kbps — Defines the administrative PIR rate, in kilobits, for the meter. When this command is executed, a valid PIR setting must be explicitly defined.

  • Page 321

    Service Ingress QoS Policies Label Description The ID that uniquely identifies the policy. Policy-Id Exclusive — Implies that this policy can only be applied to a single Scope SAP. Template — Implies that this policy can be applied to multiple SAPs on the router.

  • Page 322

    Service SAP QoS Policy Command Reference Label Description (Continued) Specifies the default broadcast forwarding type meters mapping. BCastM Specifies the default unknown unicast forwarding type meters UnknownM mapping. Specifies an IP or MAC criteria entry for the policy. Match Criteria Entry Specifies a DiffServ Code Point (DSCP) name used for an ingress SAP DSCP...

  • Page 323

    Service Ingress QoS Policies ------------------------------------------------------------------------------- Meter Mode CIR Admin CIR Rule PIR Admin PIR Rule CBS Admin MBS Admin ------------------------------------------------------------------------------- TrTcm closest closest TrTcm closest closest TrTcm closest closest TrTcm closest closest TrTcm closest closest TrTcm closest closest TrTcm closest closest TrTcm closest...

  • Page 324

    Service SAP QoS Policy Command Reference Description : (Not Specified) Src MAC Atm-Vci : Disabled Dst MAC Dot1p : 5/7 Ethernet-type : Disabled : h1 Entry Description : (Not Specified) Src MAC Atm-Vci : Disabled Dst MAC Dot1p : 6/7 Ethernet-type : Disabled : h2...

  • Page 325

    Service Ingress QoS Policies TrTcm closest closest TrTcm closest closest TrTcm closest closest ------------------------------------------------------------------------------- UCastM MCastM BCastM UnknownM ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Match Criteria ------------------------------------------------------------------------------- Entry Src MAC Dst MAC Dot1p : 7/7 Ethernet-type : Disabled : nc Entry Src MAC Dst MAC Dot1p : 6/7 Ethernet-type...

  • Page 326

    Service SAP QoS Policy Command Reference Associations ------------------------------------------------------------------------------- Service-Id : 102 (VPLS) Customer-Id - SAP : 1/1/3:102 - SAP : 1/1/7:102 =============================================================================== *A:qos1# For SAS-M: *A:qos1# show qos sap-ingress 102 detail =============================================================================== QoS Sap Ingress =============================================================================== ------------------------------------------------------------------------------- Sap Ingress Policy (102) ------------------------------------------------------------------------------- Policy-id : 102...

  • Page 327

    Service Ingress QoS Policies 500 Kbits TrTcm closest closest 10 Kbits 7 KBits ------------------------------------------------------------------------------- UCastM MCastM BCastM UnknownM ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Match Criteria ------------------------------------------------------------------------------- Entry Src MAC Dst MAC =============================================================================== *A:qos1# For SAS-Mxp *A:sim_dutc>config>qos>sap-ingress# info detail ---------------------------------------------- policy-name "default" description "Default SAP ingress QoS policy." num-qos-classifiers 2 no-ipv6 no ip-mac-match scope template...

  • Page 328

    Service SAP QoS Policy Command Reference Default FC : be Criteria-type : IP IP-Mac Rule Priority : None Mac Sub-Criteria : None IP Sub-Criteria : any IPv6 Enabled : False IPv6 Sub-Criteria : dscp Accounting : packet-based Classifiers Allowed Meters Allowed Classifiers Reqrd (VPLS) Meters Reqrd (VPLS) Classifiers Reqrd (L3 Mc) : 2...

  • Page 329

    Service Ingress QoS Policies ------------------------------------------------------------------------------- Sap Ingress Policy (2) ------------------------------------------------------------------------------- Policy-id Scope : Template Default FC : be Criteria-type : IP IP-Mac Rule Priority : None Mac Sub-Criteria : None IP Sub-Criteria : any IPv6 Enabled : False IPv6 Sub-Criteria : dscp Accounting : packet-based...

  • Page 330

    Service SAP QoS Policy Command Reference 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 331: In This Section

    Access Egress QoS Policies on 7210 SAS- M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE In This Section This section provides information to configure Access Egress QoS policies using the command line interface. Topics in this section include: •...

  • Page 332: Overview

    Overview Overview An access egress policy defines the queuing for the traffic egressing on the access ports. Access-egress queue policies are used at the Ethernet port and define the bandwidth distribution for the various FC/queue traffic egressing on the Ethernet port. There is one default access egress policy which is identified as policy ID 1.

  • Page 333

    Access Egress QoS Policies on 7210 SAS-M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE rate cir 0 pir max exit queue 7 adaptation-rule cir closest pir closest rate cir 0 pir max exit queue 8 adaptation-rule cir closest pir closest rate cir 0 pir max exit fc af create...

  • Page 334: Modifying Access Egress Qos Queues

    Overview exit ---------------------------------------------- Modifying Access Egress QoS Queues To modify access egress queue parameters specify the following: • Queue ID value. On 7210 SAS-M and 7210 SAS-T, 8 Queues are identified and are mapped as defined in Forwarding Class to Queue-ID Map for 7210 SAS-M, 7210 SAS-T, and 7210 SAS-Mxp.

  • Page 335: Default Access Egress Qos Policy Values

    Access Egress QoS Policies on 7210 SAS-M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE The following output displays the port configuration . *A:card-1>config>port# info ---------------------------------------------- shutdown ethernet access egress qos 30 exit exit exit ---------------------------------------------- *A:card-1>config>port# Default Access Egress QoS Policy Values The following displays default policy parameters: *A:card-1>config>qos>access-egress# info detail ----------------------------------------------...

  • Page 336

    Overview exit ---------------------------------------------- *A:card-1>config>qos>access-egress# Table 50 lists the default forwarding class marking values when remarking is enabled on the access egress policy for 7210 SAS devices configured in network mode and access-uplink mode: Table 50: Default FC Marking Values for 7210 SAS-M and 7210 SAS-T (Access-uplink mode) and 7210 SAS-M (Network mode) Default FC value Network mode...

  • Page 337: Deleting Qos Policies

    Access Egress QoS Policies on 7210 SAS-M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE Table 50: Default FC Marking Values (Continued)for 7210 SAS-M and 7210 SAS-T (Access-uplink mode) and 7210 SAS-M (Network mode) (Continued) Default FC value Network mode Access uplink mode dot1p-in-profile 1 dot1p-in-profile 1...

  • Page 338

    Overview 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 339: Access Egress Qos Policy Command Reference

    Access Egress QoS Policies on 7210 SAS-M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE Access Egress QoS Policy Command Reference Command Hierarchies • Configuration Commands for 7210 SAS-M (Access-uplink mode) • Configuration Commands for 7210 SAS-M network mode •...

  • Page 340: Configuration Commands For 7210 Sas-m Network Mode

    Access Egress QoS Policy Command Reference Configuration Commands for 7210 SAS-M network mode config — qos — access-egress policy-id [create] — no access-egress policy-id — description description-string — no description — fc-name [create] — no fc-name — [no] de-mark [force de-value] —...

  • Page 341: Mode

    Access Egress QoS Policies on 7210 SAS-M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE — dscp-out-profile dscp-name — no dscp-out-profile — queue queue-id — adaptation-rule [cir adaptation-rule] [pir adaptation-rule] — no adaptation-rule — rate cir cir-rate [pir pir-rate] —...

  • Page 342: Configuration Commands

    Access Egress QoS Policy Command Reference Configuration Commands Generic Commands description Syntax description description-string no description Context config>qos>access-egress Description Platforms Supported: 7210 SAS-M, 7210 SAS-T (access-uplink and network modes), 7210 SAS-Sx/ S 1/10GE, and 7210 SAS-Sx 10/100GE. This command creates a text description stored in the configuration file for a configuration context. The description command associates a text string with a configuration context to help identify the context in the configuration file.

  • Page 343

    Access Egress QoS Policies on 7210 SAS-M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE This command is used to create or edit a access egress QoS policy. The egress policy defines the queue parameters (CIR/PIR) for each of the forwarding class traffic as they egress on the access port. Policies in effect are templates that can be applied to multiple access ports as long as the scope of the policy is template.

  • Page 344

    Access Egress QoS Policy Command Reference If no de-value is present, the default values are used for the marking of the DEI bit: for example, 0 for in-profile packets, 1 for out-of-profile ones – see IEEE 802.1ad-2005 standard. If the de-value is specifically mentioned in the command line it means this value is to be used for all the packets of this forwarding class regardless of their in/out of profile status.

  • Page 345

    Access Egress QoS Policies on 7210 SAS-M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE dot1p-in-profile Syntax dot1p-in-profile dot1p-priority no dot1p-in-profile Context config> qos> access-egress> fc Description Platforms Supported: 7210 SAS-M (access-uplink mode and network mode), and 7210 SAS-T (access-uplink mode).

  • Page 346

    Access Egress QoS Policy Command Reference dot1p-out-profile Syntax dot1p-out-profile dot1p-priority no dot1p-out-profile Context config> qos> access-egress> fc Description Platforms Supported: 7210 SAS-M (access-uplink mode and network mode), and 7210 SAS-T (access-uplink mode). The command will add the capability to mark on an egress the in and out of profile status via a certain dot1p combination, similarly with the DEI options.

  • Page 347

    Access Egress QoS Policies on 7210 SAS-M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE dscp-out-profile Syntax dscp-out-profile dscp-name no dscp-out-profile Context config>qos>access-egress>fc Description Platforms Supported: 7210 SAS-M and 7210 SAS-T (Network and Access-uplink mode). This command specifies the out-of-profile DSCP name for the forwarding class. When marking is set, the corresponding DSCP value is used to mark all IP packets with out-of-profile status, on the egress of this forwarding class queue.

  • Page 348

    Access Egress QoS Policy Command Reference Parameters dscp-name — Specifies the DSCP name. Values be|cp1|cp2|cp3|cp4|cp5|cp6|cp7|cs1|cp9|af11|cp11| af12|cp13|af13|cp15|cs2|cp17|af21|cp19|af22|cp21| af23|cp23|cs3|cp25|af31|cp27|af32|cp29|af33|cp31|cs4| cp33|af41|cp35|af42|cp37|af43|cp39|cs5|cp41|cp42| cp43|cp44|cp45|ef|cp47|nc1|cp49|cp50|cp51|cp52|cp53| cp54|cp55|nc2|cp57|cp58|cp59|cp60|cp61|cp62|cp63 queue Syntax queue queue-id Context config>qos>access-egress Description Platforms Supported: 7210 SAS-M, 7210 SAS-T (access-uplink and network modes), 7210 SAS-Sx/ S 1/10GE and 7210 SAS-Sx 10/100GE. This command creates the context to modify Queue parameters associated with a particular queue.

  • Page 349

    Access Egress QoS Policies on 7210 SAS-M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE → If 'use-dot1p' is configured in the access-egress policy, then the dot1p bits are marked in the packet header for all traffic sent out of all SAPs configured on that access port. →...

  • Page 350

    Access Egress QoS Policy Command Reference → If 'all' is configured is configured in the access-egress policy, then the Dot1p bits are marked in the packet header for all traffic (L2 and IPv4) sent out of both L2 and L3 SAPs and the IP DSCP bits are marked in the packet header for all IPv4 traffic sent out of both L2 and L3 SAPs configured on that access port.

  • Page 351: Access Egress Queue Qos Policy Commands

    Access Egress QoS Policies on 7210 SAS-M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE remarking Syntax no remarking remarking Context config>qos>access-egress Description Platforms Supported: 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE network mode. This command enables the system to remark egress packets sent out of access ports. When remarking is enabled, the remark policy configured in the QoS policy context is used to determine the FC to QoS bit mapping.

  • Page 352

    Access Egress QoS Policy Command Reference Parameters adaptation-rule — Specifies the adaptation rule to be used while computing the operational CIR or PIR value. Values pir — Defines the constraints enforced when adapting the PIR rate defined within the queue queue-id rate command. The pir parameter requires a qualifier that defines the constraint used when deriving the operational PIR for the queue.

  • Page 353

    Access Egress QoS Policies on 7210 SAS-M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE If the CBS value is larger than the MBS value, an error will occur, preventing the CBS change. The no form of this command returns the CBS size to the default value. Default default Parameters...

  • Page 354

    Access Egress QoS Policy Command Reference The actual PIR rate is dependent on the queue’s adaptation-rule parameters and the actual hardware where the queue is provisioned. Values For devices with only 1G ports: 0 — 1000000, max For devices with both 1G and 10G ports : 0 — 10000000, max Default scope Syntax...

  • Page 355

    Access Egress QoS Policies on 7210 SAS-M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE Parameters sap-ingress src-pol dst-pol — Indicates that the source policy ID and the destination policy ID are SAP ingress policy IDs. Specify the source policy ID that the copy command will attempt to copy from and specify the destination policy ID to which the command will copy a duplicate of the policy.

  • Page 356

    Access Egress QoS Policy Command Reference Label Description (Continued) Specifies the administrative Committed Information Rate (CIR) parameters for the queue. The CIR defines the rate at which the system prioritizes the queue over other queues competing for the same bandwidth. min —...

  • Page 357

    Access Egress QoS Policies on 7210 SAS-M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE A:Dut-A>show>qos# access-egress =============================================================================== Access Egress Policies =============================================================================== Policy-Id Scope Description ------------------------------------------------------------------------------- Template Default Access egress QoS policy. =============================================================================== A:Dut-A>show>qos# A:Dut-A>show>qos# access-egress 1 detail =============================================================================== QoS Access Egress =============================================================================== -------------------------------------------------------------------------------...

  • Page 358

    Access Egress QoS Policy Command Reference Queue7 Down Queue8 Down ------------------------------------------------------------------------------- Low Slope ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- QueueId State Start-Avg(%) Max-Avg(%) Max-Prob(%) ------------------------------------------------------------------------------- Queue1 Down Queue2 Down Queue3 Down Queue4 Down Queue5 Down Queue6 Down Queue7 Down Queue8 Down ------------------------------------------------------------------------------- Burst Sizes and Time Average Factor ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- QueueId...

  • Page 359

    Access Egress QoS Policies for 7210 SAS-Mxp In This Section This section provides information to configure Access Egress QoS policies using the command line interface. Topics in this section include: • Overview • Basic Configurations Overview On 7210 SAS-Mxp, the users have an option to use either port-based egress queuing and shaping or SAP-based egress queuing and shaping for SAPs configured on access ports or hybrid ports.

  • Page 360: Access Egress Qos Policy For Sap-based Queuing Mode On 7210 Sas-mxp

    Overview Access Egress QoS policy for SAP-based queuing mode on 7210 SAS-Mxp 7210 SAS-Mxp supports SAP-based marking for access SAPs and port-based egress marking on access ports. SAP-based marking is only supported for L2 SAPs, that is, SAPs configured in Epipe and VPLS service. If user enables remarking in the SAP egress policy attached to the SAP, then the remark policy configured is used to mark the packets sent out of the SAP.

  • Page 361

    Access Egress QoS Policies for 7210 SAS-Mxp Note: • On 7210 SAS-Mxp, if remarking is enabled in SAP egress policy and also port based marking is disabled, then for L2 SAPs, the dot1p values configured in the SAP egress policy is used. For L3 SAPs no marking is done. •...

  • Page 362

    Overview • If remark policy type is dscp, then all traffic sent out of L2 SAPs and L3 SAPs configured on that port will have its IP DSCP bits marked (assuming L2 SAPs are carrying IP traffic). • If remark policy type is of type dot1p-dscp, then all traffic sent out of L2 SAPs and L3 SAPs configured on that port will have its IP DSCP bits (assuming L2 SAPs are carrying IP traffic) and Dot1p bits marked.

  • Page 363

    Access Egress QoS Policies for 7210 SAS-Mxp queue-mode weighted weight 1 exit A:sasr_dutb>config>qos>access-egress# Basic Configurations A basic access egress QoS policy must conform to the following: • Have a unique access egress QoS policy ID. • Have a QoS policy scope of template or exclusive. Editing QoS Policies Existing policies and entries can be edited through the CLI or NMS.

  • Page 364: Removing A Policy From The Qos Configuration

    Overview Removing a Policy from the QoS Configuration CLI Syntax: config>qos# no access-egress policy-id Example: config>qos# no access-egress 100 config>qos# no access-egress 1010 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 365

    Access Egress QoS Policies for 7210 SAS-Mxp Access Egress QoS Policy Command Reference Command Hierarchies • Configuration Commands for 7210 SAS-Mxp • Show Commands Configuration Commands for 7210 SAS-Mxp config — qos — access-egress policy-id [create] — no access-egress policy-id —...

  • Page 366

    Access Egress QoS Policy Command Reference Command Descriptions Generic Commands description Syntax description description-string no description Context config>qos>access-egress Description Platforms Supported: 7210 SAS-Mxp. This command creates a text description stored in the configuration file for a configuration context. The description command associates a text string with a configuration context to help identify the context in the configuration file.

  • Page 367

    Access Egress QoS Policies for 7210 SAS-Mxp Any changes made to an existing policy are applied to all access ports on which the policy is specified. The no form of the policy associated the default policy with the access port. Parameters policy-id —...

  • Page 368

    Access Egress QoS Policy Command Reference 7210 SAS-Mxp supports SAP-based marking for access SAPs and port-based egress marking on access ports. SAP-based marking is only supported for L2 SAPs, that is, SAPs configured in Epipe and VPLS service. If user enables remarking in the SAP egress policy attached to the SAP, then the remark policy configured is used to mark the packets sent out of the SAP.

  • Page 369

    Access Egress QoS Policies for 7210 SAS-Mxp Note: Also see the command remark policy and the sections "Access Egress QoS Policies on 7210 SAS-Mxp. The no form of the command disables remarking. Default no remarking - Remarking is disabled by default. Access Egress Queue QoS Policy Commands adaptation-rule Syntax...

  • Page 370

    Access Egress QoS Policy Command Reference min — The min (minimum) option is mutually exclusive with the max and closest options. When min is defined, the operational PIR for the queue will be equal to or greater than the administrative rate specified using the rate command. closest —...

  • Page 371

    Access Egress QoS Policies for 7210 SAS-Mxp cir cir-percent — The cir keyword is optional and when defined the required cir-percent CIR parameter expresses the queue’s CIR as a percentage dependent on the use of the port-limit. Values Percentage ranging from [0-100]. The default is 100.00. rate Syntax rate cir cir-rate [pir pir-rate]...

  • Page 372

    Access Egress QoS Policy Command Reference queue-mgmt Syntax [no] queue-mgmt name Context config>qos>access-egress>queue Description Platforms Supported: 7210 SAS-Mxp. This command associates the specified queue management policy with this queue. The queue management policy is used to specify the queue buffer parameters and queue slope policy parameters.

  • Page 373

    Access Egress QoS Policies for 7210 SAS-Mxp Allows users to specify the weight of the queue when the queue-mode is set to weighted. For queues configured in weighted mode, the CIR of the queues are met if bandwidth is available and the configured weights are considered in the PIR loop.

  • Page 374

    Access Egress QoS Policy Command Reference Parameters policy-id — Displays the policy id of the access-egress policy. association — Displays associations related to the specified access-egress policy. detail — Displays detailed policy information including the policy associations. Access-Egress Output Output The following table describes Access-egress show command output.

  • Page 375

    Access Egress QoS Policies for 7210 SAS-Mxp Label Description (Continued) min — The operational PIR for the queue will be equal to or greater than PIR Adpt Rule the administrative rate specified using the rate command. max — The operational PIR for the queue will be equal to or less than the administrative rate specified using the rate command.

  • Page 376

    Access Egress QoS Policy Command Reference Description : Default Access egress QoS policy. ------------------------------------------------------------------------------- Queue Rates and Rules ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- QueueId CIR Adpt Rule PIR Adpt Rule ------------------------------------------------------------------------------- Queue1 closest closest Queue2 closest closest Queue3 closest closest Queue4 closest closest Queue5 closest closest...

  • Page 377

    Access Egress QoS Policies for 7210 SAS-Mxp ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- QueueId Time Average Factor Queue-Mgmt ------------------------------------------------------------------------------- Queue1 default Queue2 default Queue3 default Queue4 default Queue5 default Queue6 default Queue7 default Queue8 default ------------------------------------------------------------------------------- Associations ------------------------------------------------------------------------------- Port-id : 1/1/21 Port-id : 1/1/23 Port-id : 1/1/25 Port-id : 1/1/26 ===============================================================================...

  • Page 378

    Access Egress QoS Policy Command Reference 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 379

    Service Egress Policies for 7210 SAS- In This Section This section provides information to configure Service egress QoS policies using the command line interface. Note: Service egress policies are supported only on 7210 SAS-Mxp. It is not supported on 7210 SAS-M, 7210 SAS-T, and 7210 SAS-Sx/S 1/10GE devices. Topics in this section include: •...

  • Page 380: Create A Sap Egress Policy

    Overview • Disable port-scheduler mode using the command config>system>res-prof>qos> no port-scheduler-mode. • Ensure resources are available for use by SAP egress queues in the ingress-internal- tcam resources pool using the command config>system> resource-profile>ingress- internal-tcam> qos-sap-egress-resource. A basic service egress QoS policy must conform to the following: •...

  • Page 381

    Service Egress Policies for 7210 SAS-Mxp ---------------------------------------------- description "Default SAP egress QoS policy." scope template no remarking remark 2 queue 1 adaptation-rule pir closest cir closest rate cir 0 pir max queue-mgmt "default" queue-mode weighted weight 1 exit queue 2 adaptation-rule pir closest cir closest rate cir 0 pir max queue-mgmt "default"...

  • Page 382

    Overview 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 383: Service Egress Policy Command Reference

    Service Egress Policies for 7210 SAS-Mxp Service Egress Policy Command Reference Command Hierarchies • Configuration Commands for 7210 SAS-Mxp • Copy Commands • Show Commands Configuration Commands for 7210 SAS-Mxp config — qos — sap-egress policy-id [create] — no sap-egress policy-id —...

  • Page 384

    Service Egress Policy Command Reference Command Descriptions Configuration Commands Generic Commands description Syntax description description-string no description Context config>qos>sap-egress Description Platforms Supported: 7210 SAS-Mxp. This command creates a text description stored in the configuration file for a configuration context. The description command associates a text string with a configuration context to help identify the context in the configuration file.

  • Page 385

    Service Egress Policies for 7210 SAS-Mxp This command defines the method used by the system to derive the operational CIR and PIR settings when the queue is provisioned in hardware. For the CIR and PIR parameters individually, the system attempts to find the best operational rate depending on the defined constraint. The no form of the command removes any explicitly defined constraints used to derive the operational CIR and PIR created by the application of the policy.

  • Page 386

    Service Egress Policy Command Reference Parameters queue-id — Specifies the id of the queue. Values 1 — 8 create — Mandatory keyword to create a network queue policy. sap-egress Syntax sap-egress policy-id [create] Context config>qos Description Platforms Supported: 7210 SAS-Mxp. This command enables the context to configure a SAP Egress policy.

  • Page 387

    Service Egress Policies for 7210 SAS-Mxp The no form of the command removes the explicit association of the remark policy and associates the default remark policy. In other words, if remarking is enabled and no remark policy is executed, then the default remark policy is used to mark packets sent out.

  • Page 388

    Service Egress Policy Command Reference Parameters exclusive — When the scope of a policy is defined as exclusive, the policy can only be applied to one interface/port. If a policy with an exclusive scope is assigned to a second interface an error message is generated.

  • Page 389

    Service Egress Policies for 7210 SAS-Mxp min — The min (minimum) option is mutually exclusive with the max and closest options. The hardware step size varies with the configured rate. closest — The closest parameter is mutually exclusive with the min and max parameter.

  • Page 390

    Service Egress Policy Command Reference rate Syntax rate cir cir-rate-in-kbps [pir pir-rate-in-kbps] no rate Context config>qos>sap-egress>queue Description Platforms Supported: 7210 SAS-Mxp. This command defines the administrative Peak Information Rate (PIR) and the administrative Committed Information Rate (CIR) parameters for the queue. The PIR defines the maximum rate that the queue can transmit packets through the port.

  • Page 391

    Service Egress Policies for 7210 SAS-Mxp For queues configured in weighted mode, the CIR of the queues are met if bandwidth is available and the configured weights are considered in the PIR loop. The configured weight determines the proportion of available bandwidth that is given to this queue in comparison to other queues configured in weighted mode.

  • Page 392

    Service Egress Policy Command Reference Operational Commands copy Syntax copy sap-egress <src-pol> <dst-pol> [overwrite] Context config>qos Description This command copies the existing SAP egress QoS policy entries to another SAP egress QoS policy. The copy command is a configuration level maintenance tool used to create new policies using existing policies.

  • Page 393

    Service Egress Policies for 7210 SAS-Mxp Label Description (Continued) True — Remarking is enabled for all the Remark Dot1q-tagged packets that egress the ports on which the sap-egress QoS policy is applied and remarking is enabled. False — Remarking is disabled for the policy. Displays the policy id of the remarking policy.

  • Page 394

    Service Egress Policy Command Reference 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 395

    QoS Port Scheduler Policies for 7210 SAS-M and 7210 SAS-T In This Section This section provides information to configure port scheduler policies using the command line interface. Note: This chapter is not applicable to 7210 SAS-Mxp. Topics in this section include: •...

  • Page 396

    Service Management Tasks Basic Configurations A basic QoS port scheduler policy must conform to the following: • Each QoS port scheduler policy must have a unique policy name. Creating a QoS Port Scheduler Policy To create a port scheduler policy, define the following: •...

  • Page 397: Copying And Overwriting Scheduler Policies

    QoS Port Scheduler Policies for 7210 SAS-M and 7210 SAS-T Copying and Overwriting Scheduler Policies You can copy an existing QoS policy, rename it with a new QoS policy value, or overwrite an existing policy. The overwrite option must be specified or an error occurs if the destination policy exists.

  • Page 398

    Service Management Tasks =============================================================================== *A:Dut-1>config# *A:Dut-1>config# show qos port-scheduler-policy psp1 =============================================================================== QoS Port Scheduler Policy =============================================================================== Policy-Name : psp1 Accounting : packet-based Mode : WDRR Last changed : 04/12/2001 02:05:00 Queue 1 Weight: Queue 2 Weight: Queue 3 Weight: Queue 4 Weight: Queue 5 Weight: Queue 6 Weight: Queue 7 Weight:...

  • Page 399: Schedulers On 7210 Sas-sx/s 1/10ge And 7210 Sas-sx 10/100ge

    Schedulers on 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE In this section This section describes the port scheduler and its behavior for 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE. The port scheduler on 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE is configured using the port scheduler policies. On 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE, there are 2 level of egress schedulers –...

  • Page 400

    In this section After completing the CIR loop and satisfying the CIR rates configured for all the FCs, the scheduler starts the PIR loop (only if more port bandwidth remains). In the PIR loop too, bandwidth is first allocated to higher priority FC followed by lower priority FCs. It is recommended to configure the rates correctly for higher priority FC when using strict priority mode to avoid starvation of lower priority FC.

  • Page 401: Qos Port Scheduler Policy Command Reference

    Schedulers on 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE QoS Port Scheduler Policy Command Reference Command Hierarchies • Port Scheduler Policy Configuration Commands • Operational Commands • Show Commands Port Scheduler Policy Configuration Commands config — qos — [no] port-scheduler-policy port-scheduler-name [create] —...

  • Page 402

    QoS Port Scheduler Policy Command Reference Command Descriptions Configuration Commands Generic Commands description Syntax description description-string no description Context config>qos>port-scheduler-policy Description Platforms Supported: 7210 SAS-M and 7210 SAS-T (Access-uplink mode and Network), 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE. This command creates a text description stored in the configuration file for a configuration context. The description command associates a text string with a configuration context to help identify the context in the configuration file.

  • Page 403: Port Scheduler Policy Commands

    Schedulers on 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE This command copies existing port scheduler QoS policy entries for a port scheduler QoS policy to another port scheduler QoS policy. The copy command is a configuration level maintenance tool used to create new policies using existing policies.

  • Page 404

    QoS Port Scheduler Policy Command Reference Description Platforms Supported: 7210 SAS-M and 7210 SAS-T (Access-uplink mode and Network), 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE. This command configures a particular mode of scheduling for the policy. For example, this implies that when a policy with a mode RR is applied to a port then that port will follow the round robin type of scheduling between its queues.

  • Page 405

    Schedulers on 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE Show Commands port-scheduler-policy Syntax port-scheduler-policy [port-scheduler-policy-name] [association] Context show>qos Description Platforms Supported: 7210 SAS-M and 7210 SAS-T (Access-uplink mode and Network), 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE. This command displays port-scheduler policy information Parameters port-scheduler-policy-name —...

  • Page 406

    QoS Port Scheduler Policy Command Reference Accounting : packet-based Mode : WDRR ------------------------------------------------------------------------------- Associations ------------------------------------------------------------------------------- - Port : 1/1/1 =============================================================================== *A:Dut-1>config# *A:Dut-1>config# show qos port-scheduler-policy psp =============================================================================== QoS Port Scheduler Policy =============================================================================== Policy-Name : psp Accounting : packet-based Mode : WDRR Last changed : 04/12/2001 02:04:16 Queue 1 Weight:...

  • Page 407

    Schedulers on 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE - Port : 1/1/18 - Port : 1/1/19 - Port : 1/1/21 - Port : 1/1/22 - Port : 1/1/23 - Port : 1/1/24 =============================================================================== *A:card-1# *A:Dut-1>config# show qos port-scheduler-policy default =============================================================================== QoS Port Scheduler Policy ===============================================================================...

  • Page 408

    QoS Port Scheduler Policy Command Reference *A:K-SAS-Sx>config>qos# show qos port-scheduler-policy "default" =============================================================================== QoS Port Scheduler Policy =============================================================================== Policy-Name : default Description : Default Port Scheduler policy. Accounting : packet-based Mode : STRICT Last changed : 01/03/2000 07:34:35 Number Of Queues =============================================================================== 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 409

    Schedulers on 7210 SAS-Mxp In This Section This section provides information about the scheduler support available in the 7210 SAS- Mxp devices for network port and SAP. Topics in this section include: • Overview • Scheduling with SAP based queues on Access ports •...

  • Page 410: Scheduling With Sap Based Queues On Access Ports

    Scheduling with SAP based queues on Access ports Scheduling with SAP based queues on Access ports When SAP-based scheduling is enabled, the Figure 5 shows the scheduling for access port, with multiple SAPs configured and when the port-scheduler-mode is disabled. There are 8 egress queues per SAP, a per SAP scheduler and a per access port scheduler.

  • Page 411

    Schedulers on 7210 SAS-Mxp • Per port scheduler is available and works at line-rate or configured port egress rate • Port scheduler distributes the bandwidth available to all the SAPs using WDRR scheduling mechanism (that is, all SAPs have equal weights assigned by the system). •...

  • Page 412: Scheduling On Network Ports

    Scheduling on Network Ports Scheduling on Network Ports For a network port, the scheduling behavior is similar, except that per SAP scheduler is not present in the hierarchy. Instead, per port scheduler distributes the available port bandwidth to all the queues configured on the port in two passes with the behavior being similar to the per SAP scheduler (as mentioned above).

  • Page 413: Port Based Scheduling And Queuing On Access Ports

    Schedulers on 7210 SAS-Mxp Figure 7: Hybrid Port Egress Scheduling The scheduling behavior is very similar to the SAP based queues on the access ports. In other words, the network port queues used for network traffic is treated like another SAP node in the scheduling hierarchy.

  • Page 414: Figure 8 Port Based Scheduling And Queuing

    Scheduling on Hybrid port with SAP based egress queues Figure 8: Port Based Scheduling and Queuing The behavior of the Port-based Queuing and Scheduling on Access Ports is given below: • If enabled, all SAPs on the node/chassis use port-based queuing. •...

  • Page 415: Scheduling On Hybrid Port With Port Based Sap Queues

    Schedulers on 7210 SAS-Mxp → Higher priority strict queue (s) get the bandwidth up to the configured CIR. → Any remaining bandwidth, if available, is distributed among the lower priority strict queue (s) up to the configured CIR. → Any remaining bandwidth, if available, is distributed among the weighted queues (in the CIR loop, weights are not used and hence the bandwidth is distributed in equal proportion irrespective of weights configured).

  • Page 416

    Scheduling on hybrid port with port based SAP queues 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 417: Slope Qos Policies

    Slope QoS Policies In This Section This section provides information to configure slope QoS policies using the command line interface. Topics in this section include: • Overview • Basic Configurations • Default Slope Policy Values • Service Management Tasks Overview Default buffer pool exists (logically) at each port.

  • Page 418: For 7210 Sas-m Access-uplink Mode

    Overview • For traffic received with MPLS encapsulation (For example: MPLS traffic received on network port ingress, and others) non-TCP slope is used. • For TCP traffic received with less than or equal to 2 VLAN tags (For example: VLAN ethernet traffic received on SAP ingress, and others) TCP- slopes (either high or low) is used.

  • Page 419: Wred Support On 7210 Sas-t Access-uplink Mode

    Slope QoS Policies Table 51: Slope behavior table Slopes TCP-non-TCP slope option High-Low slope option (Uses 3 WRED slopes per (Uses 2 WRED slopes per queue) queue) SAP Ingress TCP/IP traffic High-priority TCP slope or High-priority or low-priority low-priority TCP slope, based slope, based on packet profile (Number of VLAN tags <=2) on packet profile...

  • Page 420

    Overview A WRED profile (that is, each high-slope and low-slope) allows to specify the slope parameters such as max-average, start-average, drop probability and time average factor (TAF). Basic Configurations A basic slope QoS policy must conform to the following: • Each slope policy must have a unique policy ID.

  • Page 421

    Slope QoS Policies max-avg percent max-prob percent no shutdown non-tcp-slope start-avg percent max-avg percent max-prob percent no shutdown time-average-factor taf The following displays the slope policy configuration for 7210 SAS-M: A:ALA-7>config>qo>slope-policy# info ---------------------------------------------- description "slope policy SlopePolicy1" high-slope no shutdown exit low-slope no shutdown...

  • Page 422: Applying Slope Policies

    Overview queue "1" high-slope shutdown start-avg 70 max-avg 90 max-prob 75 exit low-slope shutdown start-avg 50 max-avg 75 max-prob 75 exit time-average-factor 7 exit Applying Slope Policies Apply slope policies to the egress buffer pool on the access and network ports. Ports The following CLI syntax examples may be used to apply slope policies to ports: CLI Syntax:...

  • Page 423

    Slope QoS Policies shutdown start-avg 50 max-avg 75 max-prob 75 exit non-tcp-slope shutdown start-avg 50 max-avg 75 max-prob 75 exit time-average-factor 7 exit queue "2" high-slope shutdown start-avg 70 max-avg 90 max-prob 75 exit low-slope shutdown start-avg 50 max-avg 75 max-prob 75 exit non-tcp-slope...

  • Page 424

    Overview max-avg 90 max-prob 75 exit low-slope shutdown start-avg 50 max-avg 75 max-prob 75 exit non-tcp-slope shutdown start-avg 50 max-avg 75 max-prob 75 exit time-average-factor 7 exit queue "5" high-slope shutdown start-avg 70 max-avg 90 max-prob 75 exit low-slope shutdown start-avg 50 max-avg 75 max-prob 75...

  • Page 425

    Slope QoS Policies queue "7" high-slope shutdown start-avg 70 max-avg 90 max-prob 75 exit low-slope shutdown start-avg 50 max-avg 75 max-prob 75 exit non-tcp-slope shutdown start-avg 50 max-avg 75 max-prob 75 exit time-average-factor 7 exit queue "8" high-slope shutdown start-avg 70 max-avg 90 max-prob 75 exit...

  • Page 426

    Overview Service Management Tasks Deleting QoS Policies A slope policy is associated by default with access and network egress pools. A default policy may be replaced with a non-default policy, but a policy cannot be entirely removed from the configuration. When a non-default policy is removed, the policy association reverts to the default slope policy policy-id default.

  • Page 427

    Slope QoS Policies The following output displays the copied policies for: A:ALA-7210M>config>qos# ---------------------------------------------- description "Default slope policy." queue "1" high-slope shutdown start-avg 70 max-avg 90 max-prob 75 exit low-slope shutdown start-avg 50 max-avg 75 max-prob 75 exit non-tcp-slope shutdown start-avg 50 max-avg 75 max-prob 75 exit...

  • Page 428

    Overview low-slope shutdown start-avg 50 max-avg 75 max-prob 75 exit non-tcp-slope shutdown start-avg 50 max-avg 75 max-prob 75 exit time-average-factor 7 exit queue "4" high-slope shutdown start-avg 70 max-avg 90 max-prob 75 exit low-slope shutdown start-avg 50 max-avg 75 max-prob 75 exit non-tcp-slope shutdown...

  • Page 429

    Slope QoS Policies Editing QoS Policies You can change existing policies and entries in the CLI or NMS. The changes are applied immediately to all services where this policy is applied. To prevent configuration errors copy the policy to a work area, make the edits, and then write over the original policy. 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 430

    Overview 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 431: Slope Qos Policy Command Reference

    Slope QoS Policies Slope QoS Policy Command Reference Command Hierarchies • Configuration Commands • WRED Commands • Operational Commands • Show Commands Configuration Commands config — qos — [no] slope-policy name — description description-string — no description — queue queue-id —...

  • Page 432: Wred Commands

    Slope QoS Policy Command Reference WRED Commands config — system — qos — no use-wred-slopes — use-wred-slopes slope-type Operational Commands config — qos — copy slope-policy src-name dst-name [overwrite] Show Commands show — qos — slope-policy [slope-policy-name] [detail] 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 433

    Slope QoS Policies Command Descriptions Configuration Commands Generic Commands description Syntax description description-string no description Context config>qos>slope-policy Description Platforms Supported: 7210 SAS-M and 7210 SAS-T (Access-uplink mode and Network), 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE. This command creates a text description stored in the configuration file for a configuration context. The description command associates a text string with a configuration context to help identify the context in the configuration file.

  • Page 434

    Slope QoS Policy Command Reference The copy command is a configuration level maintenance tool used to create new policies using existing policies. It also allows bulk modifications to an existing policy with the use of the overwrite keyword. Parameters slope-policy — Indicates that the source policy ID and the destination policy ID are slope policy IDs.

  • Page 435

    Slope QoS Policies Description Platforms Supported: 7210 SAS-M and 7210 SAS-T (Access-uplink mode and Network), 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE. This command sets the context to configure the high-priority, low-priority, and non-tcp slope parameters per queue. Parameters queue-id — Specifies the ID of the queue for which the drop-rate is to be configured. Values 1 —...

  • Page 436

    Slope QoS Policy Command Reference The no form of this command restores the low slope configuration commands to the default values. If the leaf commands within low-slope are set to the default parameters, the low-slope node will not appear in save config and show config output unless the detail parameter is present. non-tcp-slope Syntax [no] non-tcp-slope...

  • Page 437

    Slope QoS Policies Parameters value — Represents the Time Average Factor (TAF), expressed as a decimal integer. The value specified for TAF affects the speed at which the shared buffer average utilization tracks the instantaneous shared buffer utilization. A low value weights the new shared buffer average utilization calculation more to the shared buffer instantaneous utilization, zero using it exclusively.

  • Page 438

    Slope QoS Policy Command Reference max-prob Syntax max-prob percent no max-prob Context config>qos>slope-policy>queue>high-slope config>qos>slope-policy>queue>low-slope config>qos>slope-policy>queue>non-tcp-slope Description Platforms Supported: 7210 SAS-M and 7210 SAS-T (Access-uplink mode and Network), 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE. Sets the low priority or high priority Random Early Detection (RED) slope position for the maximum non-one packet discard probability value before the packet discard probability rises directly to one.

  • Page 439

    Slope QoS Policies no start-avg Context config>qos>slope-policy>queue>high-slope config>qos>slope-policy>queue>low-slope config>qos>slope-policy>queue>non-tcp-slope Description Platforms Supported: 7210 SAS-M and 7210 SAS-T (Access-uplink mode and Network), 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE. This command sets the low priority or high priority Random Early Detection (RED) slope position for the shared buffer average utilization value where the packet discard probability starts to increase above zero.

  • Page 440

    Slope QoS Policy Command Reference utilization and the current shared buffer instantaneous utilization when calculating the new shared buffer average utilization. The TAF value applies to all high ,low priority and non-tcp packets WRED slopes for egress access and network buffer pools controlled by the slope policy. WRED command use-wred-slopes Syntax...

  • Page 441

    Slope QoS Policies The non-TCP WRED slope is used for all packets classified as non-TCP packets on ingress, irrespective of the packet's profile or priority. Packets classified as TCP and determined to be high-priority/in-profile by the ingress meter, uses the high priority TCP WRED slope. This slope uses the values configured under config>...

  • Page 442

    Slope QoS Policy Command Reference Table 52: Show QoS Slope Policy Output Fields (Continued) Label Description Up — The administrative status of the RED slope is enabled. Admin State Down — The administrative status of the RED slope is disabled. Specifies the low priority or high priority RED slope position for the maximum non-one packet discard probability value before the packet discard probability rises directly to one.

  • Page 443

    Slope QoS Policies Queue2 Down Queue3 Down Queue4 Down Queue5 Down Queue6 Down Queue7 Down Queue8 Down ------------------------------------------------------------------------------- Time Avg Factor ------------------------------------------------------------------------------- Queue Id Time Avg Factor ------------------------------------------------------------------------------- Queue1 Queue2 Queue3 Queue4 Queue5 Queue6 Queue7 Queue8 =============================================================================== *A:SN12345678# show qos slope-policy 100 detail *A:SN12345678# =============================================================================== QoS Slope Policy...

  • Page 444

    Slope QoS Policy Command Reference QueueId State Start-Avg(%) Max-Avg(%) Max-Prob(%) ------------------------------------------------------------------------------- Queue1 Down Queue2 Down Queue3 Down Queue4 Down Queue5 Down Queue6 Down Queue7 Down Queue8 Down ------------------------------------------------------------------------------- Time Avg Factor ------------------------------------------------------------------------------- Queue Id Time Avg Factor ------------------------------------------------------------------------------- Queue1 Queue2 Queue3 Queue4 Queue5...

  • Page 445: Queue Management Policies

    Queue Management Policies In This Section Note: This chapter is applicable only to 7210 SAS-Mxp devices and not for 7210 SAS- M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE devices. This section provides information to configure queue management policies using the command line interface.

  • Page 446

    Overview • Slope for out-of-profile or low priority traffic. Each slope allows specifying the start-average, the max-average, the drop-probability and the Time Average Factor (TAF). Each queue has a default slope policy. Multiple queues in the system can share a single policy. If a policy is shared the system computes the WRED drop probabilities for each of the queues separately based on their average queue length.

  • Page 447

    Queue Management Policies high-slope start-avg percent max-avg percent max-prob percent no shutdown low-slope start-avg percent max-avg percent max-prob percent no shutdown time-average-factor taf The following output displays the queue management policy configuration: A:7210-x>config>qos>queue-mgmt# info ---------------------------------------------- high-slope shutdown start-avg 40 max-avg 50 exit low-slope shutdown...

  • Page 448

    Overview 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 449: Queue Management Policy Command Reference

    Queue Management Policies Queue Management Policy Command Reference Command Hierarchies • Configuration Commands for 7210 SAS-Mxp • Show Commands • Operational Commands Configuration Commands for 7210 SAS-Mxp config — qos — [no] queue-mgmt name — description description-string — no description —...

  • Page 450

    Queue Management Policy Command Reference — qos — copy queue-mgmt<src-name> <dst-name> [overwrite] 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 451

    Queue Management Policies Command Descriptions Configuration Commands Generic Commands description Syntax description description-string no description Context config>qos>queue-mgmt Description Platforms Supported: 7210 SAS-Mxp. This command creates a text description stored in the configuration file for a configuration context. The description command associates a text string with a configuration context to help identify the context in the configuration file.

  • Page 452

    Queue Management Policy Command Reference The copy command is a configuration level maintenance tool used to create new policies using existing policies. It also allows bulk modifications to an existing policy with the use of the overwrite keyword. Parameters src-name — Specifies the name of the source policy. Values 1 —...

  • Page 453

    Queue Management Policies This command is used to configure the out-of-profile WRED slope parameters. Syntax [no] mbs size-in-kbytes Context config>qos>queue-mgmt Description Platforms Supported: 7210 SAS-Mxp. This command specifies the MBS value (Maximum depth of the queue in kilo bytes). Parameters size-in-kbytes —...

  • Page 454

    Queue Management Policy Command Reference Default Parameters value — Represents the Time Average Factor (TAF), expressed as a decimal integer. The value specified for TAF affects the speed at which the shared buffer average utilization tracks the instantaneous shared buffer utilization. A low value weights the new shared buffer average utilization calculation more to the shared buffer instantaneous utilization, zero using it exclusively.

  • Page 455

    Queue Management Policies Description Platforms Supported: 7210 SAS-Mxp. This command is used to configure the maximum average value. Default max-avg 90 — High slope default is 90% buffer utilization. max-avg 75 — Low slope default is 75% buffer utilization. Parameters percent —...

  • Page 456

    Queue Management Policy Command Reference start-avg Syntax start-avg percent no start-avg Context config>qos>queue-mgmt>high-slope config>qos>queue-mgmt>low-slope Description Platforms Supported: 7210 SAS-Mxp. This command is used to configure the starting average value. Default max-avg 70 — High slope default is 70% buffer utilization. max-avg 50 —...

  • Page 457

    Queue Management Policies Table 53: Show Queue Management Policy Output Fields (Continued) Label Description Displays the committed burst size. Displays the maximum burst size. Slope Parameters Specifies the low priority or high priority RED slope position for the Start Avg shared buffer average utilization value where the packet discard probability starts to increase above zero.

  • Page 458

    Queue Management Policy Command Reference ------------------------------------------------------------------------------- Start Avg : 50 Admin State : Disabled Max Avg : 75 Max Prob. : 75 ------------------------------------------------------------------------------- Associations ------------------------------------------------------------------------------- SAP Egress ------------------------------------------------------------------------------- SAP Egress Policy Id : 200 Queue Ids : 1, 2, 3, 4, 5, 6, 7, 8 ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Associations...

  • Page 459

    Queue Management Policies Queue6 Down Queue7 Down Queue8 Down ------------------------------------------------------------------------------- Non Tcp Slope ------------------------------------------------------------------------------- QueueId State Start-Avg(%) Max-Avg(%) Max-Prob(%) ------------------------------------------------------------------------------- Queue1 Down Queue2 Down Queue3 Down Queue4 Down Queue5 Down Queue6 Down Queue7 Down Queue8 Down ------------------------------------------------------------------------------- Time Avg Factor ------------------------------------------------------------------------------- Queue Id Time Avg Factor...

  • Page 460

    Queue Management Policy Command Reference Queue3 Down Queue4 Down Queue5 Down Queue6 Down Queue7 Down Queue8 Down ------------------------------------------------------------------------------- Non Tcp Slope ------------------------------------------------------------------------------- QueueId State Start-Avg(%) Max-Avg(%) Max-Prob(%) ------------------------------------------------------------------------------- Queue1 Down Queue2 Down Queue3 Down Queue4 Down Queue5 Down Queue6 Down Queue7 Down Queue8...

  • Page 461: Remark Policies

    Remark Policies In This Section This section provides information to configure remark policies using the command line interface. This section is applicable to only 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, 7210 SAS- Sx 10/100GE, and 7210 SAS-Mxp devices in network mode. Topics in this section include: •...

  • Page 462

    Overview The type of the remark policy identifies the bits marked in the packet header. Each of these remark policy types can be associated with only appropriate QoS policies and service entities as listed in Table Table 54: Summary of remark policy and attachment points for 7210 SAS- T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE(Network mode) Remark Qos Policy...

  • Page 463

    Remark Policies Table 54: Summary of remark policy and attachment points for 7210 SAS- T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE(Network mode) (Continued) Remark Qos Policy Attachment Point Packet Header Bits Marked Policy Type dot1p-lsp- access-egress policy Access port •...

  • Page 464

    Overview Table 55: Summary of remark policy and attachment points for SAS-Mxp Remark Qos Policy Attachment Point Packet Header Bits Marked Policy Type dot1p access-Egress policy Access port • Dot1p bits in L2 Ethernet header for service packets sent out of all access SAPs configured on access ports.

  • Page 465

    Remark Policies Table 55: Summary of remark policy and attachment points for SAS-Mxp (Continued) Remark Qos Policy Attachment Point Packet Header Bits Marked Policy Type dot1p-lsp- access-egress policy Access port • Dot1p bits in L2 Ethernet exp-shared header for service packets sent out of ac-cess SAPs configured on access ports.

  • Page 466: Configuration Guideline

    Overview Configuration Guideline • Access Port and Access SAP Marking functionality (SAP-Based and Port-Based) - 7210 SAS-Mxp supports SAP-based egress marking and port-based egress marking on only access ports when using access SAP based egress queuing. Users have an option to use either sap-based marking or port-based marking. In SAP-based marking the remark policy defined in the SAP egress policy associated with each SAP is used to mark the packets egressing out of SAP if marking is enabled.

  • Page 467

    Remark Policies fc af dscp-in-profile af11 dscp-out-profile af12 no lsp-exp-in-profile no lsp-exp-out-profile no dot1p-lsp-exp-in-profile no dot1p-lsp-exp-out-profile no de-mark no dot1p dot1p-in-profile 3 dot1p-out-profile 2 exit fc be dscp-in-profile be dscp-out-profile be no lsp-exp-in-profile no lsp-exp-out-profile no dot1p-lsp-exp-in-profile no dot1p-lsp-exp-out-profile no de-mark no dot1p dot1p-in-profile 0 dot1p-out-profile 0...

  • Page 468

    Overview exit fc l1 dscp-in-profile af21 dscp-out-profile af22 no lsp-exp-in-profile no lsp-exp-out-profile no dot1p-lsp-exp-in-profile no dot1p-lsp-exp-out-profile no de-mark no dot1p dot1p-in-profile 3 dot1p-out-profile 2 exit fc l2 dscp-in-profile cs1 dscp-out-profile cs1 no lsp-exp-in-profile no lsp-exp-out-profile no dot1p-lsp-exp-in-profile no dot1p-lsp-exp-out-profile no de-mark no dot1p dot1p-in-profile 1 dot1p-out-profile 1...

  • Page 469: Remark Policy Command Reference

    Remark Policies Remark Policy Command Reference Command Hierarchies • Configuration Commands for 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, and 7210 SAS-Mxp in Network Mode • Show Commands • Operational Commands Configuration Commands for 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, and 7210 SAS-Mxp in Network Mode config —...

  • Page 470

    Remark Policy Command Reference — remark-policy [policy-id] [association|detail] Operational Commands config — qos — copy remark src-pol dst-pol [overwrite] 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 471

    Remark Policies Command Descriptions Configuration Commands Generic Commands description Syntax [no] description description-string Context config>qos>remark Description Platforms Supported: 7210 SAS-T (network mode), 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/ 100GE, and 7210 SAS-Mxp. This command creates a text description stored in the configuration file for a configuration context. The description command associates a text string with a configuration context to help identify the context in the configuration file.

  • Page 472

    Remark Policy Command Reference The copy command is a configuration level maintenance tool used to create new policies using existing policies. It also allows bulk modifications to an existing policy with the use of the overwrite keyword. If the destination policy already exists, the key word overwrite must be specified. Parameters src-pol —...

  • Page 473

    Remark Policies remarking-type — Specifies the type of marking values in the remark policy. Values dot1p — Specify FC to 802.1 Dot1p value to use for marking. It is the default used if user does not explicitly specify the remarking-type value. dscp—...

  • Page 474

    Remark Policy Command Reference Description Platforms Supported: 7210 SAS-T (network mode), 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/ 100GE, and 7210 SAS-Mxp. This command is used to explicitly define the marking of the DEI bit for fc fc-name according to the in and out of profile status of the packet (fc-name may be used to identify the dot1p-value).

  • Page 475

    Remark Policies dot1p-in-profile Syntax dot1p-in-profile dot1p-priority no dot1p-in-profile Context config> qos> remark> fc Description Platforms Supported: 7210 SAS-T (network mode), 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/ 100GE, and 7210 SAS-Mxp. The command will add the capability to mark on an egress the in and out of profile status through a certain dot1p combination, similarly with the DEI options.

  • Page 476

    Remark Policy Command Reference The command will add the capability to mark on an egress the in and out of profile status via a certain dot1p combination, similarly with the DEI options. It may be used when the internal in and out of profile status needs to be communicated to an adjacent network/customer device that does not support the DEI bit.

  • Page 477

    Remark Policies This command has no effect for egress packets sent out of all other non-QinQ SAPs e.g. Dot1q SAP, NULL SAP, etc. Additionally, if the egress packets for fc-name are not IEEE 802.1Q or IEEE 802.1P encapsulated, this command has no effect. In other words, this command takes effect, only when the node adds 2 tags to the packet on the egress.

  • Page 478

    Remark Policy Command Reference Context config> qos> remark> fc Description Platforms Supported: 7210 SAS-T (network mode), 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/ 100GE, and 7210 SAS-Mxp. This command specifies the out-of-profile DSCP name for the forwarding class. When marking is set, the corresponding DSCP value is used to mark all IP packets with out-of-profile status, on the egress of this forwarding class queue.

  • Page 479

    Remark Policies lsp-exp-out-profile Syntax lsp-exp-out-profile lsp-exp-value no lsp-exp-out-profile Context config> qos> remark> fc Description Platforms Supported: 7210 SAS-T (network mode), 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/ 100GE, and 7210 SAS-Mxp. This command specifies the out-of-profile LSP EXP value for the forwarding class. The EXP value will be used for all LSP labeled packets requiring marking the egress on this forwarding class queue that are out-of-profile.

  • Page 480

    Remark Policy Command Reference dscp-out-profile Syntax dscp-out-profile dscp-name no dscp-out-profile Context config>qos>remark>fc Description Platforms Supported: 7210 SAS-T (network mode), 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/ 100GE, and 7210 SAS-Mxp. This command specifies the dscp out-profile value. Parameters dscp-name — This value is used for the IP DSCP bits in the IP header. Values be|cp1|cp2|cp3|cp4|cp5|cp6|cp7|cs1|cp9|af11|cp11| af12|cp13|af13|cp15|cs2|cp17|af21|cp19|af22|cp21|...

  • Page 481

    Remark Policies Description Platforms Supported: 7210 SAS-T (network mode), 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/ 100GE, and 7210 SAS-Mxp. This command specifies the in-profile LSP EXP value for the forwarding class. This value is used for all out-of-profile LSP labeled packets which require marking the egress on the forwarding class queue. When multiple LSP EXP values are associated with the forwarding class at network egress, the last name entered overwrites the previous value.

  • Page 482

    Remark Policy Command Reference This command specifies the out-profile Dot1p LSP EXP value for the forwarding class. This value is used for all out-of-profile LSP labeled packets which require marking the egress on the forwarding class queue. When multiple Dot1p LSP EXP values are associated with the forwarding class at network egress, the last name entered overwrites the previous value.

  • Page 483

    Remark Policies Table 56: Show Remark Policy Output Fields (Continued) Label Description dot1p/LSP EXP value for out-of-profile packets. dot1P/LSP EXP Out value DSCP value used for in-profile packets DCSP In value DSCP value used for out-of-profile packets DCSP Out value Service Associations Displays the policy ID of the SAP Egress policy.

  • Page 484

    Remark Policy Command Reference dot1p dot1p dot1p dot1p dot1p ============================================================================== •indicates that the corresponding row element may have been truncated. *A:SAS-C>config>qos# show qos remark-policy 500 association =============================================================================== QoS Remarking Policies =============================================================================== ------------------------------------------------------------------------------- Remark Policy-id : 500 Type : dot1p-lsp-exp-shared Description : (Not Specified) ------------------------------------------------------------------------------- Associations...

  • Page 485

    Remark Policies Service-Id : 1070 (VPLS) Customer-Id - SAP : lag-2:1070 SAP Egress Policy Id : 11401 ------------------------------------------------------------------------------- Associations ------------------------------------------------------------------------------- Service-Id : 1140 (VPLS) Customer-Id - SAP : lag-2:1140 SAP Egress Policy Id : 15001 ------------------------------------------------------------------------------- Associations ------------------------------------------------------------------------------- Service-Id : 1500 (VPLS) Customer-Id - SAP : lag-4:1500 SAP Egress Policy Id...

  • Page 486

    Remark Policy Command Reference ------------------------------------------------------------------------------- Interface : ip-192.162.100.4 IP Addr. : 192.162.100.4/24 Port Id : 1/1/23 Interface : ip-192.162.40.4 IP Addr. : 192.162.40.4/24 Port Id : lag-5 Interface : ip-192.162.65.4 IP Addr. : 192.162.65.4/24 Port Id : 1/1/13 Network Policy Id : 1050 ------------------------------------------------------------------------------- Interface Association...

  • Page 487

    Remark Policies ------------------------------------------------------------------------------- Associations ------------------------------------------------------------------------------- Service-Id : 500 (VPLS) Customer-Id - SAP : lag-2:500 SAP Egress Policy Id : 5701 ------------------------------------------------------------------------------- Associations ------------------------------------------------------------------------------- Service-Id : 570 (VPLS) Customer-Id - SAP : lag-2:570 SAP Egress Policy Id : 6401 ------------------------------------------------------------------------------- Associations ------------------------------------------------------------------------------- Service-Id : 640 (VPLS)

  • Page 488

    Remark Policy Command Reference ------------------------------------------------------------------------------- Service-Id : 1570 (VPLS) Customer-Id - SAP : lag-4:1570 SAP Egress Policy Id : 16401 ------------------------------------------------------------------------------- Associations ------------------------------------------------------------------------------- Service-Id : 1640 (VPLS) Customer-Id - SAP : lag-4:1640 SAP Egress Policy Id : 20001 ------------------------------------------------------------------------------- Associations ------------------------------------------------------------------------------- Service-Id : 2000 (Epipe)

  • Page 489

    Remark Policies Interface Association ------------------------------------------------------------------------------- No Interface Association Found. Network Policy Id : 2050 ------------------------------------------------------------------------------- Interface Association ------------------------------------------------------------------------------- No Interface Association Found. ------------------------------------------------------------------------------- =============================================================================== *A:SAS-C>config>qos# show qos remark-policy 500 detail =============================================================================== QoS Remarking Policies =============================================================================== ------------------------------------------------------------------------------- Remark Policy-id : 500 Type : dot1p-lsp-exp-shared Description...

  • Page 490

    Remark Policy Command Reference ------------------------------------------------------------------------------- Associations ------------------------------------------------------------------------------- Service-Id : 640 (VPLS) Customer-Id - SAP : lag-2:640 SAP Egress Policy Id : 10001 ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Network ------------------------------------------------------------------------------- Network Policy Id : 50 ------------------------------------------------------------------------------- Interface Association ------------------------------------------------------------------------------- Interface : ip-192.162.105.4 IP Addr. : 192.162.105.4/24 Port Id : 1/1/23...

  • Page 491

    Remark Policies =============================================================================== 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 492

    Remark Policy Command Reference 7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide...

  • Page 493

    Standards and Protocol Support Note: The information presented is subject to change without notice. Nokia assumes no responsibility for inaccuracies contained herein. M(A,N) means 7210 SAS-M in both Access-uplink mode and Network mode; Similarly M(N) means 7210 SAS-M in network mode only T(A,N) means 7210 SAS-M in both Access-uplink mode and Network mode;...

  • Page 494

    Standards and Protocol Support RFC 1772, Application of the Border Gateway Protocol in the Internet is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 1997, BGP Communities Attribute is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 2385, Protection of BGP Sessions via the TCP MD5 Signature Option is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12...

  • Page 495

    Standards and Protocol Support RFC 5668, 4-Octet AS Specific BGP Extended Community is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 6811, Prefix Origin Validation is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx- 10/100GE, R6, and R12 Circuit Emulation RFC 4553, Structure-Agnostic Time Division Multiplexing (TDM) over Packet (SAToP) is...

  • Page 496: Fast Reroute

    Standards and Protocol Support IEEE 802.3ac, VLAN Tag is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 IEEE 802.3ad, Link Aggregation is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S- 1/10GE, Sx-10/100GE, R6, and R12 IEEE 802.3ae, 10 Gb/s Ethernet is supported on M(A,N), T(A,N), X, Mxp, Sx/S-1/10GE, Sx-10/ 100GE, R6, and R12...

  • Page 497

    Standards and Protocol Support RFC 1034, Domain Names - Concepts and Facilities is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 1035, Domain Names - Implementation and Specification is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 1350, The TFTP Protocol (revision 2) is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12...

  • Page 498

    Standards and Protocol Support RFC 5880, Bidirectional Forwarding Detection (BFD) is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 5881, Bidirectional Forwarding Detection (BFD) IPv4 and IPv6 (Single Hop) is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 5883, Bidirectional Forwarding Detection (BFD) for Multihop Paths is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 6528, Defending against Sequence Number Attacks is supported on D, E, K5, K12, M(A,N),...

  • Page 499

    Standards and Protocol Support RFC 6515, IPv4 and IPv6 Infrastructure Addresses in BGP Updates for Multicast VPNs is supported on T(N), Mxp, R6, and R12 RFC 6625, Wildcards in Multicast VPN Auto-Discover Routes is supported on T(N), Mxp, R6, and RFC 6826, Multipoint LDP In-Band Signaling for Point-to-Multipoint and Multipoint-to- Multipoint Label Switched Path is supported on T(N), Mxp, R6, and R12 RFC 7385, IANA Registry for P-Multicast Service Interface (PMSI) Tunnel Type Code Points is...

  • Page 500

    Standards and Protocol Support RFC 4007, IPv6 Scoped Address Architecture is supported on M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 4193, Unique Local IPv6 Unicast Addresses is supported on M(N), T(N), X, Mxp, Sx/S-1/ 10GE, Sx-10/100GE, R6, and R12 RFC 4291, Internet Protocol Version 6 (IPv6) Addressing Architecture is supported on M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 4443, Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6)

  • Page 501

    Standards and Protocol Support RFC 3359, Reserved Type, Length and Value (TLV) Codepoints in Intermediate System to Intermediate System is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/ 100GE, R6, and R12 RFC 3719, Recommendations for Interoperable Networks using Intermediate System to Intermediate System (IS-IS) is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx- 10/100GE, R6, and R12 RFC 3787, Recommendations for Interoperable IP Networks using Intermediate System to...

  • Page 502

    Standards and Protocol Support Management draft-ieft-snmpv3-update-mib-05, Management Information Base (MIB) for the Simple Network Management Protocol (SNMP) is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 draft-ietf-idr-bgp4-mib-05, Definitions of Managed Objects for the Fourth Version of Border Gateway Protocol (BGP-4) is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/ 100GE, R6, and R12 draft-ietf-isis-wg-mib-06, Management Information Base for Intermediate System to Intermediate...

  • Page 503

    Standards and Protocol Support RFC 1724, RIP Version 2 MIB Extension is supported on Mxp RFC 2021, Remote Network Monitoring Management Information Base Version 2 using SMIv2 is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 2115, Management Information Base for Frame Relay DTEs Using SMIv2 is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12...

  • Page 504

    Standards and Protocol Support RFC 2864, The Inverted Stack Table Extension to the Interfaces Group MIB is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 2933, Internet Group Management Protocol MIB is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 3014, Notification Log MIB is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S- 1/10GE, Sx-10/100GE, R6, and R12...

  • Page 505

    Standards and Protocol Support RFC 4022, Management Information Base for the Transmission Control Protocol (TCP) is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 4113, Management Information Base for the User Datagram Protocol (UDP) is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 4220, Traffic Engineering Link Management Information Base is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12...

  • Page 506

    Standards and Protocol Support RFC 3037, LDP Applicability is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/ 100GE, R6, and R12 RFC 3478, Graceful Restart Mechanism for Label Distribution Protocol (Helper Mode) is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 5036, LDP Specification is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/ 100GE, R6, and R12 RFC 5283, LDP Extension for Inter-Area Label Switched Paths (LSPs) is supported on K12, M(N),...

  • Page 507

    Standards and Protocol Support MPLS — RSVP-TE RFC 2702, Requirements for Traffic Engineering over MPLS is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 2747, RSVP Cryptographic Authentication is supported on K12, M(N), T(N), X, Mxp, Sx/S- 1/10GE, Sx-10/100GE, R6, and R12 RFC 2961, RSVP Refresh Overhead Reduction Extensions is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12...

  • Page 508

    Standards and Protocol Support RFC 3623, Graceful OSPF Restart Graceful OSPF Restart (Helper Mode) is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 3630, Traffic Engineering (TE) Extensions to OSPF Version 2 is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 4222, Prioritized Treatment of Specific OSPF Version 2 Packets and Congestion Avoidance is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12...

  • Page 509: Quality Of Service

    Standards and Protocol Support RFC 3985, Pseudo Wire Emulation Edge-to-Edge (PWE3) is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 4385, Pseudo Wire Emulation Edge-to-Edge (PWE3) Control Word for Use over an MPLS PSN is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 4446, IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3) is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 4447, Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP) is...

  • Page 510

    Standards and Protocol Support RFC 3260, New Terminology and Clarifications for Diffserv is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 1058, Routing Information Protocol is supported on Mxp RFC 2082, RIP-2 MD5 Authentication is supported on Mxp RFC 2453, RIP Version 2 is supported on Mxp Timing GR-1244-CORE, Clocks for the Synchronized Network: Common Generic Criteria, Issue 3, May...

  • Page 511

    Standards and Protocol Support VPLS RFC 4761, Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 4762, Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and RFC 5501, Requirements for Multicast Support in Virtual Private LAN Services is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12...

  • Page 512

    Standards and Protocol Support Page 512 7210 SAS-M, T, Mxp, Sx OS Services Guide...

  • Page 513: Documentation Feedback

    Customer Document and Product Support Customer documentation Customer Documentation Welcome Page Technical Support Product Support Portal Documentation feedback Customer Documentation Feedback...

  • Page 514

    © 2013, 2016, 2017 Nokia. 3HE11482AAAHTQZZA...

Comments to this Manuals

Symbols: 0
Latest comments: