Download Print this page

Alcatel-Lucent 7950 Quality Of Service Manual

Extensible routing system

Hide thumbs Also See for 7950:

Quality of service manual (912 pages)

,

Configuration manual (778 pages)

,

Basic system configuration manual (576 pages)

Table Of Contents

page of 612

/ 612
Contents
Table of Contents
Bookmarks

Table of Contents

Advertisement

Quick Links

Download this manual See also: Configuration Manual

QUALITY OF SERVICE GUIDE

Alcatel-Lucent 7950

EXTENSIBLE ROUTING SYSTEM | RELEASE 13.0.R1

QUALITY OF SERVICE GUIDE

Alcatel-Lucent – Proprietary & Confidential

Contains proprietary/trade secret information which is the property of Alcatel-Lucent. Not to be made available

to, or copied or used by anyone who is not an employee of Alcatel-Lucent except when there is a valid non-

disclosure agreement in place which covers such information and contains appropriate non-disclosure and

limited use obligations.

Copyright 2015 © Alcatel-Lucent. All rights reserved.

Table of Contents

Advertisement

Table of Contents

Need help?

Need help?

Do you have a question about the 7950 and is the answer not in the manual?

Questions and answers

Summary of Contents for Alcatel-Lucent 7950

Page 1 Contains proprietary/trade secret information which is the property of Alcatel-Lucent. Not to be made available to, or copied or used by anyone who is not an employee of Alcatel-Lucent except when there is a valid non- disclosure agreement in place which covers such information and contains appropriate non-disclosure and limited use obligations.
Page 2 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.
Page 3: Table Of Contents
Alcatel-Lucent Services Configuration Process ........
Page 4 Service SAP QoS Policy Command Reference ..........165 Page 4 7950 XRS Quality of Service Guide...
Page 5 Command Hierarchies .............363 7950 XRS Quality of Service Guide...
Page 6 Command Hierarchies .............489 Page 6 7950 XRS Quality of Service Guide...
Page 7 Egress Policer CIR Packet Handling without Profile Capped Mode ......589 7950 XRS Quality of Service Guide...
Page 8 ........... . .603 Page 8 7950 XRS Quality of Service Guide...
Page 9 Table 32: Show QoS Scheduler-Stats Customer Output Fields ........514 7950 XRS Quality of Service Guide...
Page 10 Table 37: Effect of Profile-Capped Mode on CIR Output........583 Page 10 7950 XRS Quality of Service Guide...
Page 11 Figure 27: Egress Policer Threshold Determination and Output Behavior ......591 7950 XRS Quality of Service Guide...
Page 12 List of Figures Page 12 7950 XRS Quality of Service Guide...
Page 13: Preface
It is assumed that the network administrators have an understanding of networking 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 Guide Page 13...
Page 14: List Of Technical Publications
• 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 14 7950 XRS Quality of Service Guide...
Page 15: 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 Alcatel- Lucent support representative and to access product manuals and documentation updates: http://support.alcatel-lucent.com...
Page 16 Preface Page 16 7950 XRS Quality of Service Guide...
Page 17: Getting Started
Getting Started In This Chapter This chapter provides process flow information to configure Quality of Service (QoS) policies and provision services. 7950 XRS Quality of Service Guide Page 17...
Page 18: Alcatel-Lucent Services Configuration Process
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. Page 18 7950 XRS Quality of Service Guide...
Page 19: Qos Policies
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 Guide Page 19...
Page 20: Qos Overview
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 7450 ESS) appear like a Layer 2 path to the service data although it is really traversing an IP or IP/ MPLS core.
Page 21: Qos Policies
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 Guide Page 21...
Page 22: Qos Policies
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 22 7950 XRS Quality of Service Guide...
Page 23: Table 2: Qos Policy Types And Descriptions
• Defines the hierarchy and parameters for each scheduler. service site • Defined in the context of a tier which is used to place the Service SAP scheduler within the hierarchy. • Three tiers of virtual schedulers are supported. 7950 XRS Quality of Service Guide Page 23...
Page 24: Service And Network Qos Policies
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 24 7950 XRS Quality of Service Guide...
Page 25: Network Qos Policies
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. 7950 XRS Quality of Service Guide Page 25...
Page 26: Table 3: Default Network Qos Policy Egress Marking
Forwarding Class dscp-name dscp-value FC ID Name Label Profile (binary - decimal) State Best-Effort Default 101110 - 46 Expedited 110000 - 48 High-1 111000 - 56 Network Control af11 001010 - 10 Assured Page 26 7950 XRS Quality of Service Guide...
Page 27: Network Queue Qos Policies
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 Guide Page 27...
Page 28: Table 5: Default Network Queue Policy Definition
• CBS = 3% • High-Prio-Only = 10% Assured (af) Queue 3 • PIR = 100% • CIR = 25% • MBS = 50% • CBS = 10% • High-Prio-Only = 10% Page 28 7950 XRS Quality of Service Guide...
Page 29 • CBS = 3% • High-Prio-Only = 10% Best-Effort (be) Queue 1 • PIR = 100% • CIR = 0% • MBS = 50% • CBS = 1% • High-Prio-Only = 10% 7950 XRS Quality of Service Guide Page 29...
Page 30: Queue Parameters
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 30 7950 XRS Quality of Service Guide...
Page 31 The CIR for network queues are defined within network queue policies based on the forwarding class. The CIR for the queues for the forwarding class are defined as a percentage of the network interface bandwidth. 7950 XRS Quality of Service Guide Page 31...
Page 32 The user has some control over how the administrative PIR is converted to an operational PIR should the hardware not support the exact CIR and PIR values specified. The interpretation of the administrative PIR is discussed below in Adaptation Rule on page 33 Page 32 7950 XRS Quality of Service Guide...
Page 33 Rates greater than the above (capped) rates are only relevant when configured on a queue which is part of a distributed or port-fair mode LAG spanning multiple FPs. 7950 XRS Quality of Service Guide Page 33...
Page 34 Note that due to the changes in this implementation, there may be small differences in the resulting rates, MBS and CBS compared to the previous implementation. This is supported on FP2- and higher-based hardware but is not applicable to the HS-MDA. Page 34 7950 XRS Quality of Service Guide...
Page 35 High priority traffic is specified in the match criteria for the policy. On service egress, the HP-only reservation for a queue is defined in the service egress QoS policy. Service egress queues are specified by forwarding class. High-priority traffic for a given traffic 7950 XRS Quality of Service Guide Page 35...
Page 36 Expedited and Best Effort queues above the CIR (exceed) For access ingress, the CIR controls both dynamic scheduling priority and marking threshold. At network ingress, the queue’s CIR affects the scheduling priority but does not provide a profile Page 36 7950 XRS Quality of Service Guide...
Page 37 An internal mechanism that provides access rules when the queue is vying for bandwidth with queues in other virtual schedulers is also needed. 7950 XRS Quality of Service Guide Page 37...
Page 38: Service Ingress Qos Policies
These queues exist within the definition of the policy. The queues only get instantiated in hardware when the policy is applied to a SAP. In the case where the service does not have multipoint traffic, the multipoint queues will not be instantiated. Page 38 7950 XRS Quality of Service Guide...
Page 39 The sub-class is only used as a SAP ingress QoS classification tool, the sub-class association is lost once ingress QoS processing is finished. 7950 XRS Quality of Service Guide Page 39...
Page 40: Table 6: Forwarding Class And Enqueuing Priority Classification Hierarchy Based On Rule Type
Other- parameter is high or low. explicitly defined. Each packet can wise, preserve from the Otherwise, preserve from only match a single prec rule. previous match. the previous match Page 40 7950 XRS Quality of Service Guide...
Page 41 The entries are evaluated in numerical order based on the entry ID from the lowest to highest ID value. The first entry that matches all match criteria has its action performed. Table 7 Table 8 list the supported IP and MAC match criteria. 7950 XRS Quality of Service Guide Page 41...
Page 42: Table 7: Service Ingress Qos Policy Ip Match Criteria
MAC and IEEE 802.1p value are compared. The other Ethernet frame types match those field values in addition to fields specific to the frame format. Table 10 lists the criteria that can be matched for the various MAC frame types. Page 42 7950 XRS Quality of Service Guide...
Page 43: Table 10: Mac Match Criteria Frame Type Dependencies
• MBS, CBS and HP Only = default (values derived from applica- ble policy) Flows Default Forwarding 1 (one) flow defined for all traffic: Class • All traffic mapped to best-effort (be) with a low priority 7950 XRS Quality of Service Guide Page 43...
Page 44: Egress Forwarding Class Override
Service Egress QoS Policies Service egress queues are implemented at the transition from the service core network to the service access network. The advantages of per-service queuing before transmission into the access network are: Page 44 7950 XRS Quality of Service Guide...
Page 45 The default access egress policy is applied to all SAPs service egress policy explicitly assigned. The characteristics of the default policy are listed in the following table. 7950 XRS Quality of Service Guide Page 45...
Page 46 (network, access). Node-level pools are used by ingress network queues. A single ingress network pool is created at the node-level for ingress network queues. Page 46 7950 XRS Quality of Service Guide...
Page 47 4. A random number is generated associated with the packet and is compared to the discard probability. 5. The lower the discard probability, the lower the chances are that the random number is within the discard range. 7950 XRS Quality of Service Guide Page 47...
Page 48: Figure 3: Red Slope Characteristics
0 and start-avg. 2. Section B is (start-avg, 0) to (max-avg, max-prob). This part of the slope describes a linear slope where packet discard probability increases from zero to max-prob. Page 48 7950 XRS Quality of Service Guide...
Page 49 0 to 1. Changing the values for start-avg, max-avg and max-prob allows the adaptation of the RED slope to the needs of the access or network queues using the shared portion of the buffer pool, including disabling the RED slope. 7950 XRS Quality of Service Guide Page 49...
Page 50: Table 12: Taf Impact On Shared Buffer Average Utilization Calculation
Table 12: TAF Impact on Shared Buffer Average Utilization Calculation Equates Shared Buffer Shared Buffer Average Instantaneous Utilization Portion Utilization Portion 1/1 (1) 0 (0) 1/2 (0.5) 1/2 (0.5) 1/4 (0.25) 3/4 (0.75) 1/8 (0.125) 7/8 (0.875) 1/16 (0.0625) 15/16 (0.9375) Page 50 7950 XRS Quality of Service Guide...
Page 51 The TAF value applies to all high and low priority RED slopes for ingress and egress buffer pools controlled by the buffer policy. 7950 XRS Quality of Service Guide Page 51...
Page 52: Policy Parameters
High (RED) slope Administrative state Shutdown start-avg 70% utilization max-avg 90% utilization max-prob 80% probability Low (RED) slope Administrative state Shutdown start-avg 50% utilization max-avg 75% utilization max-prob 80% probability Time average factor Page 52 7950 XRS Quality of Service Guide...
Page 53: Table 14: Default Slope Policy Definition
High (RED) slope Administrative state Shutdown start-avg 70% utilization max-avg 90% utilization max-prob 80% probability Low (RED) slope Administrative state Shutdown start-avg 50% utilization max-avg 75% utilization max-prob 80% probability Time average factor 7950 XRS Quality of Service Guide Page 53...
Page 54: Scheduler Policies
Level parameter (L8 through L1 weighted loops). The weighting at each level loop is defined by the weight parameter for each child. Page 54 7950 XRS Quality of Service Guide...
Page 55: Figure 4: Virtual Scheduler Internal Bandwidth Allocation
Child When Multiple Children Are Mapped to Same Above CIR Loop Legend Prioritizing Loop (Weighted or Strict) Maximum and Committed Rate Parameters Bandwidth Dependency Association Bandwidth Allocation al_0188 Figure 4: Virtual Scheduler Internal Bandwidth Allocation 7950 XRS Quality of Service Guide Page 55...
Page 56: Table 15: Supported Scheduler Policies
The type of scheduling available for the various scheduling points within the system are summarized in Table Table 15: Supported Scheduler Policies Scheduling From Single-Tier Hierarchical Service Egress Queues Access Egress Ports Network Egress Queues Network Egress Interfaces Page 56 7950 XRS Quality of Service Guide...
Page 57 Information Rate (PIR). Queue’s operating within their CIR values are serviced before queue’s operating above their CIR values with “high-priority” forwarding class queues given preference over “low-priority” forwarding class queues. In Single Tier Scheduling, all queues are treated as if 7950 XRS Quality of Service Guide Page 57...
Page 58: Table 16: Forwarding Class Scheduler Mapping
Other parameters can be modified to configure the appropriate QoS behavior. Page 58 7950 XRS Quality of Service Guide...
Page 59 (also called root schedulers) are defined without a parent scheduler. It is not necessary for Tier 1 schedulers to obtain bandwidth from a higher tier scheduler. A scheduler can enforce a maximum rate of operation for all child queues and associated schedulers. 7950 XRS Quality of Service Guide Page 59...
Page 60: Figure 5: Hierarchical Scheduler And Queue Association
Weighted Rate Limiting Scheduler Queue Weighted Rate Limiting Scheduler Queue Weighted Rate Limiting Scheduler Queue Weighted Rate Limiting Scheduler Queue Weighted Rate Limiting Scheduler Queue Figure 5: Hierarchical Scheduler and Queue Association Page 60 7950 XRS Quality of Service Guide...
Page 61: Figure 6: Scheduler Policy On Sap And Scheduler Hierarchy Creation
Queue Weighted Rate Limiting Packet Scheduler Packet Forwarding Weighted Packet Class Rate Limiting Scheduler Service Queue Forwarding Weighted Class Rate Limiting Scheduler Figure 6: Scheduler Policy on SAP and Scheduler Hierarchy Creation 7950 XRS Quality of Service Guide Page 61...
Page 62: Figure 7: Scheduler Policy On Customer Site And Scheduler Hierarchy Creation
Queues are associated with the configured schedulers by specifying the parent scheduler defined within the queue definition from the SAP egress policy. The scheduler is used to provide bandwidth to the queue relative to the operating constraints imposed by the scheduler hierarchy. Page 62 7950 XRS Quality of Service Guide...
Page 63 SAPs owned by the customer must be explicitly included in the site. The SAP must be owned by the customer the site was created within and the site assignment parameter must include the physical locale of the SAP. 7950 XRS Quality of Service Guide Page 63...
Page 64: Forwarding Classes
Network QoS Policies on page 25. All forwarding class queues support the concept of in-profile and out-of-profile. Page 64 7950 XRS Quality of Service Guide...
Page 65: High-Priority Classes
AF1 the lowest. The Assured and Low 1 classes are differentiated based on the default DSCP mappings. Note that all DSCP and EXP mappings can be modified by the user. 7950 XRS Quality of Service Guide Page 65...
Page 66: Best-Effort Classes
The best-effort classes are Low 2 (l2) and Best-Effort (be). The best-effort forwarding classes have no delivery guarantees. All packets within this class are treated, at best, like out-of-profile assured service packets. Page 66 7950 XRS Quality of Service Guide...
Page 67: Qos Policy Entities
(Best Effort (be) forwarding class) and an equal chance of being dropped during periods of congestion. QoS prioritizes traffic according to the forwarding class and uses congestion management to control access ingress, access egress, and network traffic with queuing according to priority 7950 XRS Quality of Service Guide Page 67...
Page 68: Frequently Used Qos Terms
A child’s (queue or scheduler) CIR is used with the CIR level parameter to determine the child’s committed bandwidth from the parent scheduler. When multiple children are at the same strict CIR level, the CIR weight further determines the bandwidth distribution at that level. Page 68 7950 XRS Quality of Service Guide...
Page 69 It is separated into two portions; within CIR and above CIR. Within CIR offered load is the portion of bandwidth required to meet the child’s CIR value. It can be less than the CIR value but never 7950 XRS Quality of Service Guide Page 69...
Page 70 Any scheduler can be a root scheduler. Since parent associations are not allowed in Tier 1, all schedulers in Tier 1 are considered be a root scheduler. Page 70 7950 XRS Quality of Service Guide...
Page 71 CIR distribution phase. If the parent scheduler has any bandwidth remaining after the ‘within CIR’ distribution phase, it will be distributed using the above CIR distribution phase. 7950 XRS Quality of Service Guide Page 71...
Page 72: Configuration Notes
Associating a service or access ports with a QoS policy other than the default policy is optional. • A network queue, service egress, and service ingress QoS policy must consist of at least one queue. Queues define the forwarding class, CIR, and PIR associated with the queue. Page 72 7950 XRS Quality of Service Guide...
Page 73: Network Qos Policies
Topics in this section include: • Overview on page 74 • Basic Configurations on page 77 • Default Network Policy Values on page 78 • Service Management Tasks on page 79 7950 XRS Quality of Service Guide Page 73...
Page 74: Overview
CLI Usage chapter in the Basic System Configuration Guide. Normal QoS Operation The following types of QoS mapping decisions are applicable on a network ingress IP interface. • value mapping (if defined) • Default QoS mapping Page 74 7950 XRS Quality of Service Guide...
Page 75: Dscp Marking Cpu Generated Traffic
Management protocols (SSH, SNMP, etc) → Forwarding class: Assured Forwarding (AF) → DSCP value: AF41 NOTE: The ICMP entry under sgt-qos is not referenced for ICMP ECHO_REQUEST (8) and ECHO_RESPONSE (0) packet types. 7950 XRS Quality of Service Guide Page 75...
Page 76: Default Dscp Mapping Table
0x1d 0b011110 af41 0x22 0b100010 af42 0x24 0b100100 af43 0x26 0b100110 default* *The default forwarding class mapping is used for all DSCP names/values for which there is no explicit forwarding class mapping. Page 76 7950 XRS Quality of Service Guide...
Page 77: Basic Configurations
Ingress traffic that matches the specified bits will be assigned to the corresponding forwarding class. Use the following CLI syntax to create a network QoS policy: Network Egress Parameters CLI Syntax: config>qos# network network-policy-id description description-string scope {exclusive|template} egress remarking fc {be|l2|af|l1|h2|ef|h1|nc} 7950 XRS Quality of Service Guide Page 77...
Page 78: Default Network Policy Values
Default description Default network QoS policy. scope template ingress default-action fc be profile out egress remarking fc af: fc be: fc ef: fc h1: fc h2: fc l1: fc l2: fc nc: Page 78 7950 XRS Quality of Service Guide...
Page 79: Service Management Tasks
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. 7950 XRS Quality of Service Guide Page 79...
Page 80: Remove A Policy From The Qos Configuration
600 create description "Default network QoS policy." scope template ingress default-action fc be profile out network 700 create description "Default network QoS policy." scope template ingress default-action fc be profile out --------------------------------------------- A:ALA-12>config>qos# Page 80 7950 XRS Quality of Service Guide...
Page 81: Editing Qos Policies
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. 7950 XRS Quality of Service Guide Page 81...
Page 82 Editing QoS Policies Page 82 7950 XRS Quality of Service Guide...
Page 83: In This Section
Topics in this section include: • Overview on page 84 • Basic Configurations on page 85 • Default Network Queue Policy Values on page 89 • Service Management Tasks on page 93 7950 XRS Quality of Service Guide Page 83...
Page 84: Overview
The default policy is identified as network-queue default. Default network queue policies are applied to MDA network ingress ports. You must explicitly create and then associate other network queue QoS policies. Page 84 7950 XRS Quality of Service Guide...
Page 85: Basic Configurations
50 cbs 3 high-prio-only 10 exit queue 3 create rate 100 cir 25 mbs 50 cbs 1 high-prio-only 10 exit queue 4 create rate 100 cir 25 mbs 25 cbs 3 7950 XRS Quality of Service Guide Page 85...
Page 86 1 high-prio-only 10 exit queue 13 multipoint create rate 100 cir 100 mbs 50 cbs 1 high-prio-only 10 exit queue 14 multipoint create rate 100 cir 100 mbs 50 cbs 1 Page 86 7950 XRS Quality of Service Guide...
Page 87: Network Queue Qos Policies
13 queue 5 exit fc l1 create multicast-queue 12 queue 4 exit fc l2 create multicast-queue 10 queue 2 exit fc nc create multicast-queue 16 queue 8 exit 7950 XRS Quality of Service Guide Page 87...
Page 88: Applying Network Queue Policies
Apply network queue policies to the following entities: • Ethernet Ports Ethernet Ports Use the following CLI syntax to apply a network queue policy to an Ethernet port. CLI Syntax: config>port# ethernet Page 88 7950 XRS Quality of Service Guide...
Page 89: Default Network Queue Policy Values
Network Queue QoS Policies Default Network Queue Policy Values The default network queue policies are identified as policy-id default The default policies cannot be modified or deleted. The following displays default policy parameters: 7950 XRS Quality of Service Guide Page 89...
Page 90 Applying Network Queue Policies Page 90 7950 XRS Quality of Service Guide...
Page 91: Network Ingress Ip Match Criteria
IP interface will result in an error. An example configuration is shown below: network 10 create ingress ip-criteria entry 10 create match dst-ip 10.0.0.1/32 exit action fc "h2" profile in exit exit 7950 XRS Quality of Service Guide Page 91...
Page 92: Network Ingress Ipv6 Match Criteria
IP interface will result in an error. An example configuration is shown below: network 10 create ingress ipv6-criteria entry 10 create match dst-ip 2001:db8:1000::1/128 exit action fc "ef" profile in exit exit exit Page 92 7950 XRS Quality of Service Guide...
Page 93: Service Management Tasks
When you remove a QoS policy, the policy association reverts to the default network-queue policy default. To delete a user-created network queue policy, enter the following commands: CLI Syntax: config>qos# no network-queue policy-name Example config>qos# no network-queue nq1 7950 XRS Quality of Service Guide Page 93...
Page 94: Copying And Overwriting Qos Policies
You can copy an existing network queue policy, rename it with a new policy ID name, or overwrite an existing network queue policy. The option must be specified or an error occurs if overwrite the destination policy ID exists. CLI Syntax: config>qos# copy network-queue source-policy-id dest-policy-id [overwrite] Page 94 7950 XRS Quality of Service Guide...
Page 95: Editing Qos Policies
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. 7950 XRS Quality of Service Guide Page 95...
Page 96 Editing QoS Policies Page 96 7950 XRS Quality of Service Guide...
Page 97: Network Queue Qos Policy Command Reference
[create] — adaptation-rule — no adaptation-rule — avg-frame-overheadavg-frame-overheadcbscbshigh-prio-onlyhigh-prio- onlymbsmbsport-parentport-parentrate — no rate Operational Commands config — qos — copy network-queue src-name dst-name [overwrite] Show Commands show — qos — network-queue [network-queue-policy-name] [detail] 7950 XRS Quality of Service Guide Page 97...
Page 98 Command Hierarchies Page 98 7950 XRS Quality of Service Guide...
Page 99 — A text string describing the entity. Allowed values are any string up to 80 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. 7950 XRS Quality of Service Guide Page 99...
Page 100: Network Queue Qos Policies
If overwrite is not specified, a mes- sage is generated saying that the destination policy ID exists. SR>config>qos# copy network-queue nq1 nq2 MINOR: CLI Destination "nq2" exists - use {overwrite}. SR>config>qos# copy network-queue nq1 nq2 overwrite Page 100 7950 XRS Quality of Service Guide...
Page 101 Valid names consist of any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. 7950 XRS Quality of Service Guide Page 101...
Page 102 — Defines the constraints enforced when adapting the CIR rate defined within the queue queue-id rate command. The cir parameter requires a qualifier that defines the Page 102 7950 XRS Quality of Service Guide...
Page 103 Fractional values are not allowed and must be given as a positive integer. The actual rate is dependent on the queue’s adaptation-rule parameters and the actual hardware where the queue is provisioned. Values 0 — 100 Default 7950 XRS Quality of Service Guide Page 103...
Page 104: Table 19: Network Queue Labels And Descriptions
A text string that helps identify the policy’s context in the configura- Description tion file. Displays the queue ID. Queue Displays the committed information rate. Displays the peak information rate. Displays the committed burst size. Displays FC to queue mapping. Page 104 7950 XRS Quality of Service Guide...
Page 105: Network Qos Policy Command Reference
— no fp-redirect-group broadcast-policer — fp-redirect-group policer policer-id — no fp-redirect-group policer — fp-redirect-group mcast-policer policer-id — no fp-redirect-group mcast-policer policer-id — fp-redirect-group unknown-policer policer-id — no fp-redirect-group unknown-policer — [no] ip-criteria 7950 XRS Quality of Service Guide Page 105...
Page 106 —dst-port {lt | gt | eq} dst-port-number —dst-port range start end —no dst-port —fragment {true|false|first-only|non-first-only} —no fragment —src-ip {ipv6-address/prefix-length | ipv6-address ipv6- address-mask} —no src-ip —src-port {lt | gt | eq} src-port-number Page 106 7950 XRS Quality of Service Guide...
Page 107 —no src-port start end — renum [old-entry-id new-entry-id] Operational Commands config — qos — copy network src-pol dst-pol [overwrite] Show Commands show — qos — network policy-id [detail] 7950 XRS Quality of Service Guide Page 107...
Page 108 Command Hierarchies Page 108 7950 XRS Quality of Service Guide...
Page 109 — A text string describing the entity. Allowed values are any string up to 80 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. 7950 XRS Quality of Service Guide Page 109...
Page 110 The system default policies cannot be put into the exclusive scope. An error will be generated if scope exclusive is executed in any policies with a policy-id equal to 1. Page 110 7950 XRS Quality of Service Guide...
Page 111 — When the scope of a policy is defined as template, the policy can be applied to multiple interfaces on the router. Default QoS policies are configured with template scopes. An error is generated if you try to modify the template scope parameter to exclusive scope on default policies. 7950 XRS Quality of Service Guide Page 111...
Page 112 (use the copy command) to create a new network policy that includes the default ingress DSCP-to-FC and MPLS EXP-to-FC mapping (as appropriate). You can modify parameters or use the no modifier to remove an object from the configuration. Page 112 7950 XRS Quality of Service Guide...
Page 113 The default network policy policy-id 1 cannot be deleted. Default System Default Network Policy 1 Parameters network-policy-id — The policy-id uniquely identifies the policy on the router. Default none Values 1— 65535 7950 XRS Quality of Service Guide Page 113...
Page 114 {in | out} — All packets that are assigned to this forwarding class will be considered in or out of profile based on this command. In case of congestion, the in-profile packets are preferentially queued over the out-of-profile packets. Default None Values in, out Page 114 7950 XRS Quality of Service Guide...
Page 115 The classification only applies to the outer IPv6 header of non-tunneled traffic. Attempting to apply a network QoS policy containing an ipv6-criteria statement to any object except a network IP interface will result in an error. 7950 XRS Quality of Service Guide Page 115...
Page 116 Inherit (When fc fc-name is not defined, the rule preserves the previous forwarding class of the packet.) profile {in | out} — The profile reclassification action is mandatory. Packets matching the IP flow reclassification entry will Page 116 7950 XRS Quality of Service Guide...
Page 117 This keyword is not required when the protection is disabled. The keyword is ignored when the flow entry already exists. 7950 XRS Quality of Service Guide Page 117...
Page 118 * — udp/tcp wildcard Page 118 7950 XRS Quality of Service Guide...
Page 119 * — udp/tcp wildcard dscp Syntax dscp dscp-name no dscp Context config>qos>network>ingress>ip-criteria>entry>match config>qos>network>ingress>ipv6-criteria>entry>match Description This command configures a DiffServ Code Point (DSCP) code point to be used as a network ingress QOS policy match criterion. 7950 XRS Quality of Service Guide Page 119...
Page 120 — 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 ip-address: a.b.c.d ipv6-address: 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 d: [0 — 255]D prefix-length: 1 — 128 Page 120 7950 XRS Quality of Service Guide...
Page 121 Configures a match on all non-fragmented IP packets. Non-fragmented IP packets are false — packets that have the MF bit set to zero and have the Fragment Offset field also set to zero. 7950 XRS Quality of Service Guide Page 121...
Page 122 No source IP match criterion. ip-address Specifies the source IPv4 address specified in dotted decimal notation. Values ip-address: a.b.c.d Specifies the length in bits of the subnet mask. mask Values 1 — 32 Page 122 7950 XRS Quality of Service Guide...
Page 123 1 — 65535 (decimal) range start end — The range of TCP or UDP port values to match specified as between the start and end source port values inclusive. Values 1 — 65535 (decimal) Values 7950 XRS Quality of Service Guide Page 123...
Page 124 The unknown-policer statement is ignored when the network QoS policy is applied to any object other than a VPLS spoke or mesh SDP or a network IP interface. The no version of this command removes the redirection of the FC. Page 124 7950 XRS Quality of Service Guide...
Page 125 All out-of-profile service packets are marked with the corresponding out-of-profile bit value at network egress. All the in-profile service ingress packets are marked with the corresponding in- profile bit value based on the forwarding class they belong. 7950 XRS Quality of Service Guide Page 125...
Page 126 Undefined forwarding classes default to the configured parameters in the default network policy policy-id 1. Parameters fc-name — The case-sensitive, system-defined forwarding class name for which policy entries will be created. Default none Values be, l2, af, l1, h2, ef, h1, nc Page 126 7950 XRS Quality of Service Guide...
Page 127 — The name of the DiffServ code point to be associated with the forwarding class. DiffServ code point can only be specified by its name and only an existing DiffServ code point can be specified. The software provides names for the well known code points. 7950 XRS Quality of Service Guide Page 127...
Page 128 — Specify the forwarding class name. All packets with DSCP value or MPLS EXP bits that is not defined will be placed in this forwarding class. Default None, the fc name must be specified Values be, l2, af, l1, h2, ef, h1, nc Page 128 7950 XRS Quality of Service Guide...
Page 129: Table 20: Show Qos Network Output Fields
Profile Out — on this forwarding class queue that are out of profile. In — Specifies that IP packets requiring marking the egress on this forwarding class queue that are in profile. 7950 XRS Quality of Service Guide Page 129...
Page 130 Bit Mapping: Displays the value used for out-of-profile traffic. Out-of-Profile Displays the value used for in-profile traffic. In-Profile Port-Id Specifies the physical port identifier that associates the interface. Page 130 7950 XRS Quality of Service Guide...
Page 131: Service Egress And Ingress Qos Policies
Egress SAP Forwarding Class and Forwarding Profile Overrides on page 133 → DEI Egress Remarking on page 134 → Default Service Egress and Egress Policy Values on page 141 • Basic Configurations on page 144 • Service Management Tasks on page 159 7950 XRS Quality of Service Guide Page 131...
Page 132: Overview
For information about the tasks and commands necessary to access the command line interface and to configure and maintain your router, refer to the CLI Usage chapter in the Basic System Configuration Guide. Page 132 7950 XRS Quality of Service Guide...
Page 133: Egress Sap Forwarding Class And Forwarding Profile Overrides
SAP on an IOM other than the IOM2 and IOM3 (such as an IOM1), no error message is generated, but the forwarding class and forwarding profile override portion of the SAP egress QoS Policy is ignored and has no effect. 7950 XRS Quality of Service Guide Page 133...
Page 134: Dei Egress Remarking
If qinq-mark-top- only is omitted, both the inner and outer VLAN tags are remarked. Note that the egress remarking occurs after any egress classification. Page 134 7950 XRS Quality of Service Guide...
Page 135: Dei In Ieee 802.1Ad
The ITAG header offers also an I-DEI bit that may be used to indicate the service drop eligibility associated with this frame. These bits must follow the same rules as described in DEI in IEEE 802.1ad on page 135. 7950 XRS Quality of Service Guide Page 135...
Page 136: Ieee 802.1Ad Use Case
802.1ad access provide proper DE indication by marking the new DE bit in the STAG. 7x50 PE1 7x50 PE2 802.1 a/d MPLS Access I-SAP (DE aware) Access Device Figure 9: DE Aware 802.1ad Access Network Page 136 7950 XRS Quality of Service Guide...
Page 137: Ieee 802.1Ah Use Case
The following commands can be used to remark the dot1p values at a SAP egress: CLI Syntax: sap-egress <policy-id> create fc <fc-name> create dot1p {<dot1p-value>|in-profile <dot1p-value> out- profile <dot1p-value>} dot1p-inner <dot1p-value> dot1p-inner in-profile <dot1p-value> out-profile <dot1p-value> dot1p-outer <dot1p-value> dot1p-outer in-profile <dot1p-value> out-profile 7950 XRS Quality of Service Guide Page 137...
Page 138 If qinq-mark-top- only is omitted, both the inner and outer VLAN tags are remarked. Note that the egress remarking occurs after any egress classification. Page 138 7950 XRS Quality of Service Guide...
Page 139: Implementation Requirements
SDP Egress SAP Egress Figure 11: DEI Processing Ingress into the PE1 SAP The following steps related to DEI are involved in the QoS processing as the packet moves from left to right: 7950 XRS Quality of Service Guide Page 139...
Page 140 A combination of two access networks can be possible. If PBB encapsulation is used, the configuration used for DE in SAP and SDP policies applies to both BVID and ITAG DE bits. When both fields are used the BVID takes precedence. Page 140 7950 XRS Quality of Service Guide...
Page 141: Default Service Egress And Egress Policy Values
Table 22: SAP Egress Policy Defaults Field Default description “Default SAP egress QoS policy.” scope template queue 1 1 auto-expedite parent no parent adaptation-rule adaptation-rule pir closest cir closest rate max cir 0 default default high-prio-only default 7950 XRS Quality of Service Guide Page 141...
Page 142: Default Sap Ingress Policy
0 default default high-prio-only default queue 2 multipoint priority-mode auto-expedite parent no parent adaptation-rule adaptation-rule pir closest cir closest rate max cir 0 Page 142 7950 XRS Quality of Service Guide...
Page 143 Service Egress and Ingress QoS Policies Table 23: SAP Ingress Policy Defaults (Continued) Field Default default default high-prio-only default default-fc default-priority 7950 XRS Quality of Service Guide Page 143...
Page 144: Basic Configurations
Configuring and applying QoS policies is optional. If no QoS policy is explicitly applied to a SAP or IP interface, a default QoS policy is applied. • Service Egress QoS Policy on page 145 • Service Ingress QoS Policy on page 149 Page 144 7950 XRS Quality of Service Guide...
Page 145: Service Egress Qos Policy
"SAP egress policy" queue 1 create exit queue 2 create exit queue 3 expedite create parent test1 exit fc af create queue 1 exit fc ef create queue 2 exit exit #------------------------------------------ A:ALA-7>config>qos# 7950 XRS Quality of Service Guide Page 145...
Page 146 "SAP egress policy" queue 1 create parent "scheduler-tier1" exit queue 2 create exit queue 3 expedite create parent "test1" exit fc af create queue 1 exit fc ef create exit exit ------------------------------------------------ A:ALA-7>config>qos# Page 146 7950 XRS Quality of Service Guide...
Page 147 SAP. The traffic could be classified based on its DSCP value and directed to policer 1 while the remainder of the customer’s traffic is processed using egress queue 1. This is shown jn Figure 7950 XRS Quality of Service Guide Page 147...
Page 148: Figure 12: Egress Sap
Figure 12: Egress SAP The configuration would be as follows: sap-egress 10 create queue 1 create exit policer 1 create exit ip-criteria entry 10 create match dscp ef exit action policer 1 exit exit exit Page 148 7950 XRS Quality of Service Guide...
Page 149: Service Ingress Qos Policy
Otherwise, the template scope enables the policy to be applied to multiple SAPs. The following displays an service ingress policy configuration: A:ALA-7>config>qos>sap-ingress# info ---------------------------------------------- sap-ingress 100 create description "Used on VPN sap" ---------------------------------------------- A:ALA-7>config>qos>sap-ingress# 7950 XRS Quality of Service Guide Page 149...
Page 150 17 create parent VPN_nc rate 100 cir 36 exit queue 20 multipoint create parent VPN_be rate 11000 exit queue 22 multipoint create parent VPN_priority rate 11000 exit queue 23 multipoint create parent VPN_reserved Page 150 7950 XRS Quality of Service Guide...
Page 151 25 multipoint create parent VPN_video rate 1500 cir 1500 exit queue 26 multipoint create parent VPN_voice rate 2500 cir 2500 exit queue 27 multipoint create parent VPN_nc rate 100 cir 36 exit #------------------------------------------ A:ALA-7>config>qos# 7950 XRS Quality of Service Guide Page 151...
Page 152 27 multicast-queue 27 unknown-queue 27 exit prec 0 fc be prec 2 fc af prec 3 fc ef prec 5 fc h1 prec 6 fc h2 prec 7 fc nc #------------------------------------------ A:ALA-7>config>qos# Page 152 7950 XRS Quality of Service Guide...
Page 153 6 src-ip 10.10.10.103/24 exit action fc af priority high exit entry 20 create description "Entry 20-FC-BE" match protocol 17 dst-port eq 255 exit no action exit exit exit #------------------------------------------ A:ALA-7>config>qos# 7950 XRS Quality of Service Guide Page 153...
Page 154 "QoS Policy Configuration" #------------------------------------------ sap-ingress 101 create mac-criteria entry 10 create description "Entry10-low prio" match dst-mac 04-67-ff-00-00-01 ff-ff-ff-ff-ff-ff dot1p 7 7 exit action fc be priority low exit exit exit #------------------------------------------ A:ALA-7>config>qos# Page 154 7950 XRS Quality of Service Guide...
Page 155: Figure 13: Ingress Criteria Classification Directly To Policer
The configuration would be as follows: sap-ingress 10 create queue 1 create exit queue 11 multipoint create exit policer 1 create exit mac-criteria entry 10 create match src-mac 00-xx-yy-00-00-00 ff-ff-ff-00-00-00 exit action policer 1 exit 7950 XRS Quality of Service Guide Page 155...
Page 156 Basic Configurations exit exit Page 156 7950 XRS Quality of Service Guide...
Page 157 11 multipoint create exit fc "af" create queue 2 exit fc "be" create queue 1 exit fc "ef" create queue 3 exit lsp-exp 0 fc "be" priority low lsp-exp 1 fc "af" priority high 7950 XRS Quality of Service Guide Page 157...
Page 158: Applying Service Ingress And Egress Policies
105 applied to the SAP. A:ALA-7>config>service# info ---------------------------------------------- ies 88 customer 8 vpn 88 create interface "Sector A" create sap 1/1/1.2.2 create ingress qos 100 exit egress qos 105 exit exit exit no shutdown exit ---------------------------------------------- Page 158 7950 XRS Quality of Service Guide...
Page 159: Service Management Tasks
A:ALA-7>config>qos# Remove a QoS Policy from Service SAP(s) The following service output examples show that the SAP service ingress reverted to policy-id “1” when the non-default policies were removed from the configuration. 7950 XRS Quality of Service Guide Page 159...
Page 160: Copying And Overwriting Qos Policies
"VPN_be" rate 11000 exit sap-ingress 200 create description "Used on VPN sap" queue 1 create exit queue 2 multipoint create exit queue 10 create parent "VPN_be" rate 11000 exit --------------------------------------------- A:ALA-7>config>qos# Page 160 7950 XRS Quality of Service Guide...
Page 161: Remove A Policy From The Qos Configuration
The configuration below gives an example of enabling the monitoring of the depth of queue 1 on an Epipe SAP. epipe 1 customer 1 create sap 1/2/1 create egress qos 10 queue-override queue 1 create monitor-depth exit exit exit exit 7950 XRS Quality of Service Guide Page 161...
Page 162 Page 162 7950 XRS Quality of Service Guide...
Page 163 Issuing a clear card will also clear this information. Note that packet drops caused at the pool level, rather than at the queue level, would result in lower queue depths being reported. 7950 XRS Quality of Service Guide Page 163...
Page 164 Queue Depth Monitoring Page 164 7950 XRS Quality of Service Guide...
Page 165: Service Sap Qos Policy Command Reference
[fp-redirect-group] — no multicast-policer — multicast-queue queue-id [group queue-group-name] — no multicast-queue — out-remark dscp dscp-name — out-remark prec ip-prec-value — no out-remark — profile {in | out} — no profile 7950 XRS Quality of Service Guide Page 165...
Page 166 [create] — no policer policer-id — adaptation-rule pir {max | min | closest}] [cir {max | min | closest}] — no adaptation-rule — adv-config-policy policy-name — no adv-config-policy — description description-string Page 166 7950 XRS Quality of Service Guide...
Page 167 — percent-rate pir-percent [cir cir-percent] [port-limit|local-limit] — percent-rate pir-percent police [port-limit|local-limit] — no percent-rate — rate pir-rate [cir cir-rate | police] — no rate — scope {exclusive | template} — no scope 7950 XRS Quality of Service Guide Page 167...
Page 168 [pir adaptation-rule] — no adaptation-rule — burst-limit size [bytes|kilobytes] — no burst-limit — {[0..2625][kilobytes] | [0..2688000]bytes | default } — no — rate pir-rate {max | kilobits-per-second} — no rate — slope-policy hsmda-slope-policy-name Page 168 7950 XRS Quality of Service Guide...
Page 169 — no dst-port — src-ip {ipv6-address/prefix-length} — no src-ip — src-port {lt|gt|cq} dst-port-number — src-port range start end — no src-port — renum old-entry-number new-entry-number — parent-location {default|sla} 7950 XRS Quality of Service Guide Page 169...
Page 170 — size [bytes | kilobytes] — no — parent scheduler-name [weight weight] [level level] [cir-weight cir-weight] [cir-level cir-level] — no parent — percent-rate pir-percent [cir cir-percent] [port-limit | local-limit] — no percent-rate Page 170 7950 XRS Quality of Service Guide...
Page 171 {exclusive | template} — no scope config — qos — match-list — ip-prefix-list ip-prefix-list-name [create] — no ip-prefix-list ip-prefix-list-name — description string — no description — prefix ip-prefix/prefix-length — no prefix ip-prefix/prefix-length 7950 XRS Quality of Service Guide Page 171...
Page 172 Command Hierarchies Operational Commands config — qos — copy sap-egress src-pol dst-pol [overwrite] — copy sap-ingress src-pol dst-pol [overwrite] Show Commands show — qos — sap-ingress policy-id [detail] Page 172 7950 XRS Quality of Service Guide...
Page 173 — A text string describing the entity. Allowed values are any string up to 80 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. 7950 XRS Quality of Service Guide Page 173...
Page 174 This can be required in some cases since the router exits when the first match is found and executes the actions in accordance with the accompanying action command. This requires that entries be sequenced Page 174 7950 XRS Quality of Service Guide...
Page 175 — Enter the entry number of an existing entry. Default none Values 1 — 65535 new-entry-number — Enter the new entry-number to be assigned to the old entry. Default none Values 1 — 65535 7950 XRS Quality of Service Guide Page 175...
Page 176 The no sap-ingress policy-id command deletes the SAP ingress policy. A policy cannot be deleted until it is removed from all services where it is applied. The system default SAP ingress policy is a special case; the no command restores the factory defaults to policy-id 1. Page 176 7950 XRS Quality of Service Guide...
Page 177 — When the scope of a policy is defined as exclusive, the policy can only be applied to one SAP. If a policy with an exclusive scope is assigned to a second SAP an error message is generated. If the 7950 XRS Quality of Service Guide Page 177...
Page 178 (the parent forwarding class for the sub-class) as the forwarding class. Values class[.sub-class] class: be, l2, af, l1, h2, ef, h1, nc sub-class: 29 characters max Default None (Each sub-class-name must be explicitly defined) Page 178 7950 XRS Quality of Service Guide...
Page 179 Successfully creating a sub-class places the CLI within the context of the sub-class for further sub-class parameter definitions. Within the sub-class context, commands may be executed that define sub-class 7950 XRS Quality of Service Guide Page 179...
Page 180 Specifying the fc-name is optional. When a packet matches the rule, the forwarding class is only overridden when the fc fc-name parameter is defined on the rule. If the packet matches and the Page 180 7950 XRS Quality of Service Guide...
Page 181 The no form of the command removes the specified the dscp-names from the explicit DSCP classification rule in the SAP ingress policy. As dscp-names are removed, the system repacks the lists of dscp-names with 7950 XRS Quality of Service Guide Page 181...
Page 182 0100 1100 af22 0101 0000 cp21 0101 0100 af23 0101 1000 cp23 0101 1100 0110 0000 cp25 0110 0100 af31 0110 1000 cp27 0110 1100 af32 0111 0000 cp29 0111 0100 Page 182 7950 XRS Quality of Service Guide...
Page 183 29 characters max Default Inherit (When fc fc-name is not defined, the rule preserves the previous forwarding class of the packet.) 7950 XRS Quality of Service Guide Page 183...
Page 184 Matching a DSCP based reclassification rule will override all IP precedence based reclassification rule actions. The IP DSCP bits used to match against dscp reclassification rules come from the Type of Service (ToS) Page 184 7950 XRS Quality of Service Guide...
Page 185 Any dscp-names in the list before the failed entry will be processed as normal but the processing will stop at the failed entry so that the remainder of the list is not processed. 7950 XRS Quality of Service Guide Page 185...
Page 186 1000 1100 af42 1001 0000 cp37 1001 0100 af43 1001 1000 cp39 1001 1100 1010 0000 cp41 1010 0100 cp42 1010 1000 cp43 1010 1100 cp44 1011 0000 cp45 1011 0100 1011 1000 Page 186 7950 XRS Quality of Service Guide...
Page 187 This value may be overwritten by an explicit profile action in an ip-criteria reclassification match. 7950 XRS Quality of Service Guide Page 187...
Page 188 The no form of this command deletes all the entries specified under this node. Once IP criteria entries are removed from a SAP ingress policy, the IP criteria is removed from all services where that policy is applied. Page 188 7950 XRS Quality of Service Guide...
Page 189 If the command is executed multiple times with the same lsp-exp-value, the previous forwarding class and enqueuing priority is completely overridden by the new parameters or defined to be inherited when a forwarding class or enqueuing priority parameter is missing. 7950 XRS Quality of Service Guide Page 189...
Page 190 For this reason entries must be sequenced correctly from most to least explicit. The no form of this command deletes all the entries specified under this node. Once mac-criteria entries are Page 190 7950 XRS Quality of Service Guide...
Page 191 ID will be created (depending on the system's current create keyword requirements which may require the create keyword to actually add the new policer ID to the QoS policy) and the system will enter that new policer’s context for possible parameter modification. Values 1—63 7950 XRS Quality of Service Guide Page 191...
Page 192 Valid names consist of any string up to 63 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. Page 192 7950 XRS Quality of Service Guide...
Page 193 — The max keyword is used to inform the system that the profiling rate defined for the policer is the maximum allowed rate. The system will choose a hardware supported rate that is closest but not exceeding the specified rate. 7950 XRS Quality of Service Guide Page 193...
Page 194 — When byte is defined, the value given for size is interpreted as the queue’s MBS value given in bytes. kilobyte — When kilobytes is defined, the value is interpreted as the queue’s MBS value given in kilobytes. Values 0 – 16777216 or default Default kilobyte Page 194 7950 XRS Quality of Service Guide...
Page 195 The no form of this command returns the policer to its default MBS size. Default 64 kilobytes when PIR = max, otherwise, 10ms volume of traffic for a configured non zero/non max PIR. 7950 XRS Quality of Service Guide Page 195...
Page 196 When subtract is defined, the corresponding bytes parameter specifies the number of bytes that is subtracted from the size of each packet associated with the policer for rate metering, profiling and accounting purposes. From the policer’s perspective, the maximum packet size Page 196 7950 XRS Quality of Service Guide...
Page 197 (policers or other arbiters) for bandwidth. The no form of this command is used to remove the parent association from all instances of the policer. 7950 XRS Quality of Service Guide Page 197...
Page 198 The no form of this command returns the queue to its default shaping rate and cir rate. Parameters pir-percent — Specifies the policer’s PIR as a percentage of the immediate parent root policer/arbiter rate or the FP capacity. Values Percentage ranging from 0.01 to 100.00. Default 100.00 Page 198 7950 XRS Quality of Service Guide...
Page 199 This command specifies whether to preserve the color of offered out-of-profile traffic at sap-egress policer (profility of the packet can change based on egress CIR state). When enabled, traffic determined as out-of-profile at ingress policer will be treated as out-of-profile at sap- egress policer. 7950 XRS Quality of Service Guide Page 199...
Page 200 The integer value is multiplied by 1,000 to derive the actual rate in bits-per-second. When max is specified, the maximum policer rate Page 200 7950 XRS Quality of Service Guide...
Page 201 The no form of this command attempts to return the policer’s stat-mode setting to minimal. The command will fail if insufficient policer counter resources exist to implement minimal where the QoS policer is currently applied and has a forwarding class mapping. no-stats — Counter resource allocation:0 7950 XRS Quality of Service Guide Page 201...
Page 202 Counter 0 indicates that the accounting statistic returns a value of zero. With minimal enabled as the policer stat-mode, the SAP offered stats for the policer returned via MIB query and CLI show commands will return the following values: i. offered-in ii. offered-out Page 202 7950 XRS Quality of Service Guide...
Page 203 Counter 0 indicates that the SAP policer statistic returns a value of zero. offered-priority-no-cir — Counter resource allocation:2 The offered-priority-no-cir mode allocates two forwarding plane offered counters and two traffic manager discard counters. 7950 XRS Quality of Service Guide Page 203...
Page 204 This mode does not prevent the policer from receiving trusted in-profile packets. The counters are used in the following manner: 1. offered-undefined-that-turned-green = profile in, priority high/low 2. offered-undefined-that-turned-yellow-or-red = priority high/low 3. offered-out-that-stayed-yellow-or-turned-red = profile out Page 204 7950 XRS Quality of Service Guide...
Page 205 The counters are used in the following manner: 1. offered-in-that-stayed-green-or-turned-red = profile in 2. offered-undefined-that-turned-green = priority high/low 3. offered-undefined-that-turned-yellow-or-red = priority high/low 4. offered-out-that-stayed-yellow-or-turned-red = profile out 5. dropped-in-that-stayed-green-or-turned-red = Same as 1 7950 XRS Quality of Service Guide Page 205...
Page 206 2. offered-high-that-turned-yellow-or-red = profile in, priority high 3. offered-low-that-turned-green = profile out, priority low 4. offered-low-that-turned-yellow-or-red = profile out, priority low 5. dropped-high-that-turned-green = Same as 1 6. dropped-high-that-turned-yellow-or-red = Same as 2 Page 206 7950 XRS Quality of Service Guide...
Page 207 = profile in/out, priority high/low 3. dropped-offered-that-turned-green = Same as 1 4. dropped-offered-that-turned-yellow-or-red = Same as 2 5. forwarded-offered-that-turned-green = Derived from 1 - 3 6. forwarded-offered-that-turned-yellow = Derived from 2 - 4 7950 XRS Quality of Service Guide Page 207...
Page 208 = soft-out-of-profile ‘offered-soft-out- that-turned-yellow-or-red’= soft-out-of-profile ‘offered-out-that-turned-yellow-or-red’ = profile out ‘dropped-in-that-stayed-green’ = Same as 1 ‘dropped-in-that-turned-yellow-or-red’ = Same as 2 ‘dropped-soft-out-that-turned-green’ = Same as 3 ‘dropped-soft-out-that-turned-yellow-or-red’= Same as 4 ‘dropped-out-that-turned-yellow-or-red’ = Same as 5 Page 208 7950 XRS Quality of Service Guide...
Page 209 = Same as 2 ‘dropped-out-that-turned-green’ = Same as 3 ‘dropped-out-that-turned-yellow-or-red’ = Same as 4 ‘forwarded-in-that-stayed-green’ = Derived from 1 - 5 ‘forwarded-in-that-turned-yellow’ = Derived from 2 - 6 ‘forwarded-out-that-turned-green’ = Derived from 3 - 7 7950 XRS Quality of Service Guide Page 209...
Page 210 A maximum of eight IP precedence rules are allowed on a single policy. Page 210 7950 XRS Quality of Service Guide...
Page 211 Syntax prec ip-prec-value fc fc-name [profile {in | out}] no prec ip-prec-value Context config>qos>sap-egress Description This command defines a specific IP precedence value that must be matched to perform the associated 7950 XRS Quality of Service Guide Page 211...
Page 212 This value may be overwritten by an explicit profile action in a higher priority dscp or ip-criteria reclassification match. Page 212 7950 XRS Quality of Service Guide...
Page 213 Any billing or statistical queries about a multipoint queue on a non-multipoint service returns zero values. Any queue parameter information requested about a multipoint queue on a non-multipoint service returns the queue parameters in the policy. Buffers will not be allocated for multipoint queues on non-multipoint 7950 XRS Quality of Service Guide Page 213...
Page 214 If you attempt to map forwarding class unicast traffic to a multipoint queue, an error is generated and no changes are made to the current unicast traffic queue mapping. Page 214 7950 XRS Quality of Service Guide...
Page 215 The queue’s pool association may only be removed by either re-executing the queue command without the pool keyword or by executing the no pool command within the queue’s CLI context. When the pool name is removed, the queue will be placed on the appropriate default pool. 7950 XRS Quality of Service Guide Page 215...
Page 216 All received DE=0 frames which are classified into this parent forwarding class or any of its sub-classes have their profile unchanged by enabling this option. That is the DE=0 frame profile could be undetermined Page 216 7950 XRS Quality of Service Guide...
Page 217 While the SAP ingress QoS policy may be applied to any SAP, the remarking functions are only enforced when the SAP is associated with an IP or subscriber interface (in an IES or 7950 XRS Quality of Service Guide Page 217...
Page 218 Default None (an explicit valid DSCP name must be specified) Page 218 7950 XRS Quality of Service Guide...
Page 219 This command is used in a SAP ingress QoS policy to define an explicit out-of-profile remark action for a forwarding class or sub-class. While the SAP ingress QoS policy may be applied to any SAP, the remarking 7950 XRS Quality of Service Guide Page 219...
Page 220 The following table shows the effect of the out-remark command on received SAP ingress packets. Within the out-of-profile IP packet’s ToS field, either the six DSCP bits or the three precedence bits are remarked. Page 220 7950 XRS Quality of Service Guide...
Page 221: Table 24: Out-Remark Command Effect
The out-remark command can be configured to either remark the DiffServ Code Point (DSCP) six bit value or the three Precedence bits. The prec parameter specifies that the matching packets Precedence bits should be overridden with the value represented by prec-value. 7950 XRS Quality of Service Guide Page 221...
Page 222 The queue may only be configured for profile-mode at the time the queue is created in the SAP ingress QoS policy. Page 222 7950 XRS Quality of Service Guide...
Page 223 When the policy is applied, all packets matching the forwarding class and forwarding type will be redirected to the queue within the specified queue group. The queue-group-name are configured in the config>qos>queue-group-tem- plates egress and ingress contexts. 7950 XRS Quality of Service Guide Page 223...
Page 224 This command enables the context to configure queue definitions for use on SAPs or subscribers on HSM- DAs. A single QoS policy simultaneously defines queues for both standard MDA and for HSMDA subscrib- Page 224 7950 XRS Quality of Service Guide...
Page 225: Queue Sharing And Redirection
As with standard queues, the explicit profile of a packet is dependant on ingress sub-forwarding class to which the packet is mapped. Queue sharing and redirection 7950 XRS Quality of Service Guide Page 225...
Page 226 IP based accounting function. Given a Dot1Q encapsulation, the command packet-byte- offset subtract 14 would remove the DLC header and the Dot1Q header from the size of each packet for Page 226 7950 XRS Quality of Service Guide...
Page 227 Description This command associates an existing HSMDA weighted-round-robin (WRR) scheduling loop policy to the HSMDA queue. Parameters wrr-policy-name — Specifies the existing HSMDA WRR policy name to associate to the queue. 7950 XRS Quality of Service Guide Page 227...
Page 228 Based on these classifications, packets are mapped to the RED slopes in the following manner: Ingress Slope Mapping • In-Profile — High Slope (priority ignored) Page 228 7950 XRS Quality of Service Guide...
Page 229 The no form of the command restores the association between the queue and the HSMDA default slope pol- icy. The command has no immediate effect for queues that have a local override defined for the slope policy. 7950 XRS Quality of Service Guide Page 229...
Page 230 Once a slope policy is associated with an HSMDA queue, the policy cannot be deleted. Default hsmda-default Page 230 7950 XRS Quality of Service Guide...
Page 231 -name, an error will occur. If sub-class-name is removed using the no fc fc-name.sub-class-name force command, the default-fc command will automatically drop the sub-class-name and only use fc-name (the parent forwarding class for the sub-class) as the forwarding class. 7950 XRS Quality of Service Guide Page 231...
Page 232 The default behavior for HSMDA queue accounting is to use the counters associated with the queue to which the packet is mapped. Matching an IP flow reclassification Page 232 7950 XRS Quality of Service Guide...
Page 233 The fc-name defined must be one of the eight forwarding classes supported by the system. To remove the forwarding class reclassification action for the IP flow entry, the action command must be re-executed without the fc reclassification action defined. 7950 XRS Quality of Service Guide Page 233...
Page 234 — This parameter overrides the policer’s default egress queue destination to a specified local SAP queue of that queue-id. A queue of ID queue-id must exist within the egress QoS policy. Values 1—8 Page 234 7950 XRS Quality of Service Guide...
Page 235 This keyword is not required when the protection is disabled. The keyword is ignored when the flow entry already exists. 7950 XRS Quality of Service Guide Page 235...
Page 236: Table 25: Ip Protocol Names
ISO Internet Protocol eigrp EIGRP ospf-igp OSPFIGP ether-ip Ethernet-within-IP Encapsulation encap Encapsulation Header pnni PNNI over IP l2tp Layer Two Tunneling Protocol Schedule Transfer Protocol Performance Transparency Protocol crtp Combat Radio Transport Protocol Page 236 7950 XRS Quality of Service Guide...
Page 237 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 will be executed. A match context can consist of multiple match criteria, but multiple match statements cannot be entered per entry. 7950 XRS Quality of Service Guide Page 237...
Page 238 802dot2-llc — Specifies the frame type is Ethernet IEEE 802.2 LLC. 802dot2-snap — Specifies the frame type is Ethernet IEEE 802.2 SNAP. ethernet_II — Specifies the frame type is Ethernet Type II. Page 238 7950 XRS Quality of Service Guide...
Page 239 HSMDA mappings from the standard mappings This allows the same QoS policy to be used on a standard MDA attached SAP and an HSMDA attached SAP. 7950 XRS Quality of Service Guide Page 239...
Page 240: Table 26: Default Fc Hsmda Queue Id Mappings
Table 27: Ingress HSMDA Queue Mapping Behavior Based on Forwarding Type Queue Mappings For Each Forwarding Type Service Type Queue Broadcast Multicast Unknown Epipe All packets matching None None None the FC Page 240 7950 XRS Quality of Service Guide...
Page 241 The low priority violate threshold provides a smaller burst size for the lower priority traffic associated with the 7950 XRS Quality of Service Guide Page 241...
Page 242 — Specify the length in bits of the subnet mask. Values 1 — 32 ipv4-address-mask — Specify the subnet mask in dotted decimal notation. Values a.b.c.d (dotted quad equivalent of mask length) Page 242 7950 XRS Quality of Service Guide...
Page 243 This command configures fragmented or non-fragmented IP packets as a SAP QoS policy match criterion. The no form of this command removes the match criterion and matches all packets regardless of whether they are fragmented or not. 7950 XRS Quality of Service Guide Page 243...
Page 244 To match on the source IPv4 or IPv6 address, specify the address and its associated mask, e.g. 10.1.0.0/16. The conventional notation of 10.1.0.0 255.255.0.0 can also be used for IPv4. The no form of the command removes the source IPv4 or IPv6 address match criterion. Page 244 7950 XRS Quality of Service Guide...
Page 245 | gt | eq src-port-number — The TCP or UDP port numbers to match specified as less than (lt), greater than (gt) or equal to (eq) to the source port value specified as a decimal integer. Values 1 — 65535 (decimal) 7950 XRS Quality of Service Guide Page 245...
Page 246 IP QoS Policy Match Commands range start end — The range of TCP or UDP port values to match specified as between the start and end source port values inclusive. Values 1 — 65535 (decimal) Page 246 7950 XRS Quality of Service Guide...
Page 247 The snap-pid field, etype field, ssap and dsap fields are mutually exclusive and cannot be part of the same match criteria. Use the no form of this command to remove the dsap value as the match criterion. 7950 XRS Quality of Service Guide Page 247...
Page 248 — A 48-bit mask to match a range of MAC address values. This 48-bit mask can be configured using the following formats: Format Style Format Syntax Example Decimal DDDDDDDDDDDDDD 281474959933440 Hexadecimal 0xHHHHHHHHHHHH 0xFFFFFF000000 Binary 0bBBBBBBB...B 0b11110000...B Page 248 7950 XRS Quality of Service Guide...
Page 249 — Specifies to match packets with the three-byte OUI field in the SNAP-ID set to zero. non-zero — Specifies to match packets with the three-byte OUI field in the SNAP-ID not set to zero. 7950 XRS Quality of Service Guide Page 249...
Page 250 HH:HH:HH:HH:HH:HH or HH-HH-HH-HH-HH-HH where H is a hexadecimal digit ieee-address-mask — This 48-bit mask can be configured using: This 48 bit mask can be configured using the following formats Format Style Format Syntax Example Decimal DDDDDDDDDDDDDD 281474959933440 Page 250 7950 XRS Quality of Service Guide...
Page 251 — This is optional and can be used when specifying a range of ssap values to use as the match criteria. This 8 bit mask can be configured using the following formats: Format Style Format Syntax Example Decimal Hexadecimal 0xHH 0xF0 Binary 0bBBBBBBBB 0b11110000 Default none Values 0x00 — 0xFF 7950 XRS Quality of Service Guide Page 251...
Page 252 When the sap-egress policy is applied to a SAP, the parent schedulers of the queues need to be configured in the scheduler-policy applied to the SAP or the multi-service site. Page 252 7950 XRS Quality of Service Guide...
Page 253 QoS policy is used instead of the default policer output queues. • If the policer policer-id port-redirect-group-queue keyword is successfully executed, the system will map the forwarding class to the queue within the egress queue group instance specified at the 7950 XRS Quality of Service Guide Page 253...
Page 254 The specific egress queue group instance to use is specified at the time that the QoS policy is applied to the SAP. Therefore, this parameter os only valid if SAP based redirection is required. Page 254 7950 XRS Quality of Service Guide...
Page 255 The description string can be up to 80 characters. If the string contains spaces, it must be placed within beginning and ending double quotation marks. Beginning and ending quotation marks are 7950 XRS Quality of Service Guide Page 255...
Page 256 — The min keyword is used to inform the system that the metering rate defined for the policer is the minimum allowed rate. The system will choose a hardware supported rate that is closest but not lower than the specified rate. Page 256 7950 XRS Quality of Service Guide...
Page 257 — When byte is defined, the value given for size is interpreted as the queue’s MBS value given in bytes. kilobyte — When kilobytes is defined, the value is interpreted as the queue’s MBS value given in kilobytes. Values 0 – 16777216 or default Default kilobyte 7950 XRS Quality of Service Guide Page 257...
Page 258 [bytes | kilobytes] — The size parameter is required when specifying mbs and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional Page 258 7950 XRS Quality of Service Guide...
Page 259 From the policer’s perspective, the maximum packet size is reduced by the amount being subtracted from the size of each packet. Note that the minimum resulting packet size used by the system is 1 byte. Values 1—64 Default None 7950 XRS Quality of Service Guide Page 259...
Page 260 — The root keyword specifies that the policer is intended to become a child to the root arbiter where an instance of the policer is created. If the root arbiter does not exist, the policer will be placed in the orphan state. Page 260 7950 XRS Quality of Service Guide...
Page 261 PIR leaky bucket. When the policer is first created, the metering rate defaults to max. The kilobits-per- 7950 XRS Quality of Service Guide Page 261...
Page 262 If insufficient counters exist to implement a mode on any policer instance, the stat-mode change will fail and the previous mode will continue unaffected for all instances of the policer. Page 262 7950 XRS Quality of Service Guide...
Page 263 = Same as 1 3. forwarded = Derived from 1 - 2 When collect-stats is enabled, the counters are used by the system to generate the following statistics: a. offered-in b. offered-out c. discard-in 7950 XRS Quality of Service Guide Page 263...
Page 264 CIR rate is being used to recolor the soft in-profile and out-of- profile packets. The counters are used in the following manner: 1. offered-in-that-stayed-green-or-turned-red = profile in 2. offered-soft-that-turned-green = soft-in-profile-out-of-profile 3. offered-soft-or-out-that-turned-yellow-or-red = soft-in-profile-out-of-profile, profile out 4. dropped-in-that-stayed-green-or-turned-red = Same as 1 Page 264 7950 XRS Quality of Service Guide...
Page 265 When collect-stats is enabled, the counters are used by the system to generate the following statistics: a. offered-in = 1 + 2 b. offered-out c. discard-in d. discard-out e. forward-in f. forward-out Counter 0 indicates that the accounting statistic returns a value of zero. 7950 XRS Quality of Service Guide Page 265...
Page 266 = 3 + 4 ‘offered-in’ = 1 + 2 ‘offered-out’ ‘discard-in’ = 6 + 8 ‘discard-out’ = 7 + 9 + 10 ‘forward-in’ = 11 + 13 ‘forward-out’ = 12 + 14 + 15 Page 266 7950 XRS Quality of Service Guide...
Page 267 When collect-stats is enabled, the counters are used by the system to generate the following statistics: ‘offered-in’ = 1 + 2 ‘offered-out’ = 3 + 4 ‘discard-in’ = 5 + 7 ‘discard-out’ = 6 + 8 ‘forward-in’ = 9 + 11 ‘forward-out’ = 10 + 12 7950 XRS Quality of Service Guide Page 267...
Page 268 A maximum of eight IP precedence rules are allowed on a single policy. Page 268 7950 XRS Quality of Service Guide...
Page 269 Policies in effect are templates that can be applied to multiple services as long as the scope of the policy is template. The queues defined in the policy are not instantiated until a policy is applied to a service. 7950 XRS Quality of Service Guide Page 269...
Page 270 Policy names may not begin with a number (0-9) or the underscore “_” character (e.g. _myPolicy). “Default” or “default” can not be used as policy names. Saved configurations and display output from the "info" Page 270 7950 XRS Quality of Service Guide...
Page 271 When the previous command (dot1p dot1p-value) is used without the new structure, it means that the dot1p- value is used for the entire forwarding class, same as before. The two versions of the command are mutually exclusive. 7950 XRS Quality of Service Guide Page 271...
Page 272 If no de-mark commands are used, the DE bit is preserved if an ingress inner tag exists, or set to zero otherwise. This command is only supported on FP2 and higher based hardware, and is otherwise ignored. Values 0 or 1 Page 272 7950 XRS Quality of Service Guide...
Page 273 This command takes precedence over the dot1p command if both are specified in the same policy and over the default action where the marking is taken from packet received at ingress. The configuration of qinq-mark-top-only under the SAP egress takes precedence over the use of the 7950 XRS Quality of Service Guide Page 273...
Page 274 The no form of the command sets the IEEE 802.1P or IEEE 802.1Q priority bits to 0. This command is supported on FP2 and higher based hardware, and is otherwise ignored. Default Page 274 7950 XRS Quality of Service Guide...
Page 275 This command creates a list of IPv4 prefixes for match criteria in QoS policies. An ip-prefix-list must contain only IPv4 address prefixes created using the prefix command and cannot be deleted if it is referenced by a QoS policy. 7950 XRS Quality of Service Guide Page 275...
Page 276 — A valid IPv4 address prefix in dotted decimal notation. Values 0.0.0.0 to 255.255.255.255 (host bit must be 0) prefix-length — Length of the entered IP prefix Values 1 — 32 Page 276 7950 XRS Quality of Service Guide...
Page 277 — The closest parameter is mutually exclusive with the min and max parameter. When closest is defined, the operational PIR for the queue will be the rate closest to the rate specified using the rate command. 7950 XRS Quality of Service Guide Page 277...
Page 278 Parameters default — The default parameter is mutually exclusive to specifying an explicit size value. When burst- limit default is executed, the queue is returned to the system default value. Page 278 7950 XRS Quality of Service Guide...
Page 279 — The kilobyte qualifier is used to specify that the value given for size must be interpreted as the burst limit in Kilobytes. The kilobyte qualifier is optional and mutually exclusive with the bytes qualifier. If neither bytes nor kilobytes is specified, the default qualifier is kilobytes. 7950 XRS Quality of Service Guide Page 279...
Page 280 The priority of a packet can only be set in the SAP ingress QoS policy and is only applicable on the ingress queues for a SAP. The high-prio-only parameter is used to override the default value derived from the Page 280 7950 XRS Quality of Service Guide...
Page 281 Values 0 — 131072 or default Minimum configurable non-zero value 1byte Minimum default value maximum of 10ms of PIR or 64Kbytes 7950 XRS Quality of Service Guide Page 281...
Page 282 Syntax packet-byte-offset {add bytes | subtract bytes} no packet-byte-offset Context config>qos>sap-ingress>queue Description This command is used to modify the size of each packet handled by the queue by adding or subtracting a Page 282 7950 XRS Quality of Service Guide...
Page 283 The queue will accept packets but will not be bandwidth limited by a virtual scheduler or the scheduler hierarchy applied to the SAP. The 7950 XRS Quality of Service Guide Page 283...
Page 284 Any queues or schedulers defined as strict receive no parental bandwidth until all strict queues and schedulers with a higher (numerically larger) priority on the parent have reached their maximum bandwidth or are idle. Page 284 7950 XRS Quality of Service Guide...
Page 285 If the cir-weight parameter is 1 or greater, the cir-level parameter comes into play. Values 0 — 8 (8 is the highest priority) Default 7950 XRS Quality of Service Guide Page 285...
Page 286 (including the ingress-rate/egress-rate setting) to which this queue connects. local-limit — The local-limit keyword specifies that the configure PIR and CIR percentages are relative to the rate of the queue’s parent scheduler rate or agg-rate rate at egress. Page 286 7950 XRS Quality of Service Guide...
Page 287 — Defines the weight the queue or scheduler will use at the within-cir port priority level (defined by the cir-level parameter). The weight is specified as an integer value from 0 to 100 with 7950 XRS Quality of Service Guide Page 287...
Page 288 PIR setting must be explicitly defined. When the rate command has not been executed, the default PIR of max is assumed. Fractional values are not allowed and must be given as a positive integer. Page 288 7950 XRS Quality of Service Guide...
Page 289 — Defines the administrative PIR rate, in kilobits, for the queue. When the rate command is executed, a valid PIR setting must be explicitly defined. When the rate command has not been 7950 XRS Quality of Service Guide Page 289...
Page 290 The size of the pool is the same as the size of the queue. In this manner, the WRED slopes that operate based on the pool’s buffer utilization are also reacting to the congestion depth of Page 290 7950 XRS Quality of Service Guide...
Page 291 The queue will be moved to either the default buffer pool or to a named pool if defined and the pool exists. Default no wred-queue Parameters policy slope-policy-name — Specifies an existing slope policy that is used to override the default WRED slope policy. 7950 XRS Quality of Service Guide Page 291...
Page 292 Specifies that a MAC criteria-based SAP is used to MAC — select the appropriate ingress queue and corresponding forward- ing class for matched traffic. Mode Specifies the configured mode of the meter (trTcm or srTcm). Page 292 7950 XRS Quality of Service Guide...
Page 293 Specifies the default CBS value for the queue. def — Specifies the value to override the default reserved value — buffers for the queue. Specifies the default MBS value. def — 7950 XRS Quality of Service Guide Page 293...
Page 294 Specifies one of the predefined forwarding classes in the system. When a packet matches the rule the forwarding class is only overridden when the fc fc-name parameter is defined on the rule. Page 294 7950 XRS Quality of Service Guide...
Page 295 Configures a match on all non-fragmented IP pack- False — ets. Specifies the entry’s forwarding class. Priority Specifies the default enqueuing priority overrides for all packets received on an ingress SAP using this policy. 7950 XRS Quality of Service Guide Page 295...
Page 296 Specifies the a Service Access Point (SAP) within the service where the SAP ingress policy is applied. sap-egress Syntax sap-egress [policy-id] [detail] Context show>qos Description This command displays SAP egress QoS policy information. Page 296 7950 XRS Quality of Service Guide...
Page 297 The PIR defines the maximum rate that the queue can transmit packets through the switch fabric (for SAP ingress queues) or out an egress interface (for SAP egress queues). 7950 XRS Quality of Service Guide Page 297...
Page 298 PIR setting. FC Name Specifies the forwarding class queue mapping or dot1p marking is to be edited. Queue-id Specifies the queue-id that uniquely identifies the queue within the policy. Page 298 7950 XRS Quality of Service Guide...
Page 299 Default SAP egress QoS policy. 1010 Template 1020 Template =============================================================================== A:ALA-49# configure #-------------------------------------------------- echo "QoS Policy Configuration" #-------------------------------------------------- match-list ip-prefix-list "ip-prefix-list-1" create description "IPv4 prefix list" prefix 10.0.0.0/8 prefix 192.168.0.0/16 exit exit exit #-------------------------------------------------- 7950 XRS Quality of Service Guide Page 299...
Page 300 For each queue specified, the system may find multiple hardware queues. This may be true for ingress queues on multipoint services (VPLS, IES, VPRN) or for queues created on an Ethernet Link Aggregation Page 300 7950 XRS Quality of Service Guide...
Page 301 — The id keyword is used to limit the return queues to a single queue-id. The keyword is not accepted when the system match criteria is used. 7950 XRS Quality of Service Guide Page 301...
Page 302 With each sample, the system indirectly calculates the amount of scheduling bandwidth based on how much Page 302 7950 XRS Quality of Service Guide...
Page 303 — An optional keyword used to display a calculated worst case visitation rate for the specified burst-control-group-name based on the specified value for megabits-per-second. megabits-per-second — A value also modifies the member-queues ‘at-risk’ state output. 7950 XRS Quality of Service Guide Page 303...
Page 304 Service Queue QoS Policy Commands Page 304 7950 XRS Quality of Service Guide...
Page 305: Queue Sharing And Redirection
Network IP Interface Forwarding Class-Based Redirection on page 325 • Queue Group Behavior on LAG on page 341 • Configuring Ingress/Egress PW Shaping Using Spoke-SDP Forwarding Class-Based Redirection on page 358 • Basic Configurations on page 344 7950 XRS Quality of Service Guide Page 305...
Page 306: Queue Sharing And Redirection
Access SAP port and ingress forwarding plane and network port and ingress forwarding plane queue groups are supported on IOM-3s. Queue sharing and redirection are also supported in conjunction with the use of existing Ethernet MDA, Ethernet CMA, HS-MDA and the VSM MDA. Page 306 7950 XRS Quality of Service Guide...
Page 307: Queue Group Applications
IOM/ IMM/XMA forwarding plane. To provide more flexibility on the egress side of the access port, multiple egress access queue group queue-group instances are supported per egress access port. 7950 XRS Quality of Service Guide Page 307...
Page 308: Network Port Queue Groups For Ip Interfaces
This is particularly important for protocol traffic such as LACP, EFM- OAM, ETH-CFM, ARP and IS-IS, which by default use the FC NC regular network port queue. Page 308 7950 XRS Quality of Service Guide...
Page 309: Pseudowire Shaping For Layer 2 And Layer 3 Services
IP interface which the PW packets can be forwarded on. This creates one instance of the template on the egress of the port. One or more instances of the same template can be created. 7950 XRS Quality of Service Guide Page 309...
Page 310 PW template and specify the redirect queue-group name. One or more spoke-sdps can have their FCs redirected to use queues only, or queues and policers in the same queue-group instance. Page 310 7950 XRS Quality of Service Guide...
Page 311: Figure 14: Ingress Qos Control On Vprn Bindings
GRE headers, or the FCS of the incoming frame. The following command configures the association of the network QoS policy and the FP queue group and instance within the network ingress of a VPRN: configure vprn network 7950 XRS Quality of Service Guide Page 311...
Page 312 VPRN. It is also supported for Carrier-Supporting-Carrier VPRNs. The ingress network interfaces on which the traffic is received must be on FP2- and higher-based hardware. The above command is ignored on FP1-based hardware. Page 312 7950 XRS Quality of Service Guide...
Page 313: Queue Group Templates And Port Queue Groups
The user has the option of specifying percent-rate for pir and cir parameters. For pir, the range is 0.01 to 100.00, and for cir, the range is 0.00 to 100.00. 7950 XRS Quality of Service Guide Page 313...
Page 314 When the queue rate is configured with percent-rate, a port-limit is applied, specifically, the percent-rate is relative to the rate of the port to which the queue is attached. *A:PE>config>qos>qgrps>egr>qgrp>queue# percent-rate - no percent-rate - percent-rate <pir-percent> [cir <cir-percent>] <pir-percent> : [0.01..100.00] <cir-percent> : [0.00..100.00] Page 314 7950 XRS Quality of Service Guide...
Page 315: Forwarding Plane Queue Groups
Forwarding plane queue groups are only supported with Ethernet ports and may be created on IOM/IMM/XMAs with ports in a LAG. 7950 XRS Quality of Service Guide Page 315...
Page 316: Redirection Models
Policy based redirection is applicable to port queue groups on access ingress and access and network egress, while SAP based redirection is applicable to forwarding plane queue groups on access and network ingress, and port queue groups on access and network egress. Page 316 7950 XRS Quality of Service Guide...
Page 317: Access Sap Forwarding Class Based Redirection
ID (Steps 2 and 3 may be done in opposite order). Examples are as follows: On ingress: config>qos>sap-ingress policy-id fc fc-name queue queue-id group queue-group-name On egress: config>qos>sap-egress policy-id fc fc-name queue queue-id group queue-group-name instance instance-id 7950 XRS Quality of Service Guide Page 317...
Page 318 (Steps 2 and 3 may be done in opposite order.) On ingress: config>qos>sap-ingress policy-id fc fc-name queue queue-id fp-redirect-group On egress: config>qos>sap-egress policy-id fc fc-name queue queue-id port-redirect-group-queue config>qos>sap-egress policy-id fc fc-name policer policer-id port-redirect-group-queue Page 318 7950 XRS Quality of Service Guide...
Page 319 On egress: config>service>epipe>sap sap-id egress qos sap-egress-policy-id port-redirect-group queue-group-name instance instance-id Note that redirection to a queue group on the HSMDA supports the SAP-based provisioning model, only. 7950 XRS Quality of Service Guide Page 319...
Page 320: Ingress And Egress Sap Forwarding Class Redirection Association Rules
If the queue group name does not exist as an egress queue group template, the forwarding class redirection will fail. • If a redirection queue ID does not exist within the egress queue group template, the forwarding class redirection will fail. Page 320 7950 XRS Quality of Service Guide...
Page 321 When a SAP ingress QoS policy with a forwarding class redirection to a queue group queue ID is removed from a SAP: 7950 XRS Quality of Service Guide Page 321...
Page 322 If the forwarding class is being moved to another queue group policer ID that does not exist within the ingress FP queue group, the redirection removal from the current queue group policer ID will fail. Page 322 7950 XRS Quality of Service Guide...
Page 323 QoS template, then the system will check that the corresponding queue-id exists in any queue group instances associated with any SAPs using the QoS policy. 7950 XRS Quality of Service Guide Page 323...
Page 324: Access Queue Group Statistics
The set of statistics per queue are eligible for collection in a similar manner to SAP queues. The collect-stats command enables or disables statistics collection in to a billing file based on the accounting policy applied to the queue group. Page 324 7950 XRS Quality of Service Guide...
Page 325: Network Ip Interface Forwarding Class-Based Redirection
If the IP interface is bound to a port (or LAG) and the specified queue group name does not exist on the port, the QoS policy application will fail. If the operation above is successful, then: 7950 XRS Quality of Service Guide Page 325...
Page 326 The system increments the association counter for the queue group on the port. When an IP interface associated with a queue group is unbound from a port: • The system decrements the association counter for the queue group on the unbound port Page 326 7950 XRS Quality of Service Guide...
Page 327: Egress Network Ip Interface Statistics
The existing counters will now only count IPv4 traffic, while new separate counters are available to IPv6 traffic. The feature introduces a new CLI command to explicitly enable ingress statistics on IP interfaces, changing the default to disabled. 7950 XRS Quality of Service Guide Page 327...
Page 328: Ingress Pw Shaping Using Spoke-Sdp Forwarding Class-Based Redirection
FP. The shared queue parameters are configurable using the following command: 1. This feature applies to both spoke-SDP and mesh-SDP. Spoke-SDP is used throughout for ease of reading. Page 328 7950 XRS Quality of Service Guide...
Page 329 3. One or more instances of the same policer queue-group name and/or a different policer queue-group name can be created on network ingress context of an IOM3/IMM FP. 4. The queue-group-name must be unique within all network ingress and access ingress queue groups in the system. 7950 XRS Quality of Service Guide Page 329...
Page 330 The only exceptions to this behavior are for packets received from a IES/VPRN spoke interface and from a R-VPLS spoke-SDP, which is forwarded to the R-VPLS IP interface. In Page 330 7950 XRS Quality of Service Guide...
Page 331 Ingress and Egress Queue Group Creation and Redirection these two cases, the ingress network shared queue for the packet FC defined in the network-queue policy applied to the ingress of the MDA/FP is used. 7950 XRS Quality of Service Guide Page 331...
Page 332 In this case, the packet classification is performed according to default classification rule or the QoS filters defined in the ingress context of the network QoS policy applied to the network IP interface the PW packet is received on. Page 332 7950 XRS Quality of Service Guide...
Page 333: Egress Pw Shaping Using Spoke-Sdp Forwarding Class-Based Redirection
The CLI configuration in this section uses a spoke-sdp defined in the context of a VPRN interface. However the PW shaping feature is supported with all PW based services and PW template. 7950 XRS Quality of Service Guide Page 333...
Page 334 PW packet is fed directly to the corresponding egress queue for that FC used by the IP network interface the PW packet is forwarded on. This queue can be a queue-group Page 334 7950 XRS Quality of Service Guide...
Page 335 QoS policy has the corresponding packets feed directly the corresponding the egress shared queue for that FC defined in the network-queue policy applied to the egress of this port. 7950 XRS Quality of Service Guide Page 335...
Page 336 Conversely, the CLI does not allow the user to add the egress re-classification commands to a network QoS policy if it is being used by a network IP interface or a L2 spoke-SDP. Page 336 7950 XRS Quality of Service Guide...
Page 337 QoS policy assigned to the network IP interface. Since the network QoS policy applied to a network IP interface does not support re-classification, the PW packets do not undergo re- classification. 7950 XRS Quality of Service Guide Page 337...
Page 338: Ingress Per Sap Statistics With Ingress Queue Groups
: 04/04/2014 11:51:12 Packets Octets CPM Ingress Forwarding Engine Stats Dropped Received Valid Off. HiPrio Off. LowPrio Off. Uncolor Off. Managed Queueing Stats(Ingress QoS Policy 100) Dro. HiPrio Dro. LowPrio For. InProf For. OutProf Page 338 7950 XRS Quality of Service Guide...
Page 339 Pol Ctl Pol : None Acct Pol : None Collect Stats : disabled ------------------------------------------------------------------------------- Statistics ------------------------------------------------------------------------------- Packets Octets Ing. Policer: Grp: qg1 (Stats mode: minimal) Off. All Dro. All For. All =============================================================================== A:PE1# 7950 XRS Quality of Service Guide Page 339...
Page 340: Ingress And Egress Pw Statistics
The SDP binding and queue-group statistics does however remain separate as one or more PWs can have FCs redirected to the same policer ID in the queue-group instance. Page 340 7950 XRS Quality of Service Guide...
Page 341: Queue Group Behavior On Lag
Removing a Queue Group from a LAG A queue group must be removed from the primary port of the LAG. The queue group will be deleted by the system from each of the port members of the LAG. 7950 XRS Quality of Service Guide Page 341...
Page 342 When adding a port to a LAG group, the port must have the same queue groups defined as the existing ports on the LAG before it will be allowed as a member. This includes all queue group override parameters. Page 342 7950 XRS Quality of Service Guide...
Page 343 Ingress and Egress Queue Group Creation and Redirection 7950 XRS Quality of Service Guide Page 343...
Page 344: Basic Configurations
1 best-effort create mbs 100 exit queue 2 best-effort create mbs 100 exit queue 3 best-effort create mbs 100 exit queue 4 best-effort create mbs 100 exit exit exit ---------------------------------------------- *A:Dut-T>cfg>qos>qgrps# Page 344 7950 XRS Quality of Service Guide...
Page 345: Configuring Egress Queue Group Template
1 best-effort create mbs 100 exit queue 2 best-effort create mbs 100 exit queue 3 best-effort create mbs 100 exit queue 4 best-effort create mbs 100 exit exit exit ---------------------------------------------- *A:Dut-T>cfg>qos>qgrps# 7950 XRS Quality of Service Guide Page 345...
Page 346: Applying Ingress Queue Group To Sap Ingress Policy
"ef" create queue 3 group "QG_ingress_1" exit fc "nc" create queue 4 group "QG_ingress_1" exit dot1p 0 fc "be" dot1p 2 fc "af" dot1p 4 fc "ef" dot1p 6 fc "nc" ---------------------------------------------- *A:Dut-T>config>qos>sap-ingress# Page 346 7950 XRS Quality of Service Guide...
Page 347: Applying Egress Queue Group To Sap Egress Policy
2 group "QG_egress_1" exit fc be create queue 1 group "QG_egress_1" exit fc ef create queue 3 group "QG_egress_1" exit fc nc create queue 4 group "QG_egress_1" exit ---------------------------------------------- A:Dut-T>config>qos>sap-egress# 7950 XRS Quality of Service Guide Page 347...
Page 348: Sap-Based Egress Queue Re-Direction
3 port-redirect-group-queue hsmda queue 3 port-redirect-group-queue exit exit fc l1 create queue 3 port-redirect-group-queue hsmda queue 3 port-redirect-group-queue exit exit fc l2 create queue 3 port-redirect-group-queue hsmda Page 348 7950 XRS Quality of Service Guide...
Page 349 3 port-redirect-group-queue exit exit ---------------------------------------------- This is to be in-conjunction with: *A:Dut-A# configure service vpls 1 *A:Dut-A>config>service>vpls# info ---------------------------------------------- shutdown exit sap 9/1/2:1 create egress qos 3 port-redirect-group qg1 instance 101 exit exit 7950 XRS Quality of Service Guide Page 349...
Page 350: Configuring Queue Group On Ethernet Access Ingress Port
The following displays an Ethernet access ingress port queue-group configuration example: *A:Dut-T>config>port# /configure port 9/2/1 *A:Dut-T>config>port# info ---------------------------------------------- ethernet mode access access ingress queue-group "QG_ingress_1" create exit exit egress queue-group "QG_egress_1" create exit exit exit exit no shutdown ---------------------------------------------- *A:Dut-T>config>port# Page 350 7950 XRS Quality of Service Guide...
Page 351 Ingress and Egress Queue Group Creation and Redirection *A:Dut-T>config>port# /configure port 9/2/2 *A:Dut-T>config>port# info ---------------------------------------------- ethernet mode access access ingress queue-group "QG_ingress_1" create exit exit egress queue-group "QG_egress_1" create exit exit exit exit no shutdown ---------------------------------------------- *A:Dut-T>config>port# 7950 XRS Quality of Service Guide Page 351...
Page 352: Configuring Overrides
"QG_ingress_1" create exit exit egress queue-group "QG_egress_1" create queue-overrides queue 3 create rate 1500000 cir 2000 exit exit exit exit exit exit no shutdown ---------------------------------------------- *A:Dut-T>config>port# Page 352 7950 XRS Quality of Service Guide...
Page 353: Configuring Queue Group On Ethernet Access Egress Port
Apply the SAP egress QoS policy and the queue-group template's instance under the SAP. → Identify or create the egress SAP requiring forwarding class redirection to the queue group → Assign the QoS policy and the egress queue-group template's instance to the SAP. 7950 XRS Quality of Service Guide Page 353...
Page 354: Configuring Queue Group For Network Egress Traffic On Port
→ Assign the QoS policy to the IP interface and specify the queue group name (and optionally instance ID) for redirection of egress traffic. Once a queue within a template is mapped by a forwarding class on any object, the queue may be edited, but not deleted. Page 354 7950 XRS Quality of Service Guide...
Page 355: Configuring Queue Group For Network Ingress Traffic On Forwarding Plane
→ Identify or create the IP interface requiring forwarding class redirection to the queue group. → Assign the QoS policy to the IP interface and specify the queue group name and instance ID for redirection of ingress traffic. 7950 XRS Quality of Service Guide Page 355...
Page 356: Using Queue Groups To Police Ingress/Egress Traffic On Network Interface
1 ingress network queue-group "Ingress_QG_1" instance 550 create exit exit exit exit no shutdown port 1/1/3 ethernet mtu 1514 network egress queue-group "Egress_QG_1" instance 550 create Page 356 7950 XRS Quality of Service Guide...
Page 357 Ingress and Egress Queue Group Creation and Redirection exit exit exit exit no shutdown exit router interface “to-D” address 10.10.11.3/24 port 1/1/3 qos 2 egress-port-redirect-group "Egress_QG_1" egress-instance 550 ingress-fp-redirect-group "Ingress_QG_1" ingress-instance no shutdown 7950 XRS Quality of Service Guide Page 357...
Page 358: Redirection
6 fc be profile out lsp-exp 7 fc be profile out fc af fp-redirect-group policer 4 exit fc be fp-redirect-group policer 1 exit fc l1 fp-redirect-group policer 2 exit fc l2 Page 358 7950 XRS Quality of Service Guide...
Page 359 "QGEgr1" instance 1 create exit queue-group "QGEgr1" instance 2 create exit exit exit exit no shutdown *A:Dut-T>config>service# customer 1 create description "Default customer" exit sdp 1 mpls create description "Default sdp description" far-end 2.2.2.2 7950 XRS Quality of Service Guide Page 359...
Page 360 10 port-redirect-group "QGEgr1" instance 1 exit static-mac 00:00:28:00:01:02 create no shutdown exit no shutdown exit router interface "ip-12.1.1.1" address 12.1.1.1/24 port 3/2/1:1 exit interface "system" address 1.1.1.1/32 exit #--------------------------------------------- Page 360 7950 XRS Quality of Service Guide...
Page 361: Specifying Qos Policies On Service Saps
*A:Dut-T>config>service>vpls# info ---------------------------------------------- shutdown exit sap 9/2/1 create ingress qos 10 exit egress qos 10 exit exit sap 9/2/2 create ingress qos 10 exit egress qos 10 exit exit no shutdown ---------------------------------------------- *A:Dut-T>config>service>vpls# 7950 XRS Quality of Service Guide Page 361...
Page 362 Configuring Ingress/Egress PW Shaping Using Spoke-SDP Forwarding Class-Based Redirection Page 362 7950 XRS Quality of Service Guide...
Page 363: Qos Queue Group Template Command Reference
{no-stats | minimal | offered-profile-no-cir | offered-priority-no-cir | offered-limited-profile-cir | offered-profile-cir | offered-priority-cir | offered- total-cir | offered-profile-capped-cir | offered-lim- ited-capped-cir} — no stat-mode — queue queue-id [queue-type] [create] — no queue queue-id 7950 XRS Quality of Service Guide Page 363...
Page 364 [weight weight] [level level] [cir-weight cir-weight] [cir-level cir-level] — no port-parent — rate pir-rate [cir cir-rate] — no rate — packet-byte-offset [policy slope-policy-name] — no packet-byte-offset — xp-specific — packet-byte-offset {add bytes | subtract bytes} Page 364 7950 XRS Quality of Service Guide...
Page 365 — no — high-prio-only percent — no high-prio-only — size-in-kbytes — no — packet-byte-offset {add bytes | subtract bytes} — no packet-byte-offset — parent scheduler-name [weight weight] [level level] [cir-weight cir-weight] [cir-level cir-level] 7950 XRS Quality of Service Guide Page 365...
Page 366 Command Hierarchies — no parent — rate pir-rate [cir cir-rate] — rate pir-rate police — no rate Page 366 7950 XRS Quality of Service Guide...
Page 367 [interval seconds] [repeat repeat] [absolute | rate] [arbiter root | name] — scheduler-stats — port port-id queue-group queue-group-name [ingress | egress] [interval seconds] [repeat repeat] [absolute | rate] [access | network] [instance instance-id] 7950 XRS Quality of Service Guide Page 367...
Page 368 Command Hierarchies Page 368 7950 XRS Quality of Service Guide...
Page 369 — The description character string. Allowed values are any string up to 80 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. 7950 XRS Quality of Service Guide Page 369...
Page 370 If group-name does not exist, the command has no effect and does not return an error. Default none Parameters queue-group-name — Specifies the name of the queue group template up to 32 characters in length. Page 370 7950 XRS Quality of Service Guide...
Page 371 The fc command is used to enter the forwarding class mapping context for the given fc-name. Each forwarding class has a default mapping depending on the egress queue group template. The system created 7950 XRS Quality of Service Guide Page 371...
Page 372 Another supported feature—packet-byte-offset—provides a policer with the ability to modify the size of each packet based on a defined number of bytes. Page 372 7950 XRS Quality of Service Guide...
Page 373 — The specified queue-id must exist within the queue-group template applied to the egress context of the port. Values 1—8 policer policer-id — The specified policer-id must exist within the queue-group template applied to the egress context of the port Values 1—8 7950 XRS Quality of Service Guide Page 373...
Page 374 The no version of this command removes the redirection of the FC. Parameters multicast-policer policer-id — The specified policer-id must exist within the queue-group template applied to the ingress context of the forwarding plane Values 1—32 Page 374 7950 XRS Quality of Service Guide...
Page 375 — Defines the constraints enforced when adapting the CIR rate defined within the queue queue-id rate command. The cir parameter requires a qualifier that defines the constraint used when deriving the operational CIR for the queue. When the cir parameter is not specified, the default constraint applies. 7950 XRS Quality of Service Guide Page 375...
Page 376 Parameters default — The default parameter is mutually exclusive to specifying an explicit size value. When burst- limit default is executed, the queue is returned to the system default value. Page 376 7950 XRS Quality of Service Guide...
Page 377 For policers, the size parameter is an integer expression of the number of kilobytes for the policer CBS. Values Queues: 0 - 131072 or default Values Policers:0 — 16777216 or default 7950 XRS Quality of Service Guide Page 377...
Page 378 (when a queue does not receive its fair share of buffers). Another is properly setting the RED slope parame- ters for the needs of services on this port. If the CBS value is larger than the MBS value, an error will occur, preventing the MBS change. Page 378 7950 XRS Quality of Service Guide...
Page 379 Both the scheduling and profiling throughput is affected by the offset as well as the stats (accounting) associated with the queue. The packet-byte-offset does not apply to drop statistics, received valid statistics, or the offered managed and unmanaged statistics used by Ingress Multicast Path Management. 7950 XRS Quality of Service Guide Page 379...
Page 380 The parent scheduler can be made unavailable due to the removal of a scheduler policy or scheduler. When an existing parent scheduler is removed or inoperative, the queue enters the orphaned state mentioned above and automatically return to normal operation when the parent scheduler is available again. Page 380 7950 XRS Quality of Service Guide...
Page 381 — Defines the weight the queue or scheduler will use at the within-cir port priority level (defined by the cir-level parameter). The weight is specified as an integer value from 0 to 100 with 7950 XRS Quality of Service Guide Page 381...
Page 382 — The cir keyword is optional and when defined the required pir-percent parameter expresses the queue’s committed scheduling rate as a percentage of line rate. The line rate associated with the Page 382 7950 XRS Quality of Service Guide...
Page 383 If the cir-weight parameter is 1 or greater, the cir-level parameter comes into play. Values 0 — 8 (8 is the highest priority) Default 7950 XRS Quality of Service Guide Page 383...
Page 384 Fractional values are not allowed and must be given as a positive integer. When max is specified, the maximum policer rate used will be equal to the maximum capacity of the card on which the policer is Page 384 7950 XRS Quality of Service Guide...
Page 385 If the policer rate is set to a value larger than the maximum rate possible for the card then the CIR used is equivalent to max. Values Queue: 0— 100000000, max Values Policer:0— 2000000000, max Default 7950 XRS Quality of Service Guide Page 385...
Page 386 Note that the minimum resulting packet size used by the system is 1 byte. Values 0—64 Page 386 7950 XRS Quality of Service Guide...
Page 387 The no form of the command restores the generic buffer pool behavior to the queue. The WRED pool is removed from the system. Parameters slope-policy-name — Overrides the default WRED slope policy with an explicit slope policy. The defined slope policy must exist or the command will fail. 7950 XRS Quality of Service Guide Page 387...
Page 388 QoS policies. The parameters within the template queue will be used as the default settings for each queue in the actual queue group. The queue parameters may be individually changed for each queue in each queue group using per queue overrides. Page 388 7950 XRS Quality of Service Guide...
Page 389 MBS and subtracting that result from the mbs size defined. create — Keyword used to create the queue ID instance. The create keyword requirement can be enabled/ disabled in the environment>create context. 7950 XRS Quality of Service Guide Page 389...
Page 390 — Specifies that the out of profile traffic feeding into the physical queue instance should be dropped. Using this keyword will override the bandwidth specified by the SAP ingress queue’s administrative CIR. Page 390 7950 XRS Quality of Service Guide...
Page 391 This command configures a packet byte offset for the QoS ingress queue-group policer. Default none Parameters add bytes — Specifies an number of bytes to add as the offset amount. Values 0 — 31 7950 XRS Quality of Service Guide Page 391...
Page 392 Any queues or schedulers defined as strict receive no parental bandwidth until all strict queues and schedulers with a higher (numerically larger) priority on the parent have reached their maximum bandwidth or are idle. Page 392 7950 XRS Quality of Service Guide...
Page 393 — Selects offered priority CIR statistics as the statistics mode. offered-total-cir — Selects total statistics as the statistics mode. offered-profile-capped-cir — Selects offered profile capped statistics as the statistics mode. offered-limited-capped-cir — Selects offered limited capped statistics as the statistics mode. 7950 XRS Quality of Service Guide Page 393...
Page 394 : QG_egress_1 Description : Egress queue group ------------------------------------------------------------------------------- Queue CIR Admin PIR Admin CBS HiPrio PIR Lvl/Wt Parent CIR Rule PIR Rule CIR Lvl/Wt Named-Buffer Pool ------------------------------------------------------------------------------- None closest closest (not-assigned) None Page 394 7950 XRS Quality of Service Guide...
Page 395 ------------------------------------------------------------------------------- Group-Name : QG_egress_1 Description : Egress queue group =============================================================================== Queue Group Ports (access) =============================================================================== Port Sched Pol Acctg Pol Stats Description ------------------------------------------------------------------------------- 9/2/1 9/2/2 ------------------------------------------------------------------------------- =============================================================================== Queue Group Ports (network) =============================================================================== 7950 XRS Quality of Service Guide Page 395...
Page 396 : QG_ingress_1 Description : Ingress queue-group ------------------------------------------------------------------------------- Queue Mode CIR Admin PIR Admin CBS HiPrio PIR Lvl/Wt Parent CIR Rule PIR Rule CIR Lvl/Wt Named-Buffer Pool ------------------------------------------------------------------------------- Prio None closest closest 100 Page 396 7950 XRS Quality of Service Guide...
Page 397 Queue Group Ports =============================================================================== Port Sched Pol Acctg Pol Stats Description ------------------------------------------------------------------------------- 9/2/1 9/2/2 ------------------------------------------------------------------------------- =============================================================================== Queue Group Sap FC Maps =============================================================================== Sap Policy FC Name Queue (id type) ------------------------------------------------------------------------------- (2 Unicast) (1 Unicast) 7950 XRS Quality of Service Guide Page 397...
Page 398 6678807 6649127172 For. All 85157395 84816403620 Ing. Policer: Grp: QGIng1 (Stats mode: minimal) Off. All 93584703 90933906888 Dro. All 8320200 6106644900 For. All 85264503 84827261988 Ing. Policer: Grp: QGIng1 (Stats mode: minimal) Page 398 7950 XRS Quality of Service Guide...
Page 399 Dro. All For. All Ing. Policer: 13 Grp: QGIng1 (Stats mode: minimal) Off. All Dro. All For. All Ing. Policer: 14 Grp: QGIng1 (Stats mode: minimal) Off. All Dro. All For. All 7950 XRS Quality of Service Guide Page 399...
Page 400 Oper Thresh Fair:425984 Association count:0 Priority 3 Oper Thresh Unfair:311296 Oper Thresh Fair:425984 Association count:0 Priority 2 Oper Thresh Unfair:311296 Oper Thresh Fair:425984 Association count:4 Priority 1 Oper Thresh Unfair:102400 Oper Thresh Fair:204800 Page 400 7950 XRS Quality of Service Guide...
Page 401 StatMode: minimal [Level 1 Weight 1] Assigned PIR:125 Offered:9966 Consumed:125 Assigned FIR:125 |--(P) : Policer Net-FPQG-1-T3:1->2 MaxPIR:max MaxCIR:0 CBS:0 MBS:20480 HiPrio:2048 Depth:18944 OperPIR:128 OperCIR:0 OperFIR:128 PacketByteOffset:0 StatMode: minimal [Level 1 Weight 1] 7950 XRS Quality of Service Guide Page 401...
Page 402 HiPrio:2048 Depth:21353 OperPIR:250 OperCIR:0 OperFIR:250 PacketByteOffset:0 StatMode: minimal [Level 1 Weight 1] Assigned PIR:250 Offered:9966 Consumed:250 Assigned FIR:250 |--(P) : Policer Net-FPQG-1-T3:1->7 MaxPIR:max MaxCIR:0 CBS:0 MBS:20480 HiPrio:2048 Depth:21065 OperPIR:250 OperCIR:0 OperFIR:250 PacketByteOffset:0 Page 402 7950 XRS Quality of Service Guide...
Page 403 *A:Dut-T# show qos policer port 9/2/4 network egress queue-group "QGEgr1" instance 1 =============================================================================== Policer Information (Summary), Slot 9 =============================================================================== ------------------------------------------------------------------------------- Name FC-Maps HP-Only A.PIR A.CIR Direction Depth O.PIR O.CIR O.FIR ------------------------------------------------------------------------------- Net-PQG-9/2/4-QGEgr1:1->8 Egress 64 KB 8 KB 0 KB 1026 Net-PQG-9/2/4-QGEgr1:1->7 7950 XRS Quality of Service Guide Page 403...
Page 404 : 64 KB : 0 KB Hi Prio Only : 8 KB Pkt Byte Offset Admin PIR : Max Admin CIR : 0 Kbps Oper PIR : Max Oper CIR : 0 Kbps Page 404 7950 XRS Quality of Service Guide...
Page 405 Parent Arbiter Name: (Not Specified) ------------------------------------------------------------------------------- Arbiter Member Information ------------------------------------------------------------------------------- Offered Rate : 0 Kbps Level Weight Parent PIR : 0 Kbps Parent FIR : 0 Kbps Consumed : 0 Kbps ------------------------------------------------------------------------------- =============================================================================== 7950 XRS Quality of Service Guide Page 405...
Page 406 : 8 KB Pkt Byte Offset Admin PIR : Max Admin CIR : 0 Kbps Oper PIR : Max Oper CIR : 0 Kbps Oper FIR : Max Stat Mode : minimal Page 406 7950 XRS Quality of Service Guide...
Page 407 Policer Info (1->10:110->10), Slot 9 Policer Info (1->11:111->10), Slot 9 Policer Info (1->12:112->10), Slot 9 Policer Info (1->13:113->10), Slot 9 Policer Info (1->14:114->10), Slot 9 Policer Info (1->15:115->10), Slot 9 Policer Info (1->16:116->10), Slot 9 7950 XRS Quality of Service Guide Page 407...
Page 408 Off. All : 22133355 22708822230 Dro. All For. All : 22133355 22708822230 Egress Policer: Group: QGEgr1 Instance-Id: 1 Stats mode: minimal Off. All : 22133355 22708822230 Dro. All For. All : 22133355 22708822230 Page 408 7950 XRS Quality of Service Guide...
Page 409 FC Name Queue (id type) ------------------------------------------------------------------------------- No Matching Entries =============================================================================== Queue Group FP Maps =============================================================================== Card Num Fp Num Instance Type ------------------------------------------------------------------------------- Network Network Network Network Network Network Network Network Network Network 7950 XRS Quality of Service Guide Page 409...
Page 410 ------------------------------------------------------------------------------- Statistics ------------------------------------------------------------------------------- Packets Octets Ing. Policer: Grp: QGIng3 (Stats mode: offered-profile-capped-cir) Off. InProf Off. OutProf Off. Uncolor 22159073 1506816964 Dro. InProf Dro. OutProf For. InProf 215642 14663656 For. OutProf 21943431 1492153308 Page 410 7950 XRS Quality of Service Guide...
Page 411 *A:Dut-A# show card 9 fp 1 ingress mode access queue-group "Ingress_QG_1" instance 2838 =============================================================================== Card:9 Acc.QGrp: Ingress_QG_1 Instance: 2838 =============================================================================== Group Name : Ingress_QG_1 Description : (Not Specified) Pol Ctl Pol : None Acct Pol : None 7950 XRS Quality of Service Guide Page 411...
Page 412 *A:Dut-A# monitor card 9 fp 1 ingress access queue-group "Ingress_QG_1" instance 2838 policer 2 ======================================================================== Monitor Card: 9 Ingress Access Queue-Group: Ingress_QG_1 Statistics ======================================================================== ------------------------------------------------------------------------------- At time t = 0 sec (Base Statistics) ------------------------------------------------------------------------------- Packets Octets Ing. Policer: Grp: Ingress_QG_1 (Stats mode: minimal) Page 412 7950 XRS Quality of Service Guide...
Page 413 Grp: Ingress_QG_1 (Stats mode: minimal) Off. All : 9291543 1189317504 Dro. All : 8754385 1120561280 For. All : 537158 68756224 ------------------------------------------------------------------------------- At time t = 66 sec (Mode: Delta) ------------------------------------------------------------------------------- Packets Octets 7950 XRS Quality of Service Guide Page 413...
Page 414 Grp: Ingress_QG_1 (Stats mode: minimal) Off. All : 9290735 1189214080 Dro. All : 8753622 1120463616 For. All : 537113 68750464 ======================================================================== *A:Dut-A# clear card 9 fp 1 mode access ingress queue-group "Ingress_QG_1" instance 2838 statistics Page 414 7950 XRS Quality of Service Guide...
Page 415 This command displays queue group pool information. Parameters mda-id[/port] — Displays the pool information of the specified . access-app pool-name — Displays the pool information of the specified QoS policy. Values access-ingress, access-egress 7950 XRS Quality of Service Guide Page 415...
Page 416 WA Shared In Use : 0 KB Hi-Slope Drop Prob Lo-Slope Drop Prob : 0 ------------------------------------------------------------------------------- Name FC-Maps HP-Only A.PIR A.CIR Depth O.PIR O.CIR ------------------------------------------------------------------------------- QGrp->QG_egress_1(9/2/1)->1 1000000 QGrp->QG_egress_1(9/2/1)->2 1000000 QGrp->QG_egress_1(9/2/1)->3 1000000 QGrp->QG_egress_1(9/2/1)->4 1000000 =============================================================================== *A:Dut-T>config>port# Page 416 7950 XRS Quality of Service Guide...
Page 417 Lo-Slope Drop Prob : 0 ------------------------------------------------------------------------------- Name FC-Maps HP-Only A.PIR A.CIR Depth O.PIR O.CIR ------------------------------------------------------------------------------- QGrp->QG_ingress_1(9/2/1)->1 1000000 QGrp->QG_ingress_1(9/2/1)->1 1000000 QGrp->QG_ingress_1(9/2/1)->1 1000000 QGrp->QG_ingress_1(9/2/1)->1 1000000 QGrp->QG_ingress_1(9/2/1)->1 1000000 QGrp->QG_ingress_1(9/2/1)->1 1000000 QGrp->QG_ingress_1(9/2/1)->1 1000000 QGrp->QG_ingress_1(9/2/1)->1 1000000 QGrp->QG_ingress_1(9/2/1)->1 1000000 QGrp->QG_ingress_1(9/2/1)->1 1000000 7950 XRS Quality of Service Guide Page 417...
Page 418 1000000 QGrp->QG_ingress_1(9/2/1)->1 1000000 QGrp->QG_ingress_1(9/2/1)->1 1000000 QGrp->QG_ingress_1(9/2/1)->1 1000000 QGrp->QG_ingress_1(9/2/1)->1 1000000 QGrp->QG_ingress_1(9/2/1)->1 1000000 QGrp->QG_ingress_1(9/2/1)->1 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 Page 418 7950 XRS Quality of Service Guide...
Page 419 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 7950 XRS Quality of Service Guide Page 419...
Page 420 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 Page 420 7950 XRS Quality of Service Guide...
Page 421 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 =============================================================================== *A:Dut-T>config>port# 7950 XRS Quality of Service Guide Page 421...
Page 422 Admin PIR : max* Admin CIR: 0* PIR Rule : closest* CIR Rule : closest* : def* : 100* Hi Prio : def* Ing. QGroup : QG_ingress_1 Queue-Id : 4 (Unicast) (Priority) Page 422 7950 XRS Quality of Service Guide...
Page 423 : 100* Hi Prio : def* * means the value is inherited =============================================================================== *A:Dut-T>config>port# *A:Dut-T>config>port# show port 9/2/2 egress queue-group QG_egress_1 statistics ------------------------------------------------------------------------------- Ethernet port 9/2/2 Access Egress queue-group ------------------------------------------------------------------------------- Packets Octets 7950 XRS Quality of Service Guide Page 423...
Page 424 Egress Queue: 3 Group: QG_egress_1 For. InProf For. OutProf : 40661628 2764990704 Dro. InProf Dro. OutProf Egress Queue: 4 Group: QG_egress_1 For. InProf For. OutProf : 40661629 2764990772 Dro. InProf Dro. OutProf ------------------------------------------------------------------------------- *A:Dut-T>config>port# Page 424 7950 XRS Quality of Service Guide...
Page 425 No calculations are performed on the delta or rate statistics. percent-rate — When the percent-rate keyword is specified, the rate-per-second for each statistic is displayed based on the reference rate of 10G. 7950 XRS Quality of Service Guide Page 425...
Page 426 10G. reference-rate — When a reference-rate value is specified, the rate-per-second for each statistic is displayed as a percentage based on the reference rate specified. Values 100M, 1G, 10G, 40G, 100G, 400G Page 426 7950 XRS Quality of Service Guide...
Page 427 An existing arbiter-name in the form of a string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. root — Specify the root arbiter. 7950 XRS Quality of Service Guide Page 427...
Page 428 — When the rate keyword is specified, the rate-per-second for each statistic is displayed. access — Displays scheduler statistics applied on an access port. network — Displays scheduler statistics applied on a network port. Page 428 7950 XRS Quality of Service Guide...
Page 429: Shared-Queue Qos Policy Command Reference
— percent — no — high-prio-only percent — no high-prio-only — percent — no — rate percent [cir percent] — no rate Show Commands show — qos — shared-queue [policy-name] [detail] 7950 XRS Quality of Service Guide Page 429...
Page 430 Configuration Commands Page 430 7950 XRS Quality of Service Guide...
Page 431 — A text string describing the entity. Allowed values are any string up to 80 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. 7950 XRS Quality of Service Guide Page 431...
Page 432 The broadcast forwarding type usually tracks the multicast forwarding type definition. This command overrides that default behavior. The no form of the command sets the broadcast forwarding type queue-id back to the default of track- ing the multicast forwarding type queue mapping. Page 432 7950 XRS Quality of Service Guide...
Page 433 — The queue-id parameter specified must be an existing, non-multipoint queue defined in the config>qos>sap-ingress context. Values Any valid non-multipoint queue-id in the policy including 1 and 3 through 32 . Default 7950 XRS Quality of Service Guide Page 433...
Page 434 A queue must be created as multipoint. The multipoint designator cannot be defined after the queue is created. If an attempt is made to modify the command to include the multipoint keyword, an error is generated and the command will not execute. Page 434 7950 XRS Quality of Service Guide...
Page 435 The RED slopes will detect congestion conditions and work to discard packets and slow down ran- dom TCP session flows through the queue. The RED slope definitions can be defined, modified or 7950 XRS Quality of Service Guide Page 435...
Page 436 Modifying the current MBS for the queue through the mbs command will cause the default high- prio-only function to be recalculated and applied to the queue. The high-prio-only command as defined for the specific queue can be used to override the default high-prio-only setting as defined in Page 436 7950 XRS Quality of Service Guide...
Page 437 The MBS size can sometimes be smaller than the CBS. This will result in a portion of the CBS for the queue to be unused and should be avoided. Default The mbs forwarding class defaults are listed in the table below. 7950 XRS Quality of Service Guide Page 437...
Page 438 — Defines the percentage of the max rate allowed for the queue. When the rate command is executed, a valid PIR setting must be explicitly defined. When the rate command has not been Page 438 7950 XRS Quality of Service Guide...
Page 439 CIR setting is optional. When the rate command has not been executed or the cir parameter is not explicitly specified, the default CIR (0) is assumed. Fractional values are not allowed and must be given as a positive integer. Values 0 — 100, max Default 7950 XRS Quality of Service Guide Page 439...
Page 440: Table 28: Show Qos Shared Queue Output Fields
A:ALA-1>config>qos# show qos shared-queue default =============================================================================== QoS Network Queue Policy =============================================================================== ------------------------------------------------------------------------------- Shared Queue Policy (default) ------------------------------------------------------------------------------- Policy : default Description : Default Shared Queue Policy ------------------------------------------------------------------------------- Associations ------------------------------------------------------------------------------- No Matching Entries =============================================================================== A:ALA-1>config>qos# Page 440 7950 XRS Quality of Service Guide...
Page 441: Qos Scheduler Policies
This section provides information to configure QoS scheduler and port scheduler policies using the command line interface. Topics in this section include: • Overview on page 442 • Basic Configurations on page 465 • Service Management Tasks on page 484 7950 XRS Quality of Service Guide Page 441...
Page 442: Overview
The second tier receives bandwidth from the first tier in two priorities, a “within-cir” loop and an “above-cir” loop. The second tier “within-cir” loop provides bandwidth to the third tier “within- Page 442 7950 XRS Quality of Service Guide...
Page 443: Qos Scheduler Policies
Priority level 6 remaining offered load up to remaining priority rate limit Priority level 5 remaining offered load up to remaining priority rate limit Priority level 4 remaining offered load up to remaining priority rate limit 7950 XRS Quality of Service Guide Page 443...
Page 444: Service/ Egress Port Bandwidth Allocation
Two methods are supported to allocate bandwidth to each service queue: 1. Service queue association with a scheduler on the SAP or multi-service site which is itself associated with a port-level scheduler. 2. Service queue association directly with a port-level scheduler. Page 444 7950 XRS Quality of Service Guide...
Page 445: Figure 15: Port Level Virtual Scheduler Bandwidth Allocation Based On Priority And Cir
Limit Priority 1 High “Above-CIR” Priority Weighted Distribution Above-CIR Strict Distribution Priority 1 “Above-CIR” Orphan RR Distribution Priority OSSG130 Figure 15: Port Level Virtual Scheduler Bandwidth Allocation Based on Priority and CIR 7950 XRS Quality of Service Guide Page 445...
Page 446: Figure 16: Two Scheduler Policy Model For Access Ports
As an added benefit, the two policy approach provides the carrier with the ability to preferentially allocate bandwidth within a service context through the service level policy without affecting the overall bandwidth allocation to each service Page 446 7950 XRS Quality of Service Guide...
Page 447: Figure 17: Schedulers On Sap Or Multi-Service Site Receive Bandwidth From Port Priority Levels
Scheduler Scheduler SAP or MSS SAP or MSS Priority n Weighted Rate Limiting Scheduler SAP or MSS OSSG132 Figure 17: Schedulers on SAP or Multi-Service Site Receive Bandwidth From Port Priority Levels 7950 XRS Quality of Service Guide Page 447...
Page 448 The benefit of the single scheduler policy model is that the bandwidth is allocated per priority for all queues associated with the egress port. This allows a provider to preferentially allocate bandwidth to higher priority classes of service independent of service instance. Page 448 7950 XRS Quality of Service Guide...
Page 449: Figure 18: Direct Service Or Association To Port Scheduler Model
Scheduler Queue Rate Queue Limit Priority n or MSS Weighted Rate Limiting Queue Scheduler Queue Rate Queue Limit or MSS Queue OSSG133 Figure 18: Direct Service or Association to Port Scheduler Model 7950 XRS Quality of Service Guide Page 449...
Page 450: Frame And Packet-Based Bandwidth Allocation
Figure 19 Figure 20 provide a logical view of bandwidth distribution from the port to the queue level and shows the packet or frame-based provisioning at each step. Page 450 7950 XRS Quality of Service Guide...
Page 451: Figure 19: Port Bandwidth Distribution For Service And Port Scheduler Hierarchies
Highest Highest Strict Egress Weighted Priority Rate Port Rate Limiting Queue Rate Limiting Limit Scheduler Scheduler Lowest Lowest Queue OSSG135 Figure 20: Port Bandwidth Distribution for Direct Queue to Port Scheduler Hierarchy 7950 XRS Quality of Service Guide Page 451...
Page 452: Queue Parental Association Scope
The schedulers at tiers 2 and 3 can also be moved back to a local parent at anytime by executing the local parent command. Lastly, the Page 452 7950 XRS Quality of Service Guide...
Page 453: Figure 21: Bandwidth Distribution On Network Port With Port-Based Scheduling
(Frame Provisioned) (Packet Provisioned) Egress Highest Highest Strict Network Weighted Priority Port Rate Limiting Queue Rate Limiting Scheduler Scheduler Lowest Lowest OSSG136 Figure 21: Bandwidth Distribution on Network Port with Port-Based Scheduling 7950 XRS Quality of Service Guide Page 453...
Page 454: Foster Parent Behavior For Orphaned Queues And Schedulers
It is expected that an orphan condition is not the desired state for a queue or scheduler and is the result of a temporary configuration change or configuration error. Page 454 7950 XRS Quality of Service Guide...
Page 455: Frame-Based Accounting
When egress port based virtual scheduling was added, frame based usage on the wire was added to allow for the port bandwidth to be accurately allocated to each child queue on the port. 7950 XRS Quality of Service Guide Page 455...
Page 456: Existing Egress Port Based Virtual Scheduling
20 bytes per packet and thus allow more packets through per second. Similarly, the rates defined in the scheduling policy with frame based accounting enabled will automatically be interpreted as frame based rates. Page 456 7950 XRS Quality of Service Guide...
Page 457: Qos Scheduler Policies
Setting the frame based accounting parameter on the aggregate rate limit command only affects the queues managed by the aggregate rate limit and converts them from packet based to frame based accounting mode. 7950 XRS Quality of Service Guide Page 457...
Page 458: Virtual Scheduling Unused Bandwidth Distribution
The limit-unused-bandwidth (LUB) command protects against exceeding the aggregated bandwidth by adding a LUB second-pass to the HQoS function, which ensures that the aggregate fair-share bandwidth does not exceed the aggregate rate. Page 458 7950 XRS Quality of Service Guide...
Page 459: Qos Scheduler Policies
Taking a simple scenario with 5 egress SAP queues all without rates configured but with each queue parented to a different level in a parent scheduler which has a rate of 100Mb/s, see Figure 7950 XRS Quality of Service Guide Page 459...
Page 460: Figure 22: Limit Unused Bandwidth Example
(full allocated part of [100/5=20] capacity minus the unused capacity used by capacity. higher levels) Figure 23: Resulting Bandwidth Distribution Page 460 7950 XRS Quality of Service Guide...
Page 461: Configuring Port Scheduler Policies
The port scheduler is designed to offer on-the-wire bandwidth. For Ethernet ports, this includes the IFG and the preamble for each frame and represents 20 bytes total per frame. The queues and intermediate service level schedulers (a 7950 XRS Quality of Service Guide Page 461...
Page 462 CIR and rate PIR to frame based values. The frame based values are then used to distribute the port based bandwidth down to the queue level. Page 462 7950 XRS Quality of Service Guide...
Page 463: Aggregate Rate Limits For Directly Attached Queues
Network Queue QoS Policy Queue Parenting A network-queue policy only supports direct port parent priority association. Intermediate schedulers are not supported on network ports. 7950 XRS Quality of Service Guide Page 463...
Page 464: Egress Port Scheduler Overrides
When a level is not explicitly mapped to any group, it maps directly to the root of the port scheduler at its own priority like in existing behavior. Page 464 7950 XRS Quality of Service Guide...
Page 465: Basic Configurations
"QoS Policy Configuration" #------------------------------------------ scheduler-policy "SLA1" create description "NetworkControl(3), Voice(2) and NonVoice(1) have strict priorities" tier 1 scheduler "All_traffic" create description "All traffic goes to this scheduler eventually" rate 11000 exit exit tier 2 7950 XRS Quality of Service Guide Page 465...
Page 466 NonVoice level 5 cir-level 5 rate 1500 cir 1500 exit scheduler "VPN_voice" create parent Voice rate 2500 cir 2500 exit exit exit sap-ingress 100 create description "Used on VPN sap" ---------------------------------------------- A:ALA-12>config>qos# Page 466 7950 XRS Quality of Service Guide...
Page 467: Applying Scheduler Policies
SAP ingress and egress. A:SR>config>service# info ---------------------------------------------- ies 88 customer 8 vpn 88 create interface "Sector A" create sap 1/1/1.2.2 create ingress scheduler-policy "SLA2" qos 101 exit egress scheduler-policy "SLA2" qos 1020 exit 7950 XRS Quality of Service Guide Page 467...
Page 468 Basic Configurations exit exit no shutdown exit ---------------------------------------------- A:SR>config>service# Page 468 7950 XRS Quality of Service Guide...
Page 469: Creating A Qos Port Scheduler Policy
[level priority-level] [weight weight] [cir-level priority-level] [cir-weight cir-weight] The following displays a scheduler policy configuration example: *A:ALA-48>config>qos>port-sched-plcy# info ---------------------------------------------- description "Test Port Scheduler Policy" orphan-override weight 50 cir-level 4 cir-weight 50 ---------------------------------------------- *A:ALA-48>config>qos>port-sched-plcy# 7950 XRS Quality of Service Guide Page 469...
Page 470: Configuring Port Parent Parameters
The weight value defines the relative ratio that is used to distribute bandwidth at the priority level when more above- cir offered load exists than the port priority level has bandwidth. Page 470 7950 XRS Quality of Service Guide...
Page 471: Qos Scheduler Policies
CLI Syntax: config>qos# network-queue network-queue-policy-name [create] no network-queue network-queue-policy-name queue queue-id [multipoint] [{auto-expedite | best-effort | expedite}] [priority-mode | profile-mode] [create] port-parent [level priority-level] [weight priority- weight] [cir-level cir-priority-level] [cir-weight cir-priority-weight] 7950 XRS Quality of Service Guide Page 471...
Page 472: Configuring Distributed Lag Rate
*B:ALU-A>config>service>ies>if>sap# /show qos scheduler-hierarchy sap lag-30 egress detail =============================================================================== Scheduler Hierarchy - Sap lag-30 =============================================================================== Egress Scheduler Policy : ------------------------------------------------------------------------------- Legend : (*) real-time dynamic value (w) Wire rates Bytes ------------------------------------------------------------------------------- Root (Egr) | slot(2) Page 472 7950 XRS Quality of Service Guide...
Page 473: Qos Scheduler Policies
Consumed:203247 OperPIR:205000 OperCIR:0 PktByteOffset:add 0* OnTheWireRates:false ATMOnTheWireRates:false LastMileOnTheWireRates:false |--(Q) : 1->lag-30(2/1/10)->1 AdminPIR:1000000 AdminCIR:0 Parent Limit Unused Bandwidth: not-found AvgFrmOv:101.65(*) CBS:0 B MBS:1310720 B Depth:1048320 B HiPrio:262144 B [CIR] Assigned:0 Offered:0 Consumed:0 [PIR] 7950 XRS Quality of Service Guide Page 473...
Page 474 Parent Limit Unused Bandwidth: not-found AvgFrmOv:101.65(*) CBS:0 B MBS:1253376 B Depth:1106976 B HiPrio:147456 B [CIR] Assigned:0 Offered:0 Consumed:0 [PIR] Assigned:203247 Offered:1000000 Consumed:203247 OperPIR:203125 OperCIR:0 PktByteOffset:add 0* OnTheWireRates:false ATMOnTheWireRates:false LastMileOnTheWireRates:false |--(Q) : 1->lag-30(3/2/1)->1 Page 474 7950 XRS Quality of Service Guide...
Page 475: Qos Scheduler Policies
AdminPIR:2000000 AdminCIR:0(sum) Parent Limit Unused Bandwidth: not-found AvgFrmOv:101.65(*) AdminPIR:2000000(w) AdminCIR:0(w) [Within CIR Level 0 Weight 0] Assigned:0(w) Offered:0(w) Consumed:0(w) [Above CIR Level 1 Weight 0] Assigned:206601(w) Offered:2000000(w) <----with dist-lag-rate-shared 206 Mb is 7950 XRS Quality of Service Guide Page 475...
Page 476 CBS:0 B MBS:1310720 B Depth:1047040 B HiPrio:262144 B [CIR] Assigned:0 Offered:0 Consumed:0 [PIR] Assigned:101624 Offered:1000000 Consumed:101624 OperPIR:102000 OperCIR:0 PktByteOffset:add 0* OnTheWireRates:false ATMOnTheWireRates:false LastMileOnTheWireRates:false | slot(3) |--(S) : Tier0Egress:1->lag-30:0.0->1 (Port lag-30 Orphan) AdminPIR:2000000 AdminCIR:0(sum) Page 476 7950 XRS Quality of Service Guide...
Page 477: Qos Scheduler Policies
PktByteOffset:add 0* OnTheWireRates:false ATMOnTheWireRates:false LastMileOnTheWireRates:false |--(Q) : 1->lag-30(3/2/1)->1 AdminPIR:1000000 AdminCIR:0 Parent Limit Unused Bandwidth: not-found AvgFrmOv:101.65(*) CBS:0 B MBS:1253376 B Depth:1105728 B HiPrio:147456 B [CIR] Assigned:0 Offered:0 Consumed:0 [PIR] Assigned:101624 Offered:1000000 Consumed:101624 7950 XRS Quality of Service Guide Page 477...
Page 478 Forced Prio ------------------------------------------------------------------------------- 2/1/6 active down 32768 2/1/10 active 32768 3/2/1 active 32768 3/2/2 active 32768 =============================================================================== *B:ALU-A>config>qos>port-sched-plcy# /show qos scheduler-hierarchy sap lag-30 egress detail =============================================================================== Scheduler Hierarchy - Sap lag-30 =============================================================================== Page 478 7950 XRS Quality of Service Guide...
Page 479: Qos Scheduler Policies
CBS:0 B MBS:1310720 B Depth:0 B HiPrio:262144 B [CIR] Assigned:0 Offered:0 Consumed:0 [PIR] Assigned:67749 Offered:0 Consumed:0 OperPIR:68000 OperCIR:0 PktByteOffset:add 0* OnTheWireRates:false ATMOnTheWireRates:false LastMileOnTheWireRates:false |--(Q) : 1->lag-30(2/1/10)->1 AdminPIR:1000000 AdminCIR:0 Parent Limit Unused Bandwidth: not-found 7950 XRS Quality of Service Guide Page 479...
Page 480 [As Parent] OperPIR:270996 OperCIR:0 ConsumedByChildren:270996 |--(Q) : 1->lag-30(3/2/2)->1 AdminPIR:1000000 AdminCIR:0 Parent Limit Unused Bandwidth: not-found AvgFrmOv:101.65(*) CBS:0 B MBS:1253376 B Depth:1106976 B HiPrio:147456 B [CIR] Assigned:0 Offered:0 Consumed:0 [PIR] Assigned:135498 Offered:1000000 Consumed:135498 Page 480 7950 XRS Quality of Service Guide...
Page 481: Qos Scheduler Policies
The group rate, level pir and cir rate can be entered as percent. *B:ALU-A>config>qos>port-sched-plcy# info ---------------------------------------------- dist-lag-rate-shared max-rate percent 30.00 group "test" create percent-rate 20.00 cir 20.00 exit level 1 percent-rate 10.00 percent-cir 10.00 level 2 percent-rate 20.00 percent-cir 20.00 7950 XRS Quality of Service Guide Page 481...
Page 482 : 60.00 Lvl6 CIR Percent : 60.00 Lvl7 PIR : max Lvl7 CIR : max Lvl7 PIR Percent : 70.00 Lvl7 CIR Percent : 70.00 Lvl8 PIR : max Lvl8 CIR : max Page 482 7950 XRS Quality of Service Guide...
Page 483: Qos Scheduler Policies
: 70.00 Lvl7 CIR Percent : 70.00 Lvl8 PIR : max* Lvl8 CIR : max* Lvl8 PIR Percent : 80.00 Lvl8 CIR Percent : 80.00 * means the value is inherited ------------------------------------------------------------------------------- 7950 XRS Quality of Service Guide Page 483...
Page 484: Service Management Tasks
MINOR: QOS #1003 The policy has references SR7>config>qos# Removing a QoS Policy from a Customer Multi-Service Site CLI Syntax: config>service>customer customer-id multi-service-site customer-site-name egress no scheduler-policy ingress no scheduler-policy Example config>service>customer# multi-service-site “Test” config>service>cust>multi-service-site# ingress config>service>cust>multi-service-site>ingress# no scheduler-policy Page 484 7950 XRS Quality of Service Guide...
Page 485: Removing A Qos Policy From Sap(S)
CLI Syntax: config>qos# no scheduler-policy network-policy-id Example config>qos# no scheduler-policy SLA1 To delete a port scheduler policy, enter the following commands: CLI Syntax: config>qos# no port-scheduler-policy network-policy-id Example config>qos# no port-scheduler-policy test1 7950 XRS Quality of Service Guide Page 485...
Page 486: Copying And Overwriting Scheduler Policies
"Internet_priority" create parent "NonVoice" level 2 cir-level 2 exit scheduler-policy "SLA2" create description "NetworkControl(3), Voice(2) and NonVoice(1) have strict priorities" tier 1 scheduler "All_traffic" create description "All traffic goes to this scheduler eventually" Page 486 7950 XRS Quality of Service Guide...
Page 487: Qos Scheduler Policies
"All_traffic" level 2 cir-level 2 rate 5500 exit exit tier 3 scheduler "Internet_be" create parent "NonVoice" cir-level 1 exit scheduler "Internet_priority" create parent "NonVoice" level 2 cir-level 2 exit #------------------------------------------ A:SR>config>qos# 7950 XRS Quality of Service Guide Page 487...
Page 488: Editing Qos Policies
SAPs 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 488 7950 XRS Quality of Service Guide...
Page 489: Qos Scheduler Policy Command Reference
— max-rate percent percent-rate — no max-rate — orphan-override [level priority-level] [weight percent] [cir-level priority-level] [cir- weight cir-weight] — no orphan-override Operational Commands config — qos — copy port-scheduler-policy src-name dst-name [overwrite] 7950 XRS Quality of Service Guide Page 489...
Page 490 Command Hierarchies Show Commands show — qos — port-scheduler-policy [port-scheduler-policy-name] [association] Page 490 7950 XRS Quality of Service Guide...
Page 491 — A text string describing the entity. Allowed values are any string up to 80 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. 7950 XRS Quality of Service Guide Page 491...
Page 492 — Forces the destination policy name to be copied as specified. When forced, everything in the existing destination policy will be completely overwritten with the contents of the source policy. Page 492 7950 XRS Quality of Service Guide...
Page 493 Valid names consist of any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. 7950 XRS Quality of Service Guide Page 493...
Page 494 — This parameter indicates that the tier 1 schedulers do not have a parent scheduler and the configuration of the parent under a tier 1 scheduler is blocked. Conversely, this parameter is blocked when any tier 1 scheduler has a parent configured. Page 494 7950 XRS Quality of Service Guide...
Page 495 This command creates a new scheduler or edits an existing scheduler within the scheduler policy tier. A scheduler defines bandwidth controls that limit each child (other schedulers and queues) associated with the 7950 XRS Quality of Service Guide Page 495...
Page 496 This safeguard is meant to avoid accidental creation of system objects (such as schedulers) while attempting to edit an object with a mistyped name or ID. The keyword has no effect when the object already exists. Page 496 7950 XRS Quality of Service Guide...
Page 497 A 0 (zero) weight value signifies that the child scheduler will receive bandwidth only after bandwidth is distributed to all other non-zero weighted children in the strict level. Values 0 to 100 Default 7950 XRS Quality of Service Guide Page 497...
Page 498 If the scheduler’s cir-level parameter retains the default (undefined) state, bandwidth is only allocated to the scheduler during the above CIR distribution phase. Children with the same strict cir-level are serviced according to their cir-weight. Values Undefined, 1 — 8 Default Undefined Page 498 7950 XRS Quality of Service Guide...
Page 499 (defined by the cir-level parameter). The weight is specified as an integer value from 0 to 100 with 100 being the highest weight. When the cir-weight parameter is set to a value of 0 (the default value), 7950 XRS Quality of Service Guide Page 499...
Page 500 The PIR in effect for a queue defines the maximum rate ate which the queue will be allowed to forward packets in a given second, thus shaping the queue’s output. Page 500 7950 XRS Quality of Service Guide...
Page 501 CIR and definable range is different for each class. The CIR in effect for a queue defines both its profile (in or out) marking level as well as the relative importance compared to other queues for scheduling purposes during congestion periods. Values 0 — 100000000, max, sum Default 7950 XRS Quality of Service Guide Page 501...
Page 502 This command does not have any affect when the port on which this port-scheduler-policy is configured is part of a LAG in link mode. Similarly when rates are configured as percent-active rates, the value of this object is irrelevant. Page 502 7950 XRS Quality of Service Guide...
Page 503 In a similar fashion, the percent-rate command causes any rate command values to be deleted. A policer’s rate may dynamically be changed back and forth from a percentage to an explicit rate at anytime. 7950 XRS Quality of Service Guide Page 503...
Page 504 8 priority levels starting with level 8 and moving down to level 1. Each level takes the offered load and distributes it to all child members that have a port-parent cir-level equal to the current priority level. (Any Page 504 7950 XRS Quality of Service Guide...
Page 505 When cir is not specified, all the available port or channel bandwidth may be allocated to the specified priority level during the within-cir pass. Values 1 — 40000000 (Kilobits per second (1,000 bits per second)) 7950 XRS Quality of Service Guide Page 505...
Page 506 Parameters pir-rate — Specifies the PIR rate. Values 1 — 800000000, max, in Kbps percent percent-rate — Specifies the percent rate. Values 0.01 — 100.00 Page 506 7950 XRS Quality of Service Guide...
Page 507 PIR value (based on the queue or schedulers rate command) less any bandwidth that was given to 7950 XRS Quality of Service Guide Page 507...
Page 508 If the cir-weight parameter is 1 or greater, the cir-level parameter comes into play. Values 1 — 100 (100 is the highest weight) Page 508 7950 XRS Quality of Service Guide...
Page 509: Table 29: Show Qos Scheduler-Policy Output Fields
Weight defines the relative weight of this queue in comparison to other child schedulers and queues while vying for bandwidth on the parent scheduler. 7950 XRS Quality of Service Guide Page 509...
Page 510 — Displays ingress SAP customer scheduler stats. egress — Displays egress SAP customer scheduler stats. detail — Displays detailed information. Output Show QoS Scheduler-Hierarchy Customer Output — The following table describes the customer scheduler hierarchy fields. Page 510 7950 XRS Quality of Service Guide...
Page 511 Specifies the Service Access Point (SAP) within the service where the policy is applied. Multi Service Site Specifies the multi-service site name. Orphan Queues Specifies the number of queues in an orphaned state. Hierarchy Displays the scheduler policy tree structure. 7950 XRS Quality of Service Guide Page 511...
Page 512: Table 30: Show Qos Schedule-Hierarchy Port Output Fields
Syntax scheduler-hierarchy sap sap-id [scheduler scheduler-name] [ingress | egress] [detail] Context show>qos Description This command displays the scheduler hierarchy per SAP. Parameters sap sap-id — Specifies the SAP assigned to the service. Page 512 7950 XRS Quality of Service Guide...
Page 513: Table 31: Show Qos Scheduler-Hierarchy Sap Output Fields
— The name of a scheduler configured in the config>qos>scheduler-policy>tier context. scheduler-stats customer Syntax scheduler-stats customer customer-id site customer-site-name [scheduler scheduler-name] [ingress | egress] Context show>qos Description This command displays scheduler statistics information. 7950 XRS Quality of Service Guide Page 513...
Page 514: Table 32: Show Qos Scheduler-Stats Customer Output Fields
Table 33: Show QoS Scheduler-Stats SAP Output Fields Label Description Displays the scheduler policy name. Scheduler Displays the number of packets forwarded. Forwarded Packets Displays the number of octets forwarded. Forwarded Octet Page 514 7950 XRS Quality of Service Guide...
Page 515 Table 33: Show QoS Scheduler-Stats SAP Output Fields (Continued) Label Description Displays the egress scheduler name(s). Ingress Schedulers Egress Schedulers Displays the ingress scheduler name(s). 7950 XRS Quality of Service Guide Page 515...
Page 516 Displays the port priority of orphaned queues and schedulers Orphan CIR-Lvl that are within-cir. Displays the weight of orphaned queues and schedulers that are Orphan CIR-Weight within-cir. Associations Displays associations related to the specified port scheduler policy. Page 516 7950 XRS Quality of Service Guide...
Page 517 50.00 level 1 percent-rate 10.00 percent-cir 10.00 level 2 percent-rate 20.00 percent-cir 20.00 level 3 percent-rate 30.00 percent-cir 30.00 level 4 percent-rate 40.00 percent-cir 40.00 level 5 percent-rate 50.00 percent-cir 50.00 7950 XRS Quality of Service Guide Page 517...
Page 518 : 40.00 Lvl4 CIR Percent : 40.00 Lvl5 PIR : max* Lvl5 CIR : max* Lvl5 PIR Percent : 50.00 Lvl5 CIR Percent : 50.00 Lvl6 PIR : max* Lvl6 CIR : max* Page 518 7950 XRS Quality of Service Guide...
Page 519 : 70.00 Lvl7 CIR Percent : 70.00 Lvl8 PIR : max* Lvl8 CIR : max* Lvl8 PIR Percent : 80.00 Lvl8 CIR Percent : 80.00 * means the value is inherited ------------------------------------------------------------------------------- 7950 XRS Quality of Service Guide Page 519...
Page 520: Clear Commands
ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. ingress — Display only the policy displayed on the ingress SAP. egress — Display only the policy displayed on the egress SAP. Page 520 7950 XRS Quality of Service Guide...
Page 521: Slope Qos Policies
Topics in this section include: • Overview on page 522 • Basic Configurations on page 523 • Default Slope Policy Values on page 526 • Deleting QoS Policies on page 527 7950 XRS Quality of Service Guide Page 521...
Page 522: Overview
For information about the tasks and commands necessary to access the command line interface and to configure and maintain your router, refer to CLI Usage chapter in the Basic System Configuration Guide. Page 522 7950 XRS Quality of Service Guide...
Page 523: Slope Qos Policies
The time average factor (TAF), a weighting exponent used to determine the portion of the shared buffer instantaneous utilization and shared buffer average utilization used to calculate the new shared buffer average utilization. 7950 XRS Quality of Service Guide Page 523...
Page 524 The following displays the slope policy configuration: ALA-7>config>qos# info #------------------------------------------ echo "QoS Slope/Queue Policies Configuration" #------------------------------------------ slope-policy "slopePolicy1" create description "Test" high-slope no shutdown exit low-slope no shutdown exit exit #------------------------------------------ ALA-7>config>qos# Page 524 7950 XRS Quality of Service Guide...
Page 525: Applying Slope Policies
The following CLI syntax example configures the PPP multilink pool: CLI Syntax: config>card>mda>access>egress>pool>slope-policy name Ports The following CLI syntax examples may be used to apply slope policies to ports: CLI Syntax: config>port>access>egress>pool>slope-policy name config>port>network>egress>pool>slope-policy name 7950 XRS Quality of Service Guide Page 525...
Page 526: Table 34: Slope Policy Defaults
The following output displays the default configuration: ALA-7>config>qos>slope-policy# info detail ---------------------------------------------- description "Default slope policy." high-slope shutdown start-avg 70 max-avg 90 max-prob 80 exit low-slope shutdown start-avg 50 max-avg 75 max-prob 80 exit time-average-factor 7 ---------------------------------------------- ALA-7>config>qos>slope-policy# Page 526 7950 XRS Quality of Service Guide...
Page 527: Deleting Qos Policies
The following CLI syntax example configures the PPP multilink pool: CLI Syntax: config>card>mda>access>egress>pool# no slope-policy name Ports The following CLI syntax examples can be used to remove slope policies from ports: CLI Syntax: config>port>access>egress>pool# no slope-policy name config>port>network>egress>pool# no slope-policy name 7950 XRS Quality of Service Guide Page 527...
Page 528 Deleting QoS Policies Remove a Policy from the QoS Configuration To delete a slope policy, enter the following command: CLI Syntax: config>qos# no slope-policy policy-id Example config>qos# no slope-policy slopePolicy1 Page 528 7950 XRS Quality of Service Guide...
Page 529: Copying And Overwriting Qos Policies
80 exit low-slope shutdown start-avg 50 max-avg 75 max-prob 80 exit time-average-factor 7 exit slope-policy "slopePolicy2" create description "Default slope policy." high-slope shutdown start-avg 70 max-avg 90 max-prob 80 exit low-slope 7950 XRS Quality of Service Guide Page 529...
Page 530 Copying and Overwriting QoS Policies shutdown start-avg 50 max-avg 75 max-prob 80 exit time-average-factor 7 exit #------------------------------------------ ALA-7>config>qos# Page 530 7950 XRS Quality of Service Guide...
Page 531: 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. 7950 XRS Quality of Service Guide Page 531...
Page 532 Editing QoS Policies Page 532 7950 XRS Quality of Service Guide...
Page 533: Slope Qos Policy Command Reference
— max-prob percent — no max-prob — start-avg percent — no start-avg — [no] shutdown — time-average-factor value — no time-average-factor Operational Commands config — qos — copy slope-policy src-name dst-name [overwrite] 7950 XRS Quality of Service Guide Page 533...
Page 534 Command Hierarchies Show Commands show — qos — slope-policy [slope-policy-name] [detail] Page 534 7950 XRS Quality of Service Guide...
Page 535 — A text string describing the entity. Allowed values are any string up to 80 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. 7950 XRS Quality of Service Guide Page 535...
Page 536 If overwrite is not specified, an error will occur if the destination policy ID exists. ALA-7>config>qos# copy slope-policy default sp1 MINOR: CLI Destination "sp1" exists - use {overwrite}. ALA-7>config>qos#overwrite Page 536 7950 XRS Quality of Service Guide...
Page 537 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. 7950 XRS Quality of Service Guide Page 537...
Page 538 Slope Policy QoS Commands A high value weights the new shared buffer average utilization calculation more to the previous shared buffer average utilization value. Values 0 — 15 Page 538 7950 XRS Quality of Service Guide...
Page 539 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. 7950 XRS Quality of Service Guide Page 539...
Page 540 1. A max-prob value of 80 represents 80% of 1, or a packet discard probability of 0.8. The no form of this command restores the max-prob value to the default setting. Default max-prob 80 — 80% maximum drop probability corresponding to the max-avg. Page 540 7950 XRS Quality of Service Guide...
Page 541 Syntax queue queue-id drop-rate num no queue queue-id Context config>qos>slope-policy>high-slope config>qos>slope-policy>low-slope Description Sets the low priority or high priority Random Early Detection (RED) slope drop-rate for the shared buffer per queue. 7950 XRS Quality of Service Guide Page 541...
Page 542 Specifies the ID of the queue for which the drop-rate is to be configured. queue-id — Values 1 — 8 Specifies the drop rate to be configured. drop-rate num — Values 0 — 7 Page 542 7950 XRS Quality of Service Guide...
Page 543: Table 35: Show Qos Slope Policy Output Fields
Specifies the high priority RED slope position for the maximum Max Prob. non-one packet discard probability value before the packet dis- card probability rises directly to one. 7950 XRS Quality of Service Guide Page 543...
Page 544 Start Avg : 30 Admin State : Enabled Max Avg : 40 Max Prob. : 100 ------------------------------------------------------------------------------- Associations ------------------------------------------------------------------------------- Object Type Object Id Application Pool ------------------------------------------------------------------------------- Port 1/1/1 Acc-Egr default =============================================================================== A:C# Page 544 7950 XRS Quality of Service Guide...
Page 545: Advanced Qos Policies
Topics in this section include: • Overview on page 546 • Basic Configurations on page 547 • Default Advanced Policy Values on page 549 • Deleting QoS Policies on page 550 7950 XRS Quality of Service Guide Page 545...
Page 546: Overview
For information about the tasks and commands necessary to access the command line interface and to configure and maintain your router, refer to CLI Usage chapter in the System Basic Configuration Guide. Page 546 7950 XRS Quality of Service Guide...
Page 547: Advanced Qos Policies
#------------------------------------------ echo "QoS Policies Configuration" #------------------------------------------ adv-config-policy "childPolicy1" create description "Test" child-control offered-measurement add percent 30 granularity percent 30 exit bandwidth-distribution above-offered-cap percent 5 granularity percent 5 exit exit exit #------------------------------------------ ALA-7>config>qos# 7950 XRS Quality of Service Guide Page 547...
Page 548: Applying Advanced Policies
CLI Syntax: qos sap-ingress 11 policer 1 adv-config-policy child1 queue 1 adv-config-policy child1 SAP Egress Use the following CLI syntax to apply advanced policies to an egress SAP. CLI Syntax: qos sap-egress 11 policer 1 adv-config-policy child1 queue 1 adv-config-policy child1 Page 548 7950 XRS Quality of Service Guide...
Page 549: Table 36: Advanced Policy Parameter Defaults
Advanced QoS Policies Default Advanced Policy Values The default policies cannot be edited or deleted. The following displays default advanced policy parameters: Table 36: Advanced Policy Parameter Defaults Field Default offered-measurement high-rate-hold-time time-average-factor sample-interval 7950 XRS Quality of Service Guide Page 549...
Page 550: Deleting Qos Policies
CLI Syntax: qos sap-ingress 11 policer 1 adv-config-policy child1 queue 1 no adv-config-policy SAP Egress Use the following CLI syntax to delete advanced policies from an egress SAP. CLI Syntax: qos sap-egress 11 policer 1 adv-config-policy child1 queue 1 no adv-config-policy Page 550 7950 XRS Quality of Service Guide...
Page 551: Copying And Overwriting Advanced Policies
You can change existing advanced 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. 7950 XRS Quality of Service Guide Page 551...
Page 552 Editing Advanced Policies Page 552 7950 XRS Quality of Service Guide...
Page 553: Advanced Qos Policy Command Reference
{percent percent-of-admin-pir | rate rate-in- kilobits-per-second} — [no] enqueue-on-pir-zero — [no] granularity {percent percent-of-admin-pir | rate rate-in- kilobits-per-second} [min-only] — [no] limit-pir-zero-drain — [no] lub-init-min-pir Operational Commands config — qos — copy adv-config-policy src-name dst-name [overwrite] 7950 XRS Quality of Service Guide Page 553...
Page 554 Command Hierarchies Show Commands show — qos — adv-config-policy [policy-name] [detail] Page 554 7950 XRS Quality of Service Guide...
Page 555 — A text string describing the entity. Allowed values are any string up to 80 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. 7950 XRS Quality of Service Guide Page 555...
Page 556 If overwrite is not specified, an error will occur if the destination policy ID exists. ALA-7>config>qos# copy adv-config-policy default sp1 MINOR: CLI Destination "sp1" exists - use {overwrite}. ALA-7>config>qos#overwrite Page 556 7950 XRS Quality of Service Guide...
Page 557 This command contains parameters that are intended to allow more precise control of the method that hierarchical virtual scheduling employs to emulate the effect of a scheduling context upon a member child queue or policer. 7950 XRS Quality of Service Guide Page 557...
Page 558 When a maximum PIR is in use on the child, the system attempts to interpret the maximum child forwarding rate. This rate could be very large if the child is associated with multiple ingress or egress ports. Page 558 7950 XRS Quality of Service Guide...
Page 559 A side effect of higher sensitivity (lower granularity) is that the virtual scheduler may need to adjust the 7950 XRS Quality of Service Guide Page 559...
Page 560 The max-decrement limit has a dampening effect to changes in the offered Page 560 7950 XRS Quality of Service Guide...
Page 561 The offered measurement that triggers the hold time is used when the hold timer expires unless a higher offered rate is seen in the interim. When a higher rate is 7950 XRS Quality of Service Guide Page 561...
Page 562 Prev_Offered_Rate. When taf-value is set to ‘0’, the adjustment is never applied. The no form of this command is used to remove the time average factor adjustments to new offered rate measurements. Page 562 7950 XRS Quality of Service Guide...
Page 563 (current offered rate is zero). Any inactive ‘fast start’ child that has a positive offered counter during a sampling period bypasses the normal sampling interval and does an immediate offered rate evaluation. 7950 XRS Quality of Service Guide Page 563...
Page 564 This command is used to limit the operationally configured shaping or policing rate on the child associated with the policy. After the parent virtual scheduler or policer control policy determines the appropriate rate Page 564 7950 XRS Quality of Service Guide...
Page 565 PIR. If a value of 0 is used, the system will disable the fair share increase function and only configure the actual distribution rate. Default None, an increase limit rate value must be specified when the rate qualifier is used. Values 0 — 100,000,000 7950 XRS Quality of Service Guide Page 565...
Page 566 When this command is not specified or removed, the system makes no attempt to round up the child’s determined operational PIR. The no form of this command is used to remove the operational PIR rounding behavior from all child Page 566 7950 XRS Quality of Service Guide...
Page 567 PIR. Enabling this command forces a minimum rate operational PIR to be applied to the queue for use by enqueued packets prior to an HQoS iteration. The no form of this command reverts to default behavior. 7950 XRS Quality of Service Guide Page 567...
Page 568 [policy-name] [detail] Context show>qos Description This command displays advanced QoS policy information. The name of the advanced QoS policy. Parameters policy-name — Displays detailed information about the advanced QoS policy. detail — Page 568 7950 XRS Quality of Service Guide...
Page 569: Class Fair Hierarchical Policing (Cfhp)
• Policer Enabled SAP QoS Policy Applicability on page 580 • Child Policer Parent Association on page 581 • Policer Interaction with Initial Profile, Discard Eligibility, and Ingress Priority on page 584 7950 XRS Quality of Service Guide Page 569...
Page 570: Introduction
9/1/4 ingress policer-control-policy "pcp" exit egress policer-control-policy "pcp" exit ---------------------------------------------- Example of a service using mss is as below: *A:Dut-A>config>service>vpls# pwc ------------------------------------------------------------------------------- Present Working Context : ------------------------------------------------------------------------------- <root> configure service Page 570 7950 XRS Quality of Service Guide...
Page 571 "mss1" egress qos 3 exit exit ---------------------------------------------- Here the above mentioned sap-egress qos policy "3" will have policers parented to arbiters which are configured in the policer-control-policy "pcp" as in example above. 7950 XRS Quality of Service Guide Page 571...
Page 572: Parent Policer Priority And Unfair Sensitive Discard Thresholds
See Figure 24 for a description of policer bucket rate and packet flow interaction with bucket depth. See Figure 25 for a description of parent policer bucket and priority thresholds. Page 572 7950 XRS Quality of Service Guide...
Page 573: Figure 24: Policer Bucket Rate And Packet Flow Interaction With Bucket Depth
3 Current burst Un-fair level discard for priority 3 Below priority 3 fair Parent PIR discard fair, so packets marked green (in-profile) OSSG342 Figure 25: Parent Policer Bucket and Priority Thresholds 7950 XRS Quality of Service Guide Page 573...
Page 574: Cfhp Ingress And Egress Use Cases
CFHP may also be used at egress. The reasons for utilizing egress CFHP may be to provide a non-jitter or latency inducing aggregate SLA for multiple ingress flows or simply to provide higher scale in the number of egress aggregate SLAs supported. Page 574 7950 XRS Quality of Service Guide...
Page 575: Post-Cfhp Queuing And Scheduling
The multipoint queues within the policy are created on the multicast paths; 16 multicast paths are supported by default with 28 on 7950 XRS systems and 7750 12-e systems, with the latter having setting “tools perform the system set-fabric-speed fabric-speed-b.”...
Page 576: Egress Cfhp Queuing
Any discards performed in the egress queue group queues will be reflected in the egress child policer’s discard counters and reported statistics assuming a discard counter capable stat-mode is configured for the child policer. Page 576 7950 XRS Quality of Service Guide...
Page 577: Cfhp Policer Control Policy
The root arbiter is special in that its strict priority levels directly represent the priority thresholds within the parent policer. 7950 XRS Quality of Service Guide Page 577...
Page 578: Tier 1 And Tier 2 Explicit Arbiters
This calculated PIR is used to override the child's defined PIR and is represented as the child's operational PIR. The calculated rate will never be greater than a child policer's provisioned rate. Page 578 7950 XRS Quality of Service Guide...
Page 579: Cfhp Child Policer Definition And Creation
When the last forwarding class is unmapped from the policer, all the instances of the policer on the SAPs to which the policy is applied are removed. 7950 XRS Quality of Service Guide Page 579...
Page 580: Policer Enabled Sap Qos Policy Applicability
Once a forwarding class is successfully mapped to a policer within the policy, attempting to apply the policy to a SAP or a where the policer cannot be created either due to lack of policer support or insufficient policer resources will fail. Page 580 7950 XRS Quality of Service Guide...
Page 581: Child Policer Parent Association
An orphaned policer functions in the same manner as a policer without a parent defined. An arbiter exists on a SAP when a policer-control-policy containing the arbiter is applied to the appropriate direction (ingress or egress) of the SAP. 7950 XRS Quality of Service Guide Page 581...
Page 582: Profile Capped Policers
Table 37 demonstrates how the CIR rate and initial profile of each packet affects the output of normal (non-profile-capped) and profile-capped mode policers. Page 582 7950 XRS Quality of Service Guide...
Page 583: Table 37: Effect Of Profile-Capped Mode On Cir Output
Green below Profile Yellow at or Yellow at or above CBS above CBS Egress Profile In Always Green Green below 2xCBS Yellow at or above 2xCBS Egress Profile Out Always Yellow Always Yellow 7950 XRS Quality of Service Guide Page 583...
Page 584: Policer Interaction With Initial Profile, Discard Eligibility, And Ingress Priority
When an egress policer’s CIR rate is set to 0 (or not defined), the policer will have no effect on the profile of packets offered to the policer. The soft-in-profile and hard-in-profile packets will remain in-profile while the soft-out-of-profile and hard-out-of-profile packets will remain out-of-profile. Page 584 7950 XRS Quality of Service Guide...
Page 585: Ingress 'Undefined' Initial Profile
At egress, an ingress policer output of ‘in-profile’ is treated as ‘soft-in-profile’ and an ingress policer output of ‘out-of-profile’ is treated as ‘soft-out-of-profile’. Each may be changed by egress profile reclassification or by an egress policer with a CIR rate defined. 7950 XRS Quality of Service Guide Page 585...
Page 586: Ingress Explicitly 'In-Profile' State Packet Handling Without Profile-Capped Mode
Unlike initially ‘in-profile’ packets, they do not consume the policer’s CIR bucket depth (accomplished by setting the ‘threshold-bc’ to 0) and thus do not have an impact on the amount of ‘undefined’ marked as ‘in-profile’ by the policer. Page 586 7950 XRS Quality of Service Guide...
Page 587 While explicit ‘out-of-profile’ packets remain out-of-profile within the ingress forwarding plane, the egress forwarding plane treats ingress out-of-profile packets as ‘soft-out-of-profile’ and the profile may be changed either by explicit profile reclassification or by an egress policer with a CIR rate defined. 7950 XRS Quality of Service Guide Page 587...
Page 588: Figure 26: Ingress Policer Threshold Determination And Output Behavior
Tail Drop = ‘High’ Tail Drop = ‘Low’ Tail Drop = ‘Low’ Ingress Queue Ingress Queue Ingress Queue Ingress Queue Ingress Queue al_0198 Figure 26: Ingress Policer Threshold Determination and Output Behavior Page 588 7950 XRS Quality of Service Guide...
Page 589: Egress Explicit Profile Reclassification
Egress Policer CIR Packet Handling with Profile Capped Mode When profile capped mode is enabled, the egress packet handling described in Egress Policer CIR Packet Handling without Profile Capped Mode on page 589 is modified in three aspects. 7950 XRS Quality of Service Guide Page 589...
Page 590 CIR not set to 0. Third, when the policer has a CIR = 0 rate (the default rate), all profile capped packets are treated as out-of-profile independent of the initial profile state. Page 590 7950 XRS Quality of Service Guide...
Page 591: Figure 27: Egress Policer Threshold Determination And Output Behavior
Tail Drop = ‘High’ Tail Drop = ‘Low’ Tail Drop = ‘High’ Not Possible with Egress Queue Egress Queue Egress Queue CIR Threshold = 0 Figure 27: Egress Policer Threshold Determination and Output Behavior 7950 XRS Quality of Service Guide Page 591...
Page 592: Ingress Child Policer Stat-Mode
(or maybe not at all based on the configured stat-mode). A policer is created with minimal counters sufficient to provide total offered and total discarded (the total forwarded is computed as the sum of the offered and discarded counters). The stat-mode Page 592 7950 XRS Quality of Service Guide...
Page 593 Egress policers also have a default CIR set to 0, but in the egress case a value of 0 disables policer profiling altogether. Egress packets on a CIR disabled egress policer retain their offered profile state (soft-in-profile, soft-out-of-profile, hard-in-profile or hard-out-of-profile). 7950 XRS Quality of Service Guide Page 593...
Page 594 (cir override can be performed using snmp access). Ingress supported stat-modes are: • no-stats • minimal - default • offered-profile-no-cir • offered-priority-no-cir • offered-limited-profile-cir • offered-profile-cir • offered-priority-cir • offered-total-cir • offered-profile-capped-cir • offered-limited-capped-cir Page 594 7950 XRS Quality of Service Guide...
Page 595: Egress Child Policer Stat-Mode
Details of the output showing the stat-modes for ingress and egress child policers can be found in the Class Fair Hierarchical Policing for SAPs section of the SR OS Advanced Configuration Guide. 7950 XRS Quality of Service Guide Page 595...
Page 596: Profile Preferred Mode Root Policers
CIR as FIR). In the direct-parented case (no intermediate arbiters present at all) the child policers do not need to have their offered rate polled as each policer will always have PIR equal to Page 596 7950 XRS Quality of Service Guide...
Page 597: Interaction Between Profile Preferred And Profile Capped Mode
Interaction Between Profile Preferred and Profile Capped Mode There is no requirement to restrict profile-preferred mode to only work when all children are profile-capped. 7950 XRS Quality of Service Guide Page 597...
Page 598 Interaction Between Profile Preferred and Profile Capped Mode Page 598 7950 XRS Quality of Service Guide...
Page 599: Command Reference
Command Reference Class Fair Hierarchical Policing (CFHP) Policy Command Reference Command Hierarchies 7950 XRS Quality of Service Guide Page 599...
Page 600 Command Hierarchies Page 600 7950 XRS Quality of Service Guide...
Page 601 QoS Commands Configuration Commands Generic Commands or max or 1—2000000000max or 1—2000000000 7950 XRS Quality of Service Guide Page 601...
Page 602 QoS Commands Page 602 7950 XRS Quality of Service Guide...
Page 603: Standards And Protocol Support
Standards and Protocol Support Note that the information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein. OSPF RFC 2858 Multiprotocol Extensions for BGP-4 RFC 1586 Guidelines for Running OSPF Over Frame Relay Networks...
Page 604: Standards And Protocols
Internet Protocol Version 6 (IPv6) (Helper Mode) RFC 5998 An Extension for EAP-Only Specification RFC 5307 IS-IS Extensions in Support of Authentication in IKEv2 RFC 4552 Authentication/Confidentiality Generalized Multi-Protocol Label for OSPFv3 Switching (GMPLS) Page 604 7950 XRS Quality of Service Guide...
Page 605 RFC 5059 Bootstrap Router (BSR) Identification Codes Mechanism for Protocol RFC 3209 Extensions to RSVP for RFC 3443 Time To Live (TTL) Independent Multicast (PIM) Tunnels Processing in Multi-Protocol Label Switching (MPLS) Networks 7950 XRS Quality of Service Guide Page 605...
Page 606 Engineering (RSVP-TE) Support for draft-ietf-vrrp-unified-spec-02 Virtual during failure events the Overlay Model Router Redundancy Protocol RFC4872 RSVP-TE Extensions in Version 3 for IPv4 and IPv6 Support of End to End GMPLS recovery Page 606 7950 XRS Quality of Service Guide...
Page 607 RFC 2684 Multiprotocol Encapsulation fr TCP RFC 4446 IANA Allocations for PWE3 over ATM Adaptation Layer 5 RFC 5508 NAT Behavioral Requirements RFC 4447 Pseudowire Setup and for ICMP Maintenance Using LDP 7950 XRS Quality of Service Guide Page 607...
Page 608 ETSI TS 101 329-5 Annex E extensions- RFC 4250 The Secure Shell (SSH) QoS Measurement for VoIP - Protocol Assigned Numbers Method for determining an RFC 4251 The Secure Shell (SSH) Protocol Architecture Page 608 7950 XRS Quality of Service Guide...
Page 609 Listener Discovery Protocol Information Base RFC 3164 Syslog draft-ietf-mpls-ldp-mib-07 Definitions of RFC 3273 HCRMON-MIB Managed Objects for the RFC 3411 An Architecture for Multiprotocol Label Switching, Describing Simple Network Label Distribution Protocol (LDP) 7950 XRS Quality of Service Guide Page 609...
Page 610 Standards and Protocols Page 610 7950 XRS Quality of Service Guide...
Page 611 Customer documentation and product support Customer documentation http://documentation.alcatel-lucent.com Technical support http://support.alcatel-lucent.com Documentation feedback documentation.feedback@alcatel-lucent.com...
Page 612 © 2015 Alcatel-Lucent. All rights reserved. 3HE 09868 AAAA TQZZA 01...