All specifications, procedures, and information in this document are subject to change and revision at any time
without notice. The information contained herein is believed to be accurate as of the date of publication. AlcatelLucent provides no warranty, express or implied, regarding its contents. Users are fully responsible for application
or use of the documentation.
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks
are the property of their respective owners.
Copyright 2015 Alcatel-Lucent.
All rights reserved.
Disclaimers
Alcatel-Lucent products are intended for commercial uses. Without the appropriate network design engin eering,
they must not be sold, licensed or otherwise distributed for use in any hazardous environments requiring fail-safe
performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic
control, direct life-support machines, or weapons systems, in which the failure of products could lead directly to
death, personal injury, or severe physical or environmental damage. The customer hereby agrees that the use, sale,
license or other distribution of the products for any such application without the prior written consent of
Alcatel-Lucent, shall be at the customer's sole risk. The customer hereby agrees to defend and hold Alcatel-Lucent
harmless from any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the
use, sale, license or other distribution of the products in such applications.
This document may contain information regarding the use and installation of non-Alcatel-Lucent products. Please
note that this information is provided as a courtesy to assist you. While Alcatel-Lucent tries to ensure that this
information accurately reflects information provided by the supplier, please refer to the materials provided with any
non-Alcatel-Lucent product and contact the supplier for confirmation. Alcatel-Lucent assumes no responsibility or
liability for incorrect or incomplete information provided about non-Alcatel-Lucent products.
However, this does not constitute a representation or warranty. The warranties provided for Alcatel-Lucent products,
if any, are set forth in contractual documentation entered into by Alcatel-Lucent and its customers.
This document was originally written in English. If there is any conflict or inconsistency between the English
version and any other version of a document, the English version shall prevail.
This guide describes the Quality of Service (QoS) provided by the routers and presents examples
to configure and implement various protocols and services.
This guide 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.
Audience
Preface
This guide is intended for network administrators who are responsible for configuring the routers.
It is assumed that the network administrators have an understanding of network i ng principles and
configurations. Concepts described in this guide include the following:
•CLI concepts
•Quality of Service (QoS) policies and profiles
7950 XRS Quality of Service GuidePage 13
Preface
List of Technical Publications
The documentation set is composed of the following guides:
•
This guide describes basic system configurations and operations.
•
This guide describes system security and access configurations as well as event logging
and accounting logs.
•
•
This guide describes logical IP routing interfaces and associated attributes such as an IP
address, as well as IP and MAC-based filtering, and VRRP and Cflowd.
•
This guide provides an overview of routing concepts and provides configuration examples
for RIP, OSPF, IS-IS, BGP, and route policies.
•Services Overview Guide
This guide describes how to configure service parameters such as service distribution
points (SDPs), customer information, and user services.
•Layer 2 Services and EVPN Guide
This guide describes Virtual Leased Lines (VLL), Virtual Private LAN Service (VPLS),
Provider Backbone Bridging (PBB), and Ethernet VPN (EVPN).
• Layer 3 Services Guide
This guide describes Internet Enhanced Services (IES) and Virtual Private Routed
Network (VPRN) services.
• Versatile Service Module Guide
This guide describes how to configure service parameters for the Versatile Service Module
(VSM).
•
This guide describes how to configure features such as service mirroring and Operations,
Administration and Management (OAM) tools.
•
This guide describes how to configure Quality of Service (QoS) policy management.
Page 147950 XRS Quality of Service Guide
Technical Support
If you purchased a service agreement for your router 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, follow this link to contact an AlcatelLucent support representative and to access product manuals and documentation updates:
Preface
http://support.alcatel-lucent.com
7950 XRS Quality of Service GuidePage 15
Preface
Page 167950 XRS Quality of Service Guide
In This Chapter
This chapter provides process flow information to configure Quality of Service (QoS) policies and
provision services.
Getting Started
7950 XRS Quality of Service GuidePage 17
In This Chapter
Alcatel-Lucent 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
• NetworkNetwork QoS Policies on page 73
• Network queueNetwork Queue QoS Policies on page 83
• SAP ingressService Egress and Ingress QoS Policies on page 131
• SlopeSlope QoS Policies on page 521
Reference• List of IEEE, IETF, and
other proprietary entities
Note: In SR OS 12.0.R4 any function that displays an IPv6 address or prefix changes to reflect
rules described in RFC 5952, A Recommendation for IPv6 Address Text Representation.
Specifically, hexadecimal letters in IPv6 addresses are now represented in lowercase, and the
correct compression of all leading zeros is displayed. This changes visible display output
compared to previous SR OS releases. Previous SR OS behavior can cause issues with operator
scripts that use standard IPv6 address expressions and with libraries that have standard IPv6
parsing as per RFC 5952 rules. See the section on IPv6 Addresses in the Router Configuration
Guide for more information.
Standards and Protocol Support on page 651
Page 187950 XRS Quality of Service Guide
In This Chapter
QoS Policies
This chapter provides information about Quality of Service (QoS) policy
management.
Topics in this chapter include:
•QoS Overview on page 20
•Service and Network QoS Policies on page 24
→ Network QoS Policies on page 25
→ Network Queue QoS Policies on page 27
→ Service Ingress QoS Policies on page 38
→ Service Egress QoS Policies on page 44
→ Queue Parameters on page 30
•QoS Policies on page 21
•Scheduler Policies on page 54
•QoS Policy Entities on page 67
•Configuration Notes on page 72
7950 XRS Quality of Service GuidePage 19
In This Chapter
QoS Overview
Routers are designed with Quality of Service (QoS) mechanisms on both ingress and egress to
support multiple customers and multiple services per physical interface. The router has an
extensive and flexible capabilities to classify, police, shape and mark traffic.
In the Alcatel-Lucent service router’ s service mo del, a service is provis ioned on the pro vider -edge
(PE) equipment. Service data is encapsulated and then sent in a service tunnel to the far-end
Alcatel-Lucent 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
Alcatel Lucent service routers (such as the 7950 XRS, 7750 SR, 7710 SR, 7750 SR MG and 745 0
ESS) 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.
The router supports eight forwarding classes internally named: Network-Control, High-1,
Expedited, High-2, Low-1, Assured, Low-2 and Best-Ef fort. The forwarding classes are discussed
in more detail in Forwarding Classes on page 64.
Router 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 router 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. Policy ID 1 or Policy ID
“default” is reserved for the default policy which is used if no policy is explicitly applied.
The QoS policies within the router can be divided into three main types:
•QoS policies are used for classification, defining and queuing attributes and marking.
•Scheduler policies determine how queues are scheduled.
Page 207950 XRS Quality of Service Guide
QoS Policies
Service ingress, service egress, and network QoS policies are defined with a scope of either
template or exclusive. T emplate policies can be applied to multiple SAPs or IP interfaces, whereas,
exclusive policies can only be applied to a single entity.
On most systems, the number of configurable SAP ingress and egress QOS policies per system is
larger than the maximum number that can be applied per FP. The tools dump system-resources
output displays the actual number of policies applied on a given FP (noting that the default SAP
ingress policy is always applied once for internal use). The show qos sap-ingress and show qos sap-egress commands can be used to show the number of polices configured.
One service ingress QoS policy and one service egress QoS policy can be applied to a specific
SAP. One network QoS policy can be applied to a specific IP interface. A network QoS policy
defines both ingress and egress behavior.
Router QoS policies are applied on service ingress, service egress, and network interfaces and
define:
QoS Policies
Classification rules for how traffic is mapped to queues
•The number of forwarding class queues
•The queue parameters used for policing, shaping, and buffer allocation
•QoS marking/interpretation
There are several types of QoS policies:
•Service ingress
•Service egress
•Network (for ingress and egress)
•Network queue (for ingress and egress)
•Slope
Service ingress QoS policies are applied to the customer-facing Service Access Points (SAPs) and
map traffic to forwarding class queues on ingress. The mapping of traffic to queues can be based
on combinations of customer QoS marking (IEEE 802.1p bits, DSCP, and TOS precedence), IP
and MAC criteria. The characteristics of the forwarding class queues are defined within the policy
as to the number of forwarding class queues for unicast traffic and the queue characteristics. There
can be up to eight (8) unicast forwarding class queues in the policy; one for each forwarding class.
A service ingress QoS policy also defines up to three (3) queues per forwarding class to be used
for multipoint traffic for multipoint services. 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
7950 XRS Quality of Service GuidePage 21
QoS Policies
unknown. Multicast, broadcast, and unknown types are flooded to all destinations within the
service while the unicast forwarding type is handled in a point-to-point fashion within the service.
Service egress QoS policies are applied to SAPs and map forwarding classes to service egress
queues for a service. Up to 8 queues per service can be defined for the 8 forwarding classes. A
service egress QoS policy also defines how to remark the forwarding class to IEEE 802.1p bits in
the customer traffic.
Network QoS policies are applied to IP interfaces. On ingress, the policy applied to an IP interface
maps incoming DSCP and 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 DSCP and
EXP values for traffic to be transmitted into the core network.
Network queue policies are applied on egress to network ports and on ingress to MDAs. The
policies define the forwarding class queue characteristics for these entities.
Service ingress, service egress, and network QoS policies are defined with a scope of either
template or exclusive. Template policies can be applied to multiple SAPs or IP interfaces whereas
exclusive policies can only be applied to a single entity.
One service ingress QoS policy and one service egress QoS policy can be applied to a specific
SAP. One network QoS policy can be applied to a specific IP interface. A network QoS policy
defines both ingress and egress behavior.
If no QoS policy is explicitly applied to a SAP or IP interface, a default QoS policy is applied.
Page 227950 XRS Quality of Service Guide
QoS Policies
A summary of the major functions performed by the QoS policies is listed in Table 2.
Table 2: QoS Policy Types and Descriptions
Policy TypeApplied at…DescriptionPage
Service Ingress SAP ingress• Defines up to 32 forwarding class queues and queue parame-
ters for traffic classification.
• Defines up to 31 multipoint service queues for broadcast,
multicast and destination unknown traffic in multipoint services.
• Defines match criteria to map flows to the queues based on
combinations of customer QoS (IEEE 802.1p bits, DSCP,
TOS Precedence), IP criteria or MAC criteria.
Service Egress SAP egress• Defines up to 8 forwarding class queues and queue parame-
ters for traffic classification.
• Maps one or more forwarding classes to the queues.
Network Router interface• Packets are marked using QoS policies on edge devices.
Used for classification/marking of MPLS packets.
• At ingress, defines MPLS LSP-EXP to FC mapping.
• At egress, defines FC to MPLS LSP-EXP marking.
• Used for classification/marking of IP packets.
• At ingress, defines DSCP or Dot1p to FC mapping.
• At egress, defines FC to DSCP or Dot1p marking or both.
•
Network
Queue
Network ingress• Defines forwarding class mappings to network queues and
queue characteristics for the queues.
38
44
25
27
SlopePorts• Enables or disables the high-slope, low-slope, and non-TCP
52
parameters within the egress or ingress pool.
SchedulerCustomer multi-
service site
Service SAP
• Defines the hierarchy and parameters for each scheduler.
• Defined in the context of a tier which is used to place the
scheduler within the hierarchy.
54
• Three tiers of virtual schedulers are supported.
7950 XRS Quality of Service GuidePage 23
QoS Policies
Service and Network QoS Policies
The QoS mechanisms within the routers are specialized for the type of traffic on the interface. For
customer interfaces, there is service ingress and egress traffic, and for network core interfaces,
there is network ingress and network egress traffic ().
The router uses QoS policies applied to a SAP for a service or to an network port to define the
queuing, queue attributes, and QoS marking/interpretation.
The router supports four types of service and network QoS policies:
•Service ingress QoS policies
•Service egress QoS policies
•Network QoS policies
•Network Queue QoS policies
Page 247950 XRS Quality of Service Guide
Network QoS Policies
Network QoS policies define egress QoS marking and ingress QoS interpretation for traffic on
core network IP interfaces. The router automatically creates egress queues for each of the
forwarding classes on network IP interfaces.
A network QoS policy defines both the ingress and egress handling of QoS on the IP interface.
The following functions are defined.
•Ingress
→ Defines DSCP name mappings to a forwarding classes.
→ Defines LSP EXP value mappings to forwarding classes.
•Egress
→ Defines the forwarding class to DSCP value markings.
→ Defines forwarding class to LSP EXP value markings.
→ Enables/disables remarking of QoS.
QoS Policies
The required elements to be defined in a network QoS policy are:
•A unique network QoS policy ID.
•Egress forwarding class to DSCP value mappings for each forwarding class.
•Egress forwarding class to LSP EXP value mappings for each forwarding class.
•Enabling/disabling of egress QoS remarking.
•A default ingress forwarding class and in-profile/out-of-profile state.
Optional network QoS policy elements include:
•DSCP name to forwarding class and profile state mappings for all DSCP values received.
•LSP EXP value to forwarding class and profile state mappings for all EXP values
received.
Network policy ID 1 is reserved as the default network QoS policy. The default policy cannot be
deleted or changed.
The default network QoS policy is applied to all network interfaces which do not have another
network QoS policy explicitly assigned.
For network ingress, Table 4 and Table 5 list the default mapping of DSCP name and LSP EXP
values to forwarding class and profile state for the default network QoS policy.
Table 4: Default Network QoS Policy DSCP to Forwarding Class Mappings
Network queue policies define the network forwarding class queue characteristics. Network queue
policies are applied on egress on core network ports and on ingress on . Network queue policies
can be configured to use as many queues as needed This means that the number of queues can
vary. Not all policies will use eight queues like the default network queue policy.
The queue characteristics that can be configured on a per-forwarding class basis are:
•Committed Buffer Size (CBS) as a percentage of the buffer pool
•Maximum Buffer Size (MBS) as a percentage of the buffer pool
•High Priority Only Buffers as a percentage of MBS
•Peak Information Rate (PIR) as a percentage of egress port bandwidth
•Committed Information Rate (CIR) as a percentage of egress port bandwidth
Network queue policies are identified with a unique policy name which conforms to the standard
router alphanumeric naming conventions.
7950 XRS Quality of Service GuidePage 27
QoS Policies
The system default network queue policy is named default and cannot be edited or deleted.
Table 5 describes the default network queue policy definition.
This section describes the queue parameters provisioned on access and queues for QoS.
The queue parameters are:
•Queue ID on page 30
•Queue Hardware Scheduler on page 30
•Committed Information Rate on page 31
•Peak Information Rate on page 32
•Adaptation Rule on page 33
•Committed Burst Size on page 35
•Maximum Burst Size on page 35
•High-Priority Only Buffers on page 35
•Packet Markings on page 36
•Queue-Types on page 37
Queue ID
The queue ID is used to uniquely identify the queue. The queue ID is only unique within the
context of the QoS policy within which the queue is defined.
Queue Hardware Scheduler
The hardware scheduler for a queue dictates how it will be scheduled relative to other queues at
the hardware level. When a queue is defined in a service ingress or service egress QoS policy, it is
possible to explicitly define the hardware scheduler to use for the queue when it is applied to a
SAP.
Being able to define a hardware scheduler is important as a single queue allows support for
multiple forwarding classes. The default behavior is to automatically choose the expedited or nonexpedited nature of the queue based on the forwarding classes mapped to it. As long as all
forwarding classes mapped to the queue are expedited (nc, ef, h1 or h2), the queue will be treated
as an expedited queue by the hardware schedulers. When any non-expedited forwarding classes
are mapped to the queue (be, af, l1 or l2), the queue will be treated as best effort by the hardware
schedulers.
Page 307950 XRS Quality of Service Guide
Loading...
+ 582 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.