7210 SAS OS Quality of Service Guide7210 SAS-M7210 SAS-T7210 SASMxp7210 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.
Nokia is a registered trademark of Nokia Corporation. Other products and company
names mentioned herein may be trademarks or tradenames of their respective
owners.
The information presented is subject to change without notice. No responsibility is
assumed for inaccuracies contained herein.
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
applicable agreements.
About This Guide................................................................................................................................................15
List of Technical Publications ........................................................................................................................16
Technical Support .........................................................................................................................................17
In This Chapter ...................................................................................................................................................19
Alcatel-Lucent 7210 SAS-Series Services Configuration Process .....................................................................19
In This Chapter ..................................................................................................................................................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
Overview of QoS Policies on 7210 SAS-Mxp in network mode ....................................................................28
Overview of QoS Policies on 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE ...................................32
Service and Network QoS Policies .....................................................................................................................36
Network QoS Policies in Network Mode.............................................................................................................37
'ip-interface' type Network QoS policy ..........................................................................................................38
“port” Type Network QoS Policy ....................................................................................................................40
Network QoS Policies for Access-uplink Mode ..................................................................................................42
Network Queue policies in Network mode .........................................................................................................44
Network Queue policies in Access-uplink mode ................................................................................................46
Meter ID.........................................................................................................................................................48
Committed Information Rate for Meters ........................................................................................................49
Peak Information Rate for Meters .................................................................................................................49
Adaptation Rule for Meters............................................................................................................................50
Maximum Burst Size (For Meter/Policers).....................................................................................................51
Meter Counters..............................................................................................................................................52
Meter Modes .................................................................................................................................................52
Color Aware Policing ..........................................................................................................................................52
QoS Overrides for Meters/Policers .....................................................................................................................53
Configuration guidelines of QoS Override .....................................................................................................54
Configuring Meter Override parameters .............................................................................................................54
Queue ID ......................................................................................................................................................55
Committed Information Rate for Queues.......................................................................................................56
Peak Information Rate for Queues ................................................................................................................57
Adaptation Rule for Queues ..........................................................................................................................57
Committed Burst Size (CBS) and the Maximum Burst Size (MBS) for Queues ............................................59
Service Ingress QoS Policies .............................................................................................................................61
7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide3
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
71
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
Buffer pool allocation - Per Node MBS pool on 7210 SAS-T .......................................................................79
Decommissioning Ports with Per port MBS pool ................................................................................................80
Using decommission command for Buffer Allocation on 7210 SAS-M and 7210 SAS-T devices............80
Configuration guidelines for use of ‘Decommission’ commands on 7210 SAS-M and 7210 SAS-T devices
81
Buffer Pools on 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE devices................................................82
Buffer Pools on 7210 SAS-Mxp..........................................................................................................................83
Slope Policies for 7210 SAS-M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE devices84
RED Slopes In Network and Access-uplink Mode ........................................................................................85
Tuning the Shared Buffer Utilization Calculation...........................................................................................88
Schedulers on 7210 SAS-Mxp ...........................................................................................................................97
CPU Queues ......................................................................................................................................................97
Remark Policy on 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, and 7210 SAS-Mxp (Network
Egress Port Rate Limiting...................................................................................................................................98
Discard Eligibility Indicator (DEI) based Classification and Marking............................................ 107
In This Section..................................................................................................................................................107
DEI based Classification ..................................................................................................................................107
DEI based marking ..........................................................................................................................................109
Port Level Egress Rate-Limiting ....................................................................................................... 111
In This Section..................................................................................................................................................111
Show Commands...................................................................................................................................116
Frame Based Accounting .................................................................................................................. 119
In This Section..................................................................................................................................................119
Frame Based Accounting ............................................................................................................................119
Effects of Enabling Ingress Frame Based Accounting on Ingress Meter Functionality ..............................120
Effects of Enabling Egress Frame Based Accounting on Network Queue Functionality ............................120
Accounting and Statistics ...........................................................................................................................120
In This Section..................................................................................................................................................125
Service Management Tasks .............................................................................................................................158
In This Section..................................................................................................................................................209
Service Management Tasks .............................................................................................................................216
Show Commands...................................................................................................................................226
Service Ingress QoS Policies ............................................................................................................ 229
In This Section..................................................................................................................................................229
Create Service Ingress QoS Policies ..........................................................................................................244
Service Ingress QoS Policy .........................................................................................................................244
Service Ingress QoS Meter ...................................................................................................................245
Service Ingress IP Match Criteria ..........................................................................................................246
Service Ingress MAC Match Criteria .....................................................................................................247
Examples for Computation of resources required for Service ingress QoS policy.................................248
Applying Service Ingress Policies ..............................................................................................................284
Service Management Tasks .............................................................................................................................286
In This Section..................................................................................................................................................331
Access Egress QoS Policies for 7210 SAS-Mxp ............................................................................. 359
In This Section..................................................................................................................................................359
Service Egress Policies for 7210 SAS-Mxp...................................................................................... 379
In This Section..................................................................................................................................................379
QoS Port Scheduler Policies for 7210 SAS-M and 7210 SAS-T ..................................................... 395
In This Section..................................................................................................................................................395
Creating a QoS Port Scheduler Policy ...................................................................................................396
Service Management Tasks .............................................................................................................................396
Copying and Overwriting Scheduler Policies ..............................................................................................397
Schedulers on 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE.............................................. 399
In this section....................................................................................................................................................399
87210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide
Table of Contents
QoS Port Scheduler Policy Command Reference ............................................................................................401
Port Scheduler Policy Commands .........................................................................................................403
Show Commands...................................................................................................................................405
Schedulers on 7210 SAS-Mxp ........................................................................................................... 409
In This Section..................................................................................................................................................409
Scheduling with SAP based queues on Access ports .....................................................................................410
Scheduling on Network Ports ...........................................................................................................................412
Scheduling on Hybrid port with SAP based egress queues .............................................................................412
Port Based Scheduling and Queuing on Access Ports ....................................................................................413
Scheduling on hybrid port with port based SAP queues ..................................................................................415
In This Section..................................................................................................................................................417
Service Management Tasks .............................................................................................................................426
In This Section..................................................................................................................................................445
Service Management Tasks .............................................................................................................................446
Creating a Queue Management Policy .......................................................................................................446
In This Section..................................................................................................................................................461
147210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide
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. 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.All the variants of 7210 SAS-M and 7210 SAS-T can be configured in two modes,
that is, in network mode and in access-uplink mode. In network mode configuration 7210
SAS-M and 7210 SAS-T uses IP/MPLS to provide service transport. In access-uplink mode
configuration 7210 SAS-M and 7210 SAS-T uses Ethernet QinQ technology to provide
service transport. The mode can be selected by configuring the BOF appropriately. 7210
SAS-Mxp, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE devices operates only on
Network mode.
Preface
This guide also presents examples to configure and implement various tests.
Note:
•This user guide is applicable to all 7210 SAS-M, 7210 SAS-T, 7210 SAS-Mxp, 7210
SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE platforms, unless specified otherwise.
•In either mode, it is expected that the user will only configure the required CLI
parameters appropriate for the mode he intends to use. Unless otherwise noted, most
of the configuration is similar in both the network mode and Access uplink mode.
•The 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE can be operated in
standalone mode and satellite mode. The user guide provides features and CLI
commands supported in 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE
standalone mode of operations. Only the Basics System Configuration User Guide
contains information on how to boot the 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/
100GE in satellite mode of operation.
7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide15
About This Guide
Audience
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.
This document is organized into functional chapters and provides concepts and descriptions
of the implementation flow, as well as Command Line Interface (CLI) syntax and command
usage.
This manual is intended for network administrators who are responsible for configuring the
7210 SAS-Series routers. It is assumed that the network administrators have an understanding
of networking principles and configurations. Protocols, standards, and services described in
this manual include the following:
•CLI concepts
•Quality of Service (QoS) policies and profiles
List of Technical Publications
The 7210 SAS-M, T, X, R6, R12, Mxp, Sx OS documentation set is composed of the
following books:
•7210 SAS-M, T, X, R6, R12, Mxp, Sx OS Basic System Configuration Guide
This guide describes basic system configurations and operations.
•7210 SAS-M, T, X, R6, R12, Mxp, Sx OS System Management Guide
This guide describes system security and access configurations as well as event
logging and accounting logs.
This guide provides an overview of routing concepts and provides configuration
examples for OSPF, IS-IS, and route policies.
Technical Support
Preface
If you purchased a service agreement for your 7210 SAS device and related products from a
distributor or authorized reseller, contact the technical support staff for that distributor or
reseller for assistance. If you purchased an Alcatel-Lucent service agreement, contact your
welcome center.
7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide17
About This Guide
187210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide
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 accessuplink mode. Unless otherwise noted, many of the qos policies are applicable to both network
mode and access-uplink mode.
Getting Started
Alcatel-Lucent 7210 SAS-Series Services
Configuration Process
Table 1 lists the tasks necessary to configure and apply QoS policies. This guide is presented
in an overall logical configuration flow. Each section describes a software area and provides
CLI syntax and command usage to configure parameters for a functional area.
Table 1: Configuration Process
AreaTaskChapter
Policy configurationConfiguring QoS Policies
•Egress RatePort Level Egress Rate-Limiting
•Accounting ModeFrame Based Accounting
•NetworkNetwork QoS Policies
•Network queueNetwork Queue QoS Policies
•SAP ingressService Ingress QoS Policies
7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide19
Alcatel-Lucent 7210 SAS-Series Services Configuration Process
207210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide
In This Chapter
This chapter provides information about Quality of Service (QoS) policy management.
Topics in this chapter include:
•QoS Overview
•QoS Policy Entities
•Configuration Notes
QoS Policies
QoS Overview
The 7210 SAS devices are designed with QoS mechanisms on both ingress and egress to
support multiple services per physical port. The 7210 SAS devices are extensive and flexible
capabilities to Classify, Police, Queue, Shape, and mark traffic.
Note: The QoS capabilities supported on different 7210 SAS platforms are different. In other
words, not all the platforms support all of the capabilities. Please read through the following
chapters to know what is available on different 7210 SAS platforms.
In the Nokia service router’s service model, a service is provisioned on the provider-edge
(PE) equipment. Service data is encapsulated and then sent in a service tunnel to the far-end
Nokia service router where the service data is delivered.
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.
7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide21
QoS Overview
The 7210 SAS supports eight forwarding classes internally named: Network-Control, High1, 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. There are different types of QoS policies that cater
to the different QoS needs at each point in the service delivery model. QoS policies are
defined in a global context in the 7210 SAS and only take effect when the policy is applied
to a relevant entity.
QoS policies are uniquely identified with a policy ID number or name. Typically, Policy ID
1 or Policy ID “default” (there are a few instances where the default QoS policy uses a
different ID) is reserved for the default policy which is used if no policy is explicitly applied.
The QoS policies within the 7210 SAS can be divided into three main types:
•QoS policies are used for classification, defining metering and queuing attributes and
defining marking behavior.
•Slope policies define default buffer allocations and WRED slope definitions.
•Port Scheduler policies, SAP ingress/egress policies or network/network-queue
policies determine how queues are scheduled.
Overview of QoS Policies on 7210 SAS-M and 7210 SAS-T
in Access-uplink mode
When configured to operate in access-uplink mode, 7210 SAS M and 7210 SAS-T QoS
policies are applied on service ingress, access port egress, and access-uplink port ingress and
egress. 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 and buffer allocation
•QoS marking/interpretation
There are several types of QoS policies:
•Service ingress (for access SAP ingress)
•Access egress (for access port egress)
•Network (for access-uplink port, ingress and egress)
•Network queue (for access-uplink port, egress)
227210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide
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. The mapping of traffic to
meters can be based on combinations of customer QoS marking (IEEE 802.1p bits), IP and
MAC criteria. The characteristics of the forwarding class meters are defined within the policy
as to the number of forwarding class meters for unicast traffic and the meter characteristics
(like CIR, PIR, etc.). Each of the forwarding classes can be associated with different unicast
parameters. A service ingress QoS policy also defines up to three (3) meters per forwarding
class to be used for multipoint traffic for multipoint services. There can be up to 32 meters in
total per Service ingress QOS policies. In the case of the VPLS, four types of forwarding are
supported (which is not to be confused with forwarding classes); unicast, multicast,
broadcast, and unknown. Multicast, broadcast, and unknown types are flooded to all
destinations within the service while the unicast forwarding type is handled in a point-topoint fashion within the service.
An access egress policy is analogous to a SAP egress policy as defined in the 7x50 SR series
of products. The difference is the point of attachment. 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 QoS policy maps the traffic egressing out on
the customer facing ports into various queues and marks the traffic accordingly. The FCs are
mapped onto the queues. There are 8 queues at the port level. FC-to-queue mapping is static
and is not configurable. The number of queues is not user configurable and software always
allocates 8 queues at the port level. An access egress policy also defines how to remark the
forwarding class to packet header bits (for example: IEEE 802.1p bits in the L2 VLAN
header, etc.).
For devices configured to operate in access uplink mode, network QoS policies apply to
access uplink ports. Access-uplink ports in access-uplink mode are analogous to network
ports in network mode. On ingress, the policy applied to an access-uplink port maps incoming
Dot1p values to forwarding class and profile state for the traffic received from the core
network. On egress, the policy maps forwarding class and profile state to packet header
values (for example: IEEE 802.1p value in the L2 header, etc.) for traffic to be transmitted
into the core network.
Network queue policies are applied on egress of access-uplink ports when operating in
access-uplink mode. The policies define the forwarding class queue characteristics for these
entities. The FCs are mapped onto the queues. There are 8 queues at the port level. FC-toqueue mapping is system defined not user configurable. The number of queues is not user
configurable and software always allocates 8 queues at the port level.
Service ingress, access egress, and network QoS policies are defined with a scope of either
template or exclusive. Template policies can be applied to multiple entities (such as SAPs and
ports) whereas exclusive policies can only be applied to a single entity.
7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide23
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 accessuplink mode. A network QoS policy defines both ingress and egress behavior. One network
queue policy can be applied to an access-uplink port. If no QoS policy is explicitly applied to
a SAP, port or interface, a default QoS policy is applied.
A summary of the major functions performed by the QoS policies is listed in Table 3.
Note: Not all policies are supported on all platforms. For more information, see the sections,
and chapters below.
Table 2: QoS Policy Types and Descriptions for 7210 SAS-M, T devices in Access-uplink mode
Policy TypeDevice
Operating
Mode
Service Ingress Access-Uplink
mode
Access Egress Access-Uplink
mode
NetworkAccess-Uplink
mode
Applied at…DescriptionPage
SAP ingress•Defines up to 16 forwarding class
61
meters and meter parameters for traffic
classification.
•Defines match criteria to map flows to
the meters based on any one of the
criteria.
Access port•Defines up to 8 forwarding class queues
42
and queue parameters for traffic
classification.
•Maps forwarding classes to the queues.
•Defines FC to remarking values (for
example: Dot1p, etc.).
•Defines CIR levels and PIR weights that
determines how the queue gets
prioritized by the scheduler.
Access-Uplink
port
•Used for classification/marking of IP
packets.
37
•At ingress, defines Dot1p to FC
mapping and 8 meters.
•At egress, defines FC to remarking
values (for example: Dot1p, etc.)
247210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide
QoS Policies
Table 2: QoS Policy Types and Descriptions for 7210 SAS-M, T devices in Access-uplink mode (Continued)
Policy TypeDevice
Operating
Mode
Network QueueAccess-uplink
mode
SlopeAccess-uplink
mode
Port schedulerAccess-uplink
mode
Applied at…DescriptionPage
Access-uplink
port
Access ports
and Access
uplink ports
Access ports
and Access
uplink ports
•Defines forwarding class mappings to
network queues and queue
characteristics for the queues.
• Enables or disables the high-slope, lowslope, and non-TCP parameters within
the egress pool.
•Defines the parameters for the port
scheduler.
44
90
94
Overview of QoS Policies on 7210 SAS-M and 7210 SAS-T
in network mode
QoS policies are applied on service ingress, access port egress, network port ingress and
egress, and network IP interfaces ingress when configured to operate in network mode.
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:
•Service ingress (for access SAP ingress)
•Access egress (for access port egress)
•Network (for network and hybrid port, ingress and egress)
•Network queue (for network and hybrid port, egress)
•Port scheduler (for access port, network port and hybrid port egress)
•Slope Policies
•Remark policies (for access port, network port and hybrid port egress marking only
on 7210 SAS-T Network Mode)
7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide25
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. The characteristics of the forwarding class meters are defined within the policy
as to the number of forwarding class meters for unicast traffic and the meter characteristics
(like CIR, PIR, etc.). Each of the forwarding classes can be associated with different unicast
parameters. A service ingress QoS policy also defines up to three (3) meters per forwarding
class to be used for multipoint traffic for multipoint services. There can be up to 32 meters in
total per Service ingress QOS policies. In the case of the VPLS, four types of forwarding are
supported (which is not to be confused with forwarding classes), unicast, multicast,
broadcast, and unknown. Multicast, broadcast, and unknown types are flooded to all
destinations within the service while the unicast forwarding type is handled in a point-topoint fashion within the service.
An access egress policy is analogous to a SAP egress policy as defined in the 7x50 SR series
of products. The difference is the point of attachment. 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 QoS policy maps the traffic egressing out on
the customer facing ports into various queues and marks the traffic accordingly. The FCs are
mapped onto the queues. There are 8 queues at the port level. FC-to-queue mapping is static
and is not configurable. The number of queues is not user configurable and software allocates
8 queues at the port level. An access egress policy also defines how to remark the forwarding
class to packet header bits (e.g. IEEE 802.1p bits in the L2 VLAN header, and others.).
For devices configured to operate in network mode, there are two types of network QoS
policies, one applied to a network IP interface and the other is applied to a network port.
Network QoS policies are applied to IP interfaces. On ingress, the policy applied to an IP
interface maps incoming MPLS LSP EXP values to forwarding class and profile state for the
traffic received from the core network. On egress, the policy maps forwarding class and
profile state to MPLS LSP EXP values for traffic to be transmitted into the core network. The
network policy applied to a network port maps incoming IP packets, DSCP or Dot1p values,
to the forwarding class and the profile state for the traffic received from the core network. On
egress, the policy maps forwarding class and profile state to DSCP and/or Dot1p values for
IP traffic to be transmitted into the core network.
Network queue policies are applied on egress to network ports when operating in network
mode. The policies define the forwarding class queue characteristics for these entities. The
FCs are mapped onto the queues. There are 8 queues at the port level. FC-to-queue mapping
is static and is not configurable. The number of queues is not user configurable and software
allocates 8 queues at the port level.
Service ingress, access egress, and network QoS policies are defined with a scope of either
template or exclusive. Template policies can be applied to multiple entities (such as SAPs and
ports) whereas exclusive policies can only be applied to a single entity.
267210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide
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. when operating in network mode. One network QoS policy can be
applied to a access-uplink port when operating in access-uplink modeA network QoS policy
defines both ingress and egress behavior. One network queue policy can be applied to the
network port or a access-uplink port.
If no QoS policy is explicitly applied to a SAP, port or interface, a default QoS policy is
applied.
A summary of the major functions performed by the QoS policies is listed in Tabl e 3.
Note: Not all policies are supported on all platforms. For more information, see the sections,
and chapters below.
Table 3: QoS Policy Types and Descriptions for 7210 SAS-M, T devices in network mode
Policy TypeDevice
Operating
Mode
Applied at…DescriptionPage
Service Ingress Network mode SAP ingress•Defines up to 16 forwarding class
meters and meter parameters for traffic
classification.
•Defines match criteria to map flows to
the meters based on any one of the
criteria.
Access Egress Network mode Access port•Defines up to 8 forwarding class queues
and queue parameters for traffic
classification.
•Maps forwarding classes to the queues.
•Defines FC to remarking values.
•Defines CIR levels and PIR weights that
determines how the queue gets
prioritized by the scheduler.
61
61
7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide27
QoS Overview
Table 3: QoS Policy Types and Descriptions for 7210 SAS-M, T devices in network mode (Continued)
Policy TypeDevice
Operating
Mode
Network (of
type’ipinterface’)
Network (of
type’port’)
Network QueueNetwork mode Network Ports
SlopeNetwork mode Access ports,
Network modeIP interface•Used for classification/marking of
Network modeNetwork and
Applied at…DescriptionPage
Hybrid Ports
and Hybrid
Ports
Network ports
and Hybrid
ports
MPLS packets.
•At ingress, defines MPLS LSP-EXP to
FC mapping and 12 meters used by FCs.
•At egress, defines FC to MPLS LSPEXP marking.
•Used for classification/marking of IP
packets.
•At ingress, defines DSCP or Dot1p to
FC mapping and 8 meters.
•At egress, defines FC to DSCP or Dot1p
marking or both.
•Defines forwarding class mappings to
network queues and queue
characteristics for the queues.
• Enables or disables the high-slope, lowslope, and non-TCP parameters within
the egress pool.
37
37
44
90
Port schedulerNetwork mode Access ports,
Network ports
and Hybrid
ports
Remark Network Mode
(Only on 7210
SAS-T)
Network Port,
Access ports
and Hybrid
Ports
•Defines the parameters for the port
scheduler.
•Applied at egress, defines the FC to
Priority Bits (DSCP or dot1p or EXP)
marking.
94
461
Overview of QoS Policies on 7210 SAS-Mxp in network
mode
QoS policies are applied on service ingress, access port egress, network port ingress and
egress, and network IP interfaces ingress when configured to operate in network mode.
287210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide
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:
•Service ingress (for access SAP ingress)
•Access egress (for access SAP egress)
•Access egress (for access port egress)
•Network (for network and hybrid port, ingress and egress)
•Network queue (for network and hybrid port, egress)
•Port scheduler (for access port, network port and hybrid port egress)
•Slope Policies
•Remark policies (for access port, network port and hybrid port egress marking)
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. The characteristics of the forwarding class meters are defined within the policy
as to the number of forwarding class meters for unicast traffic and the meter characteristics
(like CIR, PIR, etc.). Each of the forwarding classes can be associated with different unicast
parameters. A service ingress QoS policy also defines up to three (3) meters per forwarding
class to be used for multipoint traffic for multipoint services. There can be up to 32 meters in
total per Service ingress QOS policies. In the case of the VPLS, four types of forwarding are
supported (which is not to be confused with forwarding classes); unicast, multicast,
broadcast, and unknown. Multicast, broadcast, and unknown types are flooded to all
destinations within the service while the unicast forwarding type is handled in a point-topoint fashion within the service.
Service egress QoS policies are applied to SAPs and map forwarding classes to service egress
queues for a service. The system allocates a maximum of 8 queues per SAP for the 8
forwarding classes. It is not user configurable. All traffic types (that is, both unicast and BUM
traffic types) share the same queue on service egress. A service egress QoS policy defines the
forwarding class queue characteristics and also defines how to remark the forwarding class
to priority bits in the packet header (for example: IEEE 802.1p bits in the Ethernet VLAN tag)
in the customer traffic.
7210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide29
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.).
The 7210 SAS-Mxp provides an option to use port-based queuing on access ports. This is a
per-node configuration option and is mutually exclusive to use of SAP-based egress queues
(configured through service egress policies). When enabled, all SAPs on the access port share
a set of 8 queues configured on the port and the access egress policy is used to define the
queue parameters for port-based queues.
For devices configured to operate in network mode, there are two types of network QoS
policies, one applied to a network IP interface and the other is applied to a network port.
Network QoS policies are applied to IP interfaces. On ingress, the policy applied to an IP
interface maps incoming MPLS LSP EXP values to forwarding class and profile state for the
traffic received from the core network. On egress, the policy maps forwarding class and
profile state to MPLS LSP EXP values for traffic to be transmitted into the core network. The
network policy applied to a network port maps incoming IP packets, DSCP or Dot1p values,
to the forwarding class and the profile state for the traffic received from the core network. On
egress, the policy maps forwarding class and profile state to DSCP and/or Dot1p values for
IP traffic to be transmitted into the core network.
Network queue policies are applied on egress to network ports when operating in network
mode. The policies define the forwarding class queue characteristics for these entities. The
FCs are mapped onto the queues. There are 8 queues at the port level. FC-to-queue mapping
is static and is not configurable. The number of queues is not user configurable and software
allocates 8 queues at the port level.
Service ingress, access egress, and network QoS policies are defined with a scope of either
template or exclusive. Template policies can be applied to multiple entities (such as SAPs and
ports) whereas exclusive policies can only be applied to a single entity.
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. A network QoS policy defines both ingress and egress
behavior. One network queue policy can be applied to the network port. If no QoS policy is
explicitly applied to a SAP, port or interface, a default QoS policy is applied.
A summary of the major functions performed by the QoS policies is listed in Table 3.
Note: Not all policies are supported on all platforms. For more information, see the sections,
and chapters below.
307210 SAS-M, T, Mxp, Sx, S OS Quality of Service Guide
Loading...
+ 484 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.