Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - QUALITY OF SERVICE CONFIGURATION GUIDE 2010-09-22 Configuration Manual
  1. Manuals
  2. Brands
  3. Juniper Manuals
  4. Software
  5. JUNOSE SOFTWARE FOR E SERIES 11.3.X - QUALITY OF SERVICE CONFIGURATION GUIDE...
  6. Configuration manual
Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - QUALITY OF SERVICE CONFIGURATION GUIDE 2010-09-22 Configuration Manual

Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - QUALITY OF SERVICE CONFIGURATION GUIDE 2010-09-22 Configuration Manual

Software for e series broadband services routers quality of service configuration guide
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
JunosE™ Software
for E Series™ Broadband
Services Routers
Quality of Service Configuration Guide
Release
11.3.x
Published: 2010-09-22
Copyright © 2010, Juniper Networks, Inc.

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the JUNOSE SOFTWARE FOR E SERIES 11.3.X - QUALITY OF SERVICE CONFIGURATION GUIDE 2010-09-22 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - QUALITY OF SERVICE CONFIGURATION GUIDE 2010-09-22

Summary of Contents for Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - QUALITY OF SERVICE CONFIGURATION GUIDE 2010-09-22

  • Page 1 JunosE™ Software for E Series™ Broadband Services Routers Quality of Service Configuration Guide Release 11.3.x Published: 2010-09-22 Copyright © 2010, Juniper Networks, Inc.
  • Page 2 Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are owned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312, 6,429,706, 6,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.
  • Page 3 REGARDING LICENSE TERMS. 1. The Parties. The parties to this Agreement are (i) Juniper Networks, Inc. (if the Customer’s principal office is located in the Americas) or Juniper Networks (Cayman) Limited (if the Customer’s principal office is located outside the Americas) (such applicable entity being referred to herein as “Juniper”), and (ii) the person or organization that originally purchased from Juniper or an authorized Juniper reseller the applicable...
  • Page 4 Customer shall be liable for any such violations. The version of the Software supplied to Customer may contain encryption or other capabilities restricting Customer’s ability to export the Software without an export license. Copyright © 2010, Juniper Networks, Inc.
  • Page 5 (including Juniper modifications, as appropriate) available upon request for a period of up to three years from the date of distribution. Such request can be made in writing to Juniper Networks, Inc., 1194 N. Mathilda Ave., Sunnyvale, CA http://www.gnu.org/licenses/gpl.html...
  • Page 6 Copyright © 2010, Juniper Networks, Inc.
  • Page 7 Subinterfaces ........... . 169 Chapter 21 Configuring QoS for 802.3ad Link Aggregation Groups ....175 Copyright © 2010, Juniper Networks, Inc.
  • Page 8 Index ............341 viii Copyright © 2010, Juniper Networks, Inc.

  • Page 9: Table Of Contents

    Dynamic Oversubscription ........18 Copyright © 2010, Juniper Networks, Inc.
  • Page 10 Configuring a Scheduler Profile for a Scheduler Node or Queue ....48 Using Expressions for Bandwidth and Burst Values in a Scheduler Profile ..48 Copyright © 2010, Juniper Networks, Inc.
  • Page 11 Bandwidth Allocation for Simple Shared Shaping ..... 75 Simple Shared Shaping on the Best-Effort Scheduler Node ... . . 75 Copyright © 2010, Juniper Networks, Inc.
  • Page 12 Attaching a QoS Profile to an ATM VP ......128 Copyright © 2010, Juniper Networks, Inc.
  • Page 13 Monitoring QoS Configurations for Ethernet ......174 Copyright © 2010, Juniper Networks, Inc.
  • Page 14 Interface Set Parents and Types ........197 Sample Interface Columns and Scheduler Hierarchies ....197 Copyright © 2010, Juniper Networks, Inc.
  • Page 15 Range of QoS Parameters ........219 Copyright © 2010, Juniper Networks, Inc.
  • Page 16 Overriding the QoS Shaping Mode ....... . 265 Module Types and Capabilities for QoS Cell Mode Application ..266 Copyright © 2010, Juniper Networks, Inc.
  • Page 17 Monitoring the QoS Profiles Attached to an Interface ..... 320 Monitoring the Configuration of QoS Port-Type Profiles ....321 Copyright © 2010, Juniper Networks, Inc. xvii...
  • Page 18 Index ............341 xviii Copyright © 2010, Juniper Networks, Inc.
  • Page 19 Figure 21: Hierarchical Simple Shared Shaping over Ethernet ....82 Chapter 11 Configuring Variables in the Simple Shared Shaping Algorithm ..85 Copyright © 2010, Juniper Networks, Inc.
  • Page 20 Configuring QoS for L2TP Sessions ....... . . 187 Copyright © 2010, Juniper Networks, Inc.
  • Page 21 Encapsulations ..........276 Copyright © 2010, Juniper Networks, Inc.
  • Page 22 JunosE 11.3.x Quality of Service Configuration Guide xxii Copyright © 2010, Juniper Networks, Inc.

  • Page 23: Part 3 Scheduling And Shaping Traffic

    Configuring Shadow Nodes for Queue Management ....141 Table 15: Shadow Node Consumption of Node and Queue Resources ..144 Copyright © 2010, Juniper Networks, Inc. xxiii...

  • Page 24: Part 5 Interface Solutions For Qos

    Table 40: show scheduler-profile Output Fields ......310 xxiv Copyright © 2010, Juniper Networks, Inc.
  • Page 25 Table 56: show qos-parameter Output Fields ......334 Table 57: show qos-parameter-define Output Fields ..... . 335 Copyright © 2010, Juniper Networks, Inc.
  • Page 26 JunosE 11.3.x Quality of Service Configuration Guide xxvi Copyright © 2010, Juniper Networks, Inc.

  • Page 27: About The Documentation

    Audience This guide is intended for experienced system and network specialists working with Juniper Networks E Series Broadband Services Routers in an Internet access environment. E Series and JunosE Text and Syntax Conventions Table 1 on page xxviii defines notice icons used in this documentation.

  • Page 28: Table 1: Notice Icons

    Indicates that you must press two or more Press Ctrl + b. keys simultaneously. Syntax Conventions in the Command Reference Guide Plain text like this Represents keywords. terminal length Italic text like this Represents variables. mask, accessListName xxviii Copyright © 2010, Juniper Networks, Inc.

  • Page 29: Obtaining Documentation

    CD-ROMs or DVD-ROMs, see the Portable Libraries page at http://www.juniper.net/techpubs/resources/index.html Copies of the Management Information Bases (MIBs) for a particular software release are available for download in the software image bundle from the Juniper Networks Web site at http://www.juniper.net/...

  • Page 30: Self-Help Online Tools And Resources

    7 days a week, 365 days a year. Self-Help Online Tools and Resources For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called the Customer Support Center (CSC) that provides you with the following features: Find CSC offerings: http://www.juniper.net/customers/support/...

  • Page 31: Qos On The E Series Router

    PART 1 QoS on the E Series Router Quality of Service Overview on page 3 Copyright © 2010, Juniper Networks, Inc.
  • Page 32 JunosE 11.3.x Quality of Service Configuration Guide Copyright © 2010, Juniper Networks, Inc.

  • Page 33: Quality Of Service Overview

    QoS is a suite of features that configure queuing and scheduling on the forwarding path of the Juniper Networks E Series Broadband Services Routers. QoS provides a level of predictability and control beyond the best-effort delivery that the router provides by default.

  • Page 34: Qos Audience

    See the ERX Module Guide for modules supported on ERX7xx models, ERX14xx models, and the Juniper Networks ERX310 Broadband Services Router. See the E120 and E320 Module Guide for modules supported on the Juniper Networks E120 and E320 Broadband Services Routers.

  • Page 35: Interface Specifiers

    Also known as best-effort node. Cell delay variation. Measures the difference between a cell’s expected and actual transfer delay. Determines the amount of jitter. CDVT Cell delay variation tolerance. Specifies the acceptable tolerance of CDV (jitter). Copyright © 2010, Juniper Networks, Inc.
  • Page 36 Queues are stacked above scheduler nodes in a hierarchy. The root node is associated with a channel or physical port. Shaping rate Bandwidth in a queue or node can be throttled to a specified rate. Copyright © 2010, Juniper Networks, Inc.

  • Page 37: Qos Features

    Collection of QoS commands that specify queue profiles, drop profiles, scheduler profiles, and statistics profiles in combination with interface types. Queue profile Template that specifies the buffering and tail-dropping behavior of an egress queue. Copyright © 2010, Juniper Networks, Inc.
  • Page 38 The intent is to trigger TCP congestion avoidance in a random set of TCP flows before congestion becomes severe and causes tail dropping on a large number of flows. Copyright © 2010, Juniper Networks, Inc.

  • Page 39: Configuring Qos On The E Series Router

    Attach the QoS profile to one or more interfaces, or specify the profile as a QoS port-type profile for a given interface type. See “Queuing and Buffer Management Overview” on page 17. QoS References For more information about QoS, see the following resources: Copyright © 2010, Juniper Networks, Inc.
  • Page 40 DSL Forum Technical Report (TR)-059—DSL Evolution - Architecture Requirements for the Support of QoS-Enabled IP Services Floyd, S., and Jacobson, V. Random Early Detection for Congestion Avoidance. IEEE/ACM Transactions on Networking 1(4), August 1993 Copyright © 2010, Juniper Networks, Inc.

  • Page 41: Classifying, Queuing, And Dropping Traffic

    Defining Service Levels with Traffic Classes and Traffic-Class Groups on page 13 Configuring Queue Profiles for Buffer Management on page 17 Configuring Dropping Behavior with RED and WRED on page 25 Gathering Statistics for Rates and Events in the Queue on page 37 Copyright © 2010, Juniper Networks, Inc.
  • Page 42 JunosE 11.3.x Quality of Service Configuration Guide Copyright © 2010, Juniper Networks, Inc.

  • Page 43: Defining Service Levels With Traffic Classes And Traffic-Class Groups

    The router assigns packets to the best-effort class in each of the following cases: You do not create any other traffic classes. Packets are not classified into a traffic class. Copyright © 2010, Juniper Networks, Inc.

  • Page 44: Traffic-Class Groups Overview

    Create a traffic class by assigning a name that represents the type of service and enter Traffic Class Configuration mode. host1(config)#traffic-class low-loss1 host1(config-traffic-class)# The traffic class name can be up to 31 characters. It cannot include spaces. Copyright © 2010, Juniper Networks, Inc.

  • Page 45: Configuring Traffic-Class Groups That Define Service Levels

    (Optional) Specify strict-priority scheduling across the fabric for queues in the traffic class. host1(config-traffic-class)#fabric-strict-priority (Optional) For Juniper Networks ERX1440, E120 , and E320 Broadband Services Routers, specify the relative weight for queues in the traffic class in the fabric. host1(config-traffic-class)#fabric-weight 12 Fabric weight controls the bandwidth of fabric queues associated with the traffic class.

  • Page 46: Service

    Monitoring Traffic Classes and Traffic-Class Groups for Defined Levels of Service To monitor traffic classes and traffic-class groups: Monitoring Service Levels with Traffic Classes on page 296 Monitoring Service Levels with Traffic-Class Groups on page 297 Copyright © 2010, Juniper Networks, Inc.

  • Page 47: Configuring Queue Profiles For Buffer Management

    When egress packet memory is in low demand, a more liberal buffer management strategy is used to provide active queues with more access to the shared memory resource. Copyright © 2010, Juniper Networks, Inc.

  • Page 48: Static Oversubscription

    NOTE: All color-based thresholds vary in proportion to the dynamic queue length. Related Configuring Queue Profiles to Manage Buffers and Thresholds on page 22 Documentation Guidelines for Managing Queue Thresholds on page 19 Guidelines for Managing Buffers on page 20 Copyright © 2010, Juniper Networks, Inc.

  • Page 49: Memory Requirements For Queue And Buffers

    Configuring a maximum queue threshold enables the system to allocate more buffers to other queues in the system. Video queues are similar but because they are higher bandwidth, they might require higher maximum committed thresholds. Copyright © 2010, Juniper Networks, Inc.

  • Page 50: Guidelines For Configuring A Minimum Threshold

    JunosE Software uses 128-byte buffers. When setting very small queue thresholds, keep the following guidelines in mind: Copyright © 2010, Juniper Networks, Inc.

  • Page 51: Guidelines For Managing Buffer Starvation

    When the heavy weight node finally transmits, it dequeues all buffers, but it cannot dequeue the packets that were dropped. You do not achieve the expected bandwidth based on scheduler profile weights. Copyright © 2010, Juniper Networks, Inc.

  • Page 52: Configuring Queue Profiles To Manage Buffers And Thresholds

    To configure a minimal level of buffering or to limit the buffering in queues, set a maximum queue length. For example, if you want to control latency by configuring Copyright © 2010, Juniper Networks, Inc.
  • Page 53 Queuing and Buffer Management Overview on page 17 Documentation Guidelines for Managing Queue Thresholds on page 19 Guidelines for Managing Buffers on page 20 Memory Requirements for Queue and Buffers on page 19 buffer-weight committed-length Copyright © 2010, Juniper Networks, Inc.

  • Page 54: Monitoring Queues And Buffers

    JunosE 11.3.x Quality of Service Configuration Guide conformed-fraction conformed-length exceeded-fraction exceeded-length queue-profile Monitoring Queues and Buffers To monitor queues and buffers, see: Monitoring Queue Thresholds on page 298 Monitoring Queue Profiles on page 301 Copyright © 2010, Juniper Networks, Inc.

  • Page 55: Configuring Dropping Behavior With Red And Wred

    TCP flows before congestion becomes severe and causes tail dropping on a large number of flows. Tail dropping can lead to TCP slow-starts, and tail dropping on a large number of flows results in global synchronization. Copyright © 2010, Juniper Networks, Inc.

  • Page 56: Red And Wred Overview

    RED drops packets with increasing frequency, up to the maximum drop probability. When the average queue length exceeds the maximum drop threshold, all packets are dropped. Figure 2 on page 26 shows this behavior. Figure 2: Packets Dropped as Queue Length Increases Copyright © 2010, Juniper Networks, Inc.

  • Page 57: Configuring Red

    (Optional) Set the minimum and maximum threshold for conformed traffic. host1(config-drop-profile)#conformed-threshold percent 25 90 5 (Optional) Set the minimum and maximum threshold for exceeded traffic. host1(config-drop-profile)#exceeded-threshold percent 20 90 6 The thresholds specify a linear relationship between average queue length and drop probability. Copyright © 2010, Juniper Networks, Inc.

  • Page 58: Example: Configuring Average Queue Length For Red

    The following drop profiles result in identical behavior: host1(config)#drop-profile colorblind1 host1(config-drop-profile)#committed-threshold percent 30 90 5 host1(config-drop-profile)#exit host1(config)#drop-profile colorblind2 host1(config-drop-profile)#committed-threshold percent 30 90 5 Copyright © 2010, Juniper Networks, Inc.

  • Page 59: Example: Configuring Color-Blind Red

    100000 100000 host1(config-queue)#conformed-fraction 100 host1(config-queue)#exceeded-fraction 100 To achieve the same drop treatment for each color, you can specify color-blind RED in combination with a color-sensitive queue profile, as shown in Figure 4 on page 30. Copyright © 2010, Juniper Networks, Inc.

  • Page 60: Configuring Wred

    WRED is not supported on the ES2 10G Uplink LM. On the ES2 10G LM, you must configure WRED in one of the 15 configurable drop profiles; you cannot configure its default drop profile. Copyright © 2010, Juniper Networks, Inc.
  • Page 61 30 90 4 (Optional) Set the minimum and maximum threshold for conformed traffic. host1(config-drop-profile)#conformed-threshold percent 25 90 5 (Optional) Set the minimum and maximum threshold for exceeded traffic. host1(config-drop-profile)#exceeded-threshold percent 20 90 6 Copyright © 2010, Juniper Networks, Inc.

  • Page 62: Example: Configuring Different Treatment Of Colored Packets For Wred

    You can define different dropping behaviors for each traffic class in the router. By doing so, you can assign less aggressive drop profiles to higher-priority queues and more aggressive drop profiles to lower-priority queues. Figure 6 on page 33 shows an example Copyright © 2010, Juniper Networks, Inc.

  • Page 63: Example: Configuring Wred And Dynamic Queue Thresholds

    In general, you use queues as follows: Fixed-size queues on core routers and core-facing interfaces where the number of queues is relatively small (tens or hundreds, but not thousands). Copyright © 2010, Juniper Networks, Inc.
  • Page 64 To configure WRED to run on queues whose limits dynamically expand and contract, use the percent keyword when you configure thresholds in a drop profile. For example: host1(config)#drop-profile internetDropProfile host1(config-drop-profile)#average-length-exponent 9 host1(config-drop-profile)#committed-threshold percent 30 90 4 host1(config-drop-profile)#conformed-threshold percent 25 90 5 host1(config-drop-profile)#exceeded-threshold percent 20 90 6 Copyright © 2010, Juniper Networks, Inc.

  • Page 65: Monitoring Red And Wred

    Configuring WRED on page 30 Documentation Dropping Behavior Overview on page 25 RED and WRED Overview on page 26 Monitoring RED and WRED To monitor drop profiles, see: Monitoring Drop Profiles for RED and WRED on page 302 Copyright © 2010, Juniper Networks, Inc.
  • Page 66 JunosE 11.3.x Quality of Service Configuration Guide Copyright © 2010, Juniper Networks, Inc.

  • Page 67: Gathering Statistics For Rates And Events In The Queue

    30-second rate period results in rate statistics being gathered over 30-second time segments. Forwarding rate threshold—Threshold for forwarding rate events. A forwarding-rate event is counted whenever the forwarding rate exceeds the specified threshold. Copyright © 2010, Juniper Networks, Inc.

  • Page 68: Rate Statistics

    MIB. However, using SNMP to obtain queue-level statistics consumes significant network bandwidth because SNMP polls large volumes of data frequently. As an alternative to using the SNMP MIB, you can use the bulkstats statistics application. Copyright © 2010, Juniper Networks, Inc.

  • Page 69: Configuring Statistic Profiles For Qos

    Rate period range is 1–43200 seconds. Reference the statistics profile by a QoS profile. host1(config)#qos-profile qospro-3 host1(config-qos-profile)#ip queue traffic-class tc1 scheduler-profile sp1 statistics-profile statpro-5 Attach the QoS profile to the appropriate interface. host1(config)#interface gigabitEthernet 1/0 host1(config-subif)#qos-profile qospro-3 Copyright © 2010, Juniper Networks, Inc.

  • Page 70: Configuring Event Statistics

    Drop rate threshold range is 0–1073741824 bps; default is no threshold. (Optional) Set a threshold for conformed (yellow) packets. host1(config-statistics-profile)#conformed-drop-threshold 4000000 Drop rate threshold range is 0–1073741824 bps; default is no threshold. (Optional) Set a threshold for exceeded (red) packets. Copyright © 2010, Juniper Networks, Inc.

  • Page 71: Clearing Qos Statistics On The Egress Queue

    3/0 explicit traffic-class class15 Use the explicit keyword to clear queues only on the specified interface and not queues stacked above the interface. Related Monitoring QoS Statistics for Rates and Events on page 42 Documentation clear egress-queue Copyright © 2010, Juniper Networks, Inc.

  • Page 72: Clearing Qos Statistics On The Fabric Queue

    Monitoring Forwarding and Drop Events on the Egress Queue on page 313 Monitoring Forwarding and Drop Rates on the Egress Queue on page 314 Monitoring Queue Statistics for the Fabric on page 318 Monitoring the Configuration of Statistics Profiles on page 319 Copyright © 2010, Juniper Networks, Inc.

  • Page 73: Scheduling And Shaping Traffic

    Configuring Variables in the Simple Shared Shaping Algorithm on page 85 Configuring Compound Shared Shaping of Traffic on page 95 Configuring Implicit and Explicit Constituent Selection for Shaping on page 103 Monitoring a QoS Scheduler Hierarchy on page 117 Copyright © 2010, Juniper Networks, Inc.
  • Page 74 JunosE 11.3.x Quality of Service Configuration Guide Copyright © 2010, Juniper Networks, Inc.

  • Page 75: Qos Scheduler Hierarchy Overview

    The scheduler then selects a second-level node from the group of nodes that are stacked above the selected first-level node. This selection is also based on the allocated bandwidth. Finally, the scheduler selects a queue from the group of queues stacked above the second-level node. Copyright © 2010, Juniper Networks, Inc.

  • Page 76: Shaping Rates, Assured Rates, And Relative Weights In A Scheduler

    2-to-1 ratio. Similarly, if the bandwidth were oversubscribed and only 30 Mbps were available, this amount would also be allocated to the two nodes at the 2-to-1 ratio, with Node A getting 20 Mbps and Node B getting 10 Mbps. Copyright © 2010, Juniper Networks, Inc.

  • Page 77: Hierarchy

    See “Configuring Implicit Constituents for Simple or Compound Shared Shaping” on page 110 and “Configuring Explicit Constituents for Simple or Compound Shared Shaping” on page 115. Reference the scheduler profile in a QoS profile and apply to an interface. Copyright © 2010, Juniper Networks, Inc.

  • Page 78: Configuring A Scheduler Profile For A Scheduler Node Or Queue

    You specify an expression consisting of an operand, followed by zero or more [ operator, operand ] pairs. You can specify bandwidth as a percentage and burst in milliseconds or bytes by using expressions with the shaping-rate, shared-shaping-rate, assured-rate, and weight commands. Copyright © 2010, Juniper Networks, Inc.
  • Page 79 Documentation for QoS parameters, see Scheduler Profiles and Parameter Expressions for QoS Administrators on page 221 Configuring Rate Shaping for a Scheduler Node or Queue on page 52 Configuring Port Shaping on page 52 Copyright © 2010, Juniper Networks, Inc.
  • Page 80 Configuring an Assured Rate for a Scheduler Node or Queue on page 54 Configuring the HRR Weight for a Scheduler Node or Queue on page 56 Configuring Simple Shared Shaping on page 77 Configuring Compound Shared Shaping on page 96 Copyright © 2010, Juniper Networks, Inc.

  • Page 81: Configuring Rates And Weights In The Scheduler Hierarchy

    With port shaping, you can configure scheduler nodes at the port level, as shown in Figure 9 on page 51. Figure 9: Port Shaping on an Ethernet Module Copyright © 2010, Juniper Networks, Inc.

  • Page 82: Configuring Rate Shaping For A Scheduler Node Or Queue

    Configuring a Scheduler Profile for a Scheduler Node or Queue on page 48 scheduler-profile shaping-rate Configuring Port Shaping To configure port-shaping: Configure the scheduler profile and the shaping rate. host1(config)#scheduler-profile 80mbps host1(config-scheduler-profile)#shaping-rate 80000000 host1(config-scheduler-profile)#exit Copyright © 2010, Juniper Networks, Inc.

  • Page 83: Static And Hierarchical Assured Rate Overview

    This recalculation is necessary because of the number of scheduler nodes and queues that may be dynamically created or deleted through applications such as Copyright © 2010, Juniper Networks, Inc.

  • Page 84: Configuring An Assured Rate For A Scheduler Node Or Queue

    You can configure the effective weight of the scheduler node or queue by configuring a static assured rate or a hierarchical assured rate (HAR). HAR dynamically adjusts the available bandwidth for a scheduler node based on the creation and deletion of other scheduler nodes. Copyright © 2010, Juniper Networks, Inc.

  • Page 85: Configuring A Static Assured Rate

    To change an assured rate to an HRR weight: Create a scheduler profile. host1(config)#scheduler-profile static host1(config-scheduler-profile)# Delete the configured assured rate. host1(config-scheduler-profile)#no assured-rate The assured rate in the scheduler profile reverts to using the HRR weight specification. Copyright © 2010, Juniper Networks, Inc.

  • Page 86: Configuring The Hrr Weight For A Scheduler Node Or Queue

    For more information about specifying an expression that you can reference within a scheduler profile, see Using Expressions for Bandwidth and Burst Values in a Scheduler Profile on page 48 Relative Strict-Priority Scheduling Overview on page 58 scheduler-profile weight Copyright © 2010, Juniper Networks, Inc.

  • Page 87: Configuring Strict-Priority Scheduling

    If multiple queues above the strict-priority node have packets, the HRR algorithm selects which strict-priority queue is scheduled next. Figure 11 on page 58 illustrates an example of a QoS scheduler’s hierarchy. Copyright © 2010, Juniper Networks, Inc.

  • Page 88: Relative Strict-Priority Scheduling Overview

    Relative strict priority provides low latency only if you undersubscribe the port by shaping all VCs on the port so that the sum of the shaping rates is less than the port rate. The Copyright © 2010, Juniper Networks, Inc.

  • Page 89: Comparison Of True Strict Priority With Relative Strict Priority Scheduling

    Figure 12: True Strict-Priority Configuration This configuration provides low latency for the strict-priority queues, irrespective of the state of the nonstrict queues. The worst-case latency for a strict packet caused by a Copyright © 2010, Juniper Networks, Inc.

  • Page 90: Schedulers And Relative Strict Priority

    HRR scheduler and shape the aggregate for the VC in the SAR scheduler. VC backpressure affects only the nonstrict traffic for the VC. For this type of configuration, you should shape the relative strict traffic for each VC in the HRR Copyright © 2010, Juniper Networks, Inc.

  • Page 91: Oversubscribing Atm Ports

    HRR scheduler to obtain approximate strict-priority scheduling. Note that under conditions of low VC bandwidth and large packet sizes, latency and jitter increase because of the inherent propagation delay of large packets over a small shaping rate. The following Copyright © 2010, Juniper Networks, Inc.

  • Page 92: Zero-Weight Queues

    In Figure 14 on page 63, the VC node is shaped in the HRR scheduler to 1 Mbps to limit the aggregate traffic for the subscriber. The relative strict traffic is shaped to 500 Kbps. Copyright © 2010, Juniper Networks, Inc.

  • Page 93: Configuring Strict-Priority Scheduling

    Configure the auto-strict-priority traffic-class group, and add the traffic classes that must receive strict-priority scheduling to the group. host1(config)#traffic-class-group Strict-priority auto-strict-priority host1(config-traffic-class-group)#traffic-class Low-latency-1 host1(config-traffic-class-group)#traffic-class Low-latency-2 host1(config-traffic-class-group)#exit Create a scheduler profile for strict-priority traffic and configure the shaping rate. host1(config)#scheduler-profile strictPriorityBandwidth host1(config-scheduler-profile)#shaping-rate 20000000 host1(config-scheduler-profile)#exit Copyright © 2010, Juniper Networks, Inc.

  • Page 94: Figure 15: Sample Strict-Priority Scheduling Hierarchy

    For more information about specifying an expression that you can reference within a scheduler profile, see Using Expressions for Bandwidth and Burst Values in a Scheduler Profile on page 48 group node qos-profile queue scheduler-profile shaping-rate Copyright © 2010, Juniper Networks, Inc.

  • Page 95: Configuring Relative Strict-Priority Scheduling For Aggregate Shaping Rates

    This configuration creates the hierarchy shown in Figure 16 on page 66. Copyright © 2010, Juniper Networks, Inc.

  • Page 96: Figure 16: Sample Relative Strict-Priority Scheduler Hierarchy

    For more information about specifying an expression that you can reference within a scheduler profile, see Using Expressions for Bandwidth and Burst Values in a Scheduler Profile on page 48 node qos-profile scheduler-profile shaping-rate weight Copyright © 2010, Juniper Networks, Inc.

  • Page 97: Shared Shaping Overview

    When determining a shared shaping rate, the system includes all bytes in Layer 2 encapsulations. The packets that are included in the rate depend on the node specified. For example, rates for an Ethernet node include the Ethernet and VLAN encapsulations. Copyright © 2010, Juniper Networks, Inc.

  • Page 98: Shared Shaper Terms

    Software-assisted mechanism that measures the rate of active constituents, and shapes the rate of the best-effort node or queue to the residual shared-shaping rate. Related For definitions of other common QoS terms, see QoS Terms on page 5 Documentation Copyright © 2010, Juniper Networks, Inc.

  • Page 99: How Shared Shaping Works

    Compound shared shaping responds to changes in traffic rates more rapidly than simple shared shaping, in the order of milliseconds. You can use line modules with the EFA2 ASIC or the TFA ASIC. Copyright © 2010, Juniper Networks, Inc.

  • Page 100: Active Constituents For Shared Shaping

    Shared Shaping and Best-Effort Queues and Nodes A scheduler profile that includes a shared-shaping rate cannot be associated with a queue other than the best-effort queue or a node other than the best-effort node. Copyright © 2010, Juniper Networks, Inc.

  • Page 101: Atm And Shared Shaping

    Beginning with JunosE Release 6.1.0, low-CDV mode causes SAR shaping of VCs and VPs only when you specify the shared-shaping-rate command for the best-effort VC or VP node in the HRR scheduler. Copyright © 2010, Juniper Networks, Inc.

  • Page 102: Logical Interface Traffic Carried In Other Queues

    Traffic in the strict-priority traffic-class group can starve out other traffic competing within the shared shaper. You might want to configure an individual shaping rate for strict-priority queues, thus reserving the remaining shared bandwidth for nonstrict traffic. Copyright © 2010, Juniper Networks, Inc.

  • Page 103: Oversubscription And Shared Shaping

    Configuring Simple Shared Shaping on page 77 Configuring Compound Shared Shaping on page 96 Configuring Implicit Constituents for Simple or Compound Shared Shaping on page 110 Configuring Explicit Constituents for Simple or Compound Shared Shaping on page 115 Copyright © 2010, Juniper Networks, Inc.
  • Page 104 JunosE 11.3.x Quality of Service Configuration Guide Copyright © 2010, Juniper Networks, Inc.

  • Page 105: Configuring Simple Shared Shaping Of Traffic

    If you instead configure the shared-shaping rate on the best-effort node, the hierarchical scheduler allocates bandwidth between multiple data queues based on their relative weight and assured rate. Copyright © 2010, Juniper Networks, Inc.

  • Page 106: Simple Shared Shaping For Triple-Play Networks

    VC 3 is configured for data, voice, and video. The shared shaper is configured on the best-effort node or queue for VC 1; the corresponding voice queue for VC 1 shares the configured rate. Figure 18: Simple Shared Shaping over ATM Copyright © 2010, Juniper Networks, Inc.

  • Page 107: Configuring Simple Shared Shaping

    Configure the traffic classes and traffic-class groups. See “Configuring Traffic Classes That Define Service Levels” on page 14 and “Configuring Traffic-Class Groups That Define Service Levels” on page 15. To configure simple shared shaping: Create the scheduler profile. Copyright © 2010, Juniper Networks, Inc.
  • Page 108 Attach the profile to the interface. (config)#interface atm 11/0.10 (config-subif)#qos-profile subscriber-default-mode (config-scheduler-profile)#exit Related Simple Shared Shaping Overview on page 75 Documentation Guidelines for Configuring Simple and Compound Shared Shaping on page 70 Copyright © 2010, Juniper Networks, Inc.

  • Page 109: Example: Simple Shared Shaping For Atm Vcs

    (config)#traffic-class voice (config-traffic-class)#fabric-strict-priority (config-traffic-class)#exit (config)#traffic-class video (config-traffic-class)#exit (config)#traffic-class-group EF auto-strict-priority (config-traffic-class-group)#traffic-class voice (config-traffic-class-group)#exit ((config)#traffic-class-group AF extended (config-traffic-class-group)#traffic-class video (config-traffic-class-group)#exit Configure the shared shaper. (config)#scheduler-profile 200kbps (config-scheduler-profile)#shaping-rate 200000 (config-scheduler-profile)#exit (config)#scheduler-profile 300kbps (config-scheduler-profile)#shaping-rate 300000 (config-scheduler-profile)#exit (config)#scheduler-profile shared-1mbps Copyright © 2010, Juniper Networks, Inc.

  • Page 110: Example: Simple Shared Shaping For Atm Vps

    In the example shown in Figure 20 on page 81, VP 1 is shaped to a shared rate of 5 Mbps. The shared shaper requires that voice and video traffic be carried in queues associated Copyright © 2010, Juniper Networks, Inc.

  • Page 111: Figure 20: Vp Shared Shaping

    5 Mbps. The EF and AF queues for the VP share the 5 Mbps with the best-effort traffic. The EF queue has first claim on the shared 5 Mbps, but only up to its individual shaping Copyright © 2010, Juniper Networks, Inc.

  • Page 112: Example: Simple Shared Shaping For Ethernet

    S-VLAN 0. The active constituents for the simple shared shaper are the three nodes for S-VLAN 0 in the three traffic-class groups. NOTE: This example uses QoS parameters to configure shared shaping. Configure the traffic classes and traffic-class groups. (config)#traffic-class tc1 (config)#exit (config)#traffic-class tc2 (config)#exit (config)#traffic-class-group g1 Copyright © 2010, Juniper Networks, Inc.
  • Page 113 (config-qos-profile)#vlan queue traffic-class best-effort (config-qos-profile)#vlan node scheduler-profile vlan-be (config-qos-profile)#svlan node scheduler-profile svlan-be (config-qos-profile)#vlan queue traffic-class tc1 (config-qos-profile)#svlan node scheduler-profile svlan-g1 group g1 (config-qos-profile)#svlan queue traffic-class tc2 (config-qos-profile)#svlan node scheduler-profile svlan-g2 group g2 (config-qos-profile)#ethernet group g2 scheduler-profile default Copyright © 2010, Juniper Networks, Inc.
  • Page 114 (config-if)#svlan id 0 1 (config-if)#ip address 1.2.1.1 255.255.255.0 (config-if)#exit (config)#interface fastEthernet 11/0.2 (config-if)#svlan id 0 2 (config-if)#ip address 1.3.1.1 255.255.255.0 (config-if)#exit Related Configuring Simple Shared Shaping on page 77 Documentation Simple Shared Shaping Overview on page 75 Copyright © 2010, Juniper Networks, Inc.

  • Page 115: Configuring Variables In The Simple Shared Shaping Algorithm

    Figure 22 on page 85 shows a two-constituent simple shared shaper consisting of best-effort and video traffic. The sum of the best-effort and video traffic is shaped to the configured shared-shaping rate. Figure 22: Simple Shared Shaper Behavior Without Algorithm Controls Copyright © 2010, Juniper Networks, Inc.

  • Page 116: Simple Shared Shaper Algorithm Calculations

    Calculates the new measured rate. Calculates the virtual output queue length (VOQL). Calculates the new dynamic rate. Uses the larger value of the new dynamic rate (from Step 3) and a minimum dynamic rate. Copyright © 2010, Juniper Networks, Inc.

  • Page 117: Variables Of The Simple Shared Shaper Algorithm

    5 Mbps. The default value is 0. reactionFactor—Controls how the simple shared shaper reacts to changing rates, expressed as a percentage. The default value of 200 changes the algorithm to use 200 percent of the changing rate. Copyright © 2010, Juniper Networks, Inc.

  • Page 118: Guidelines For Controlling The Simple Shared Shaper Algorithm

    Guidelines for Controlling the Simple Shared Shaper Algorithm You can configure the simple shared shaper variables individually, but it is useful to use configuration guidelines to determine how the variables work together to achieve a desired behavior. Copyright © 2010, Juniper Networks, Inc.

  • Page 119: Configuring Simple Shared Shaper Algorithm Variables

    The range for the convergence factor is 0–99 percent, with 0 being the most liberal and 99 the most conservative. The default value is 50. (Optional) Configure the specify the reaction factor for all simple shared shapers on the router. host1(config-qos-shared-shaper-control)#reaction-factor 50 Copyright © 2010, Juniper Networks, Inc.

  • Page 120: Sample Process For Controlling The Simple Shared Shaper Algorithm

    The example contains two parts: when the video flow is turned on, and then turned off. NOTE: The rates in this example are approximate and for illustrative purposes only. Your configuration might yield different results based on network variables. Copyright © 2010, Juniper Networks, Inc.

  • Page 121: Table 9: Rising Edge Sample When Video Flow Starts

    The conservative configuration overreacts to VOQL and the change of rate, and converges very slowly. Figure 25 on page 92 shows a graph of the dynamic rate when the video flow starts. Copyright © 2010, Juniper Networks, Inc.

  • Page 122: Figure 25: Dynamic Rate When Video Flow Starts

    14337 14503 14701 Most – – – – – – – – – – conservati v e Figure 26 on page 93 shows a graph of the dynamic rate when the video flow stops. Copyright © 2010, Juniper Networks, Inc.

  • Page 123: Figure 26: Dynamic Rate When Video Flow Stops

    Figure 26: Dynamic Rate When Video Flow Stops Related Simple Shared Shaping Algorithm Overview on page 85 Documentation Variables of the Simple Shared Shaper Algorithm on page 87 Configuring Simple Shared Shaper Algorithm Variables on page 89 Copyright © 2010, Juniper Networks, Inc.
  • Page 124 JunosE 11.3.x Quality of Service Configuration Guide Copyright © 2010, Juniper Networks, Inc.

  • Page 125: Configuring Compound Shared Shaping Of Traffic

    Issue the show qos shared-shaper command to determine whether compound shared shapers are supported for the line module. Contact your Juniper Networks account representative for more information about line modules with the EFA2 ASIC. The TFA hardware is only available on the ES2 10G LM on the E120 and E320 Broadband Services Routers.

  • Page 126: Bandwidth Allocation For Compound Shared Shaping

    See “Configuring Traffic Classes That Define Service Levels” on page 14 and “Configuring Traffic-Class Groups That Define Service Levels” on page 15. To configure compound shared shaping: Create the scheduler profile. host1(config)#scheduler-profile compound Configure the compound shared shaper. host1(config-scheduler-profile)#shared-shaping-rate 128000 burst 32767 compound explicit-constituents Copyright © 2010, Juniper Networks, Inc.
  • Page 127 Using Expressions for Bandwidth and Burst Values in a Scheduler Profile on page 48 Example: Compound Shared Shaping for ATM VCs on page 98 Constituent Selection for Shared Shaping Overview on page 103 node qos-profile queue scheduler-profile Copyright © 2010, Juniper Networks, Inc.

  • Page 128: Example: Compound Shared Shaping For Atm Vcs

    Configure the traffic classes, traffic-class groups, and additional scheduler profiles. Configure the scheduler profile that defines the shared shaper and the profiles that apply the legacy shaper. host1(config)#scheduler-profile shared-1Mbps host1(config-scheduler-profile)#shared-shaping-rate 1000000 burst 32768 auto host1(config)#scheduler-profile 300Kbps host1(config-scheduler-profile)#shaping-rate 300000 host1(config)#scheduler-profile 200Kbps host1(config-scheduler-profile)#shaping-rate 200000 Copyright © 2010, Juniper Networks, Inc.
  • Page 129 200000 AF video atm-vc queue 300000 atm-vc ATM11/0.2 1000000 compound best-effort atm-vc queue atm-vc best-effort node EF voice atm-vc queue 200000 AF video atm-vc queue 300000 Total shared shapers: 2 Total constituents: Total failovers: Copyright © 2010, Juniper Networks, Inc.

  • Page 130: Example: Compound Shared Shaping For Atm Vps

    Figure 28: VP Compound Shared Shaping Example To configure VP compound shared shaping: Configure the traffic classes, traffic-class groups, and additional scheduler profiles. Configure the scheduler profile that defines the shared shaper and the profiles that apply the legacy shaper. Copyright © 2010, Juniper Networks, Inc.
  • Page 131 VP 1 Group EF node, and the VP 1 Group AF node. The available bandwidth is strictly allocated in the following order: VP1 EF group node VP1 AF group node VP1 default group node Related Configuring Compound Shared Shaping on page 96 Documentation Compound Shared Shaping Overview on page 95 Copyright © 2010, Juniper Networks, Inc.
  • Page 132 JunosE 11.3.x Quality of Service Configuration Guide Copyright © 2010, Juniper Networks, Inc.

  • Page 133: Configuring Implicit And Explicit Constituent Selection For Shaping

    The other case for inactive constituents is when you use explicit constituent selection and some of the nodes and queues are explicitly not included in the shared shaper. Copyright © 2010, Juniper Networks, Inc.

  • Page 134: Types Of Shared Shaper Constituents

    Copyright © 2010, Juniper Networks, Inc.

  • Page 135: Implicit Constituent Selection Overview

    Logical interface types include IP, VP, VC, VLAN, and S-VLAN. All nodes and queues for the same logical interface are potential constituents. Nodes are selected over queues. Copyright © 2010, Juniper Networks, Inc.

  • Page 136: Figure 29: Implicit Constituent Selection For Compound Shared Shaper At

    B’s shared shaper are the VC 3 default group queue, the VC 3 Group EF node, and the VC 3 Group AF node. The VC 3 default group queue is selected instead of the VC 3 default group node because the shared shaper is associated with that best-effort queue. Copyright © 2010, Juniper Networks, Inc.

  • Page 137: Implicit Bandwidth Allocation For Compound Shared Shaping

    For example, suppose a compound shared shaper has a rate of 2 Mbps. The shared shaper has three active constituents: the best-effort node, a voice queue in the auto-strict traffic-class group, and a video queue in an extended traffic-class group. For compound Copyright © 2010, Juniper Networks, Inc.
  • Page 138 Unlike strict constituents, which can consume bandwidth up to the legacy shaping rate or the shared-shaping rate, weighted constituents share bandwidth with their peers solely Copyright © 2010, Juniper Networks, Inc.

  • Page 139: Weighted Compound Shared Shaping Example

    The VC 1 AF group node is weighted with the VC 1 best-effort node. The sum of the constituent weights is 32. With a weight of 31, the VC 1 AF group node can transmit Copyright © 2010, Juniper Networks, Inc.

  • Page 140: Configuring Implicit Constituents For Simple Or Compound Shared Shaping

    Before you configure implicit constituents: Configure the traffic classes and traffic-class groups. See “Configuring Traffic Classes That Define Service Levels” on page 14 and “Configuring Traffic-Class Groups That Define Service Levels” on page 15. To configure implicit constituents: Copyright © 2010, Juniper Networks, Inc.

  • Page 141: Explicit Constituent Selection Overview

    To identify the constituents for simple shared shaping, include the explicit-constituents keyword with the shared-shaping-rate simple command in a scheduler profile that you associate with a best-effort node or queue to identify the logical interface. Copyright © 2010, Juniper Networks, Inc.

  • Page 142: Explicit Shared Shaping Example

    EF node, and the VC 1 Group AF node. Explicit Weighted Compound Shared Shaping Example Figure 34 on page 113 illustrates a case where scheduler profiles A, B, C, D, and E are applied to scheduler objects. Copyright © 2010, Juniper Networks, Inc.

  • Page 143: Figure 34: Case 1: Explicit Constituent Selection With Weighted Constituents

    1/10. Figure 35 on page 114 illustrates another case where scheduler profiles B, X, Y, and Z are applied to scheduler objects. Each profile assigns a weight to an explicit constituent. Copyright © 2010, Juniper Networks, Inc.

  • Page 144: Figure 35: Case 2: Explicit Constituent Selection With Weighted Constituents

    NOTE: The node is selected as the constituent when both the node and the queues stacked over node are specified in a scheduler profile. Related Configuring Explicit Constituents for Simple or Compound Shared Shaping on page 115 Documentation Copyright © 2010, Juniper Networks, Inc.

  • Page 145: Configuring Explicit Constituents For Simple Or Compound Shared Shaping

    You can optionally set a value that determines the precedence of a constituent among its peers (strict or weighted) for claiming bandwidth. For strict-priority constituents, the priority range is 1–8 and the default value is 8. A lower value correlates to a higher claim. Copyright © 2010, Juniper Networks, Inc.
  • Page 146 Related Constituent Selection for Shared Shaping Overview on page 103 Documentation Explicit Constituent Selection Overview on page 111 scheduler-profile shared-shaping-constituent shared-shaping-rate Copyright © 2010, Juniper Networks, Inc.

  • Page 147: Monitoring A Qos Scheduler Hierarchy

    To monitor QoS scheduling, see: Monitoring the QoS Scheduler Hierarchy on page 303 Monitoring the Configuration of Scheduler Profiles on page 309 Monitoring Shared Shapers on page 310 Monitoring Shared Shaper Algorithm Variables on page 312 Copyright © 2010, Juniper Networks, Inc.
  • Page 148 JunosE 11.3.x Quality of Service Configuration Guide Copyright © 2010, Juniper Networks, Inc.

  • Page 149: Creating A Qos Scheduler Hierarchy On An Interface With Qos Profiles

    QoS Profile Overview on page 121 Configuring and Attaching QoS Profiles to an Interface on page 125 Configuring Shadow Nodes for Queue Management on page 141 Monitoring a Scheduler Hierarchy on an Interface with QoS Profiles on page 147 Copyright © 2010, Juniper Networks, Inc.
  • Page 150 JunosE 11.3.x Quality of Service Configuration Guide Copyright © 2010, Juniper Networks, Inc.

  • Page 151: Qos Profile Overview

    Line modules with the FFA ASIC hardware provide 2000 level 1 nodes or queues and 64,000 level 2 nodes or queues. The ES2 4G LM provides 2000 level 1 nodes or queues Copyright © 2010, Juniper Networks, Inc.

  • Page 152: Scaling Subscribers On The Tfa Asic With Qos

    If you do not create a QoS hierarchy with queues at level 3, the system adds phantom nodes to enforce this requirement. To display the hierarchy that is created for the subscriber on the line module, issue the show qos scheduler-hierarchy command. Copyright © 2010, Juniper Networks, Inc.

  • Page 153: Profiles

    For more information about system resource requirements for shadow nodes, see Documentation Managing System Resources for Shadow Nodes on page 143 For QoS system maximums, see JunosE Release Notes, Appendix A, System Maximums Monitoring the QoS Profiles Attached to an Interface on page 320 Copyright © 2010, Juniper Networks, Inc.
  • Page 154 JunosE 11.3.x Quality of Service Configuration Guide Copyright © 2010, Juniper Networks, Inc.

  • Page 155: Configuring And Attaching Qos Profiles To An Interface

    Table 14 on page 125 lists the interface types and the commands that you can use with them. Table 14: Interface Types and Supported Commands Shadow Interface Type Queue Node Group Node atm-vc – atm-vp – bridge – ethernet Copyright © 2010, Juniper Networks, Inc.

  • Page 156: Configuring A Qos Profile

    Configure the scheduler hierarchy and shaping with scheduler profiles. See “Configuring a Scheduler Hierarchy” on page 47. To configure a QoS profile: Create a QoS profile and enter QoS Profile Configuration mode. host1(config)#qos-profile qosp-vc-queuing Copyright © 2010, Juniper Networks, Inc.
  • Page 157 Configuring Shadow Nodes on page 144 Monitoring a Scheduler Hierarchy on an Interface with QoS Profiles on page 147 For information about configuring QoS profiles with Service Manager, see JunosE Broadband Access Configuration Guide group Copyright © 2010, Juniper Networks, Inc.

  • Page 158: Attaching A Qos Profile To An Interface

    50 qos-profile qosp-vp-strictbw Attaching a QoS Profile to an S-VLAN You can attach a QoS profile to the specified S-VLAN ID assigned to a VLAN subinterface that is configured over an Ethernet interface. Copyright © 2010, Juniper Networks, Inc.

  • Page 159: Attaching A Qos Profile To A Port Type

    Supported Interface Types for QoS Profiles on page 125 Documentation Configuring a QoS Profile on page 126 For information about attaching a QoS profile using Service Manager, see JunosE Broadband Access Configuration Guide atm-vp qos-profile Copyright © 2010, Juniper Networks, Inc.

  • Page 160: Munged Qos Profile Overview

    ATM is named atm-default. Add the rules in the QoS port-type profile to the munged QoS profile. The entries in the QoS profile specified in the corresponding qos-port-type-profile command have the lowest precedence. Copyright © 2010, Juniper Networks, Inc.

  • Page 161: Sample Munged Qos Profile Process

    QoS profile that is attached to the specific interface, ATM 11/0.2. Figure 36: Munged Profile Example The port-attached QoS profile on ATM 11.0 contains the following queue rule: host1(config)#qos-profile atmPort host1(config-qos-profile)#ip queue traffic-class priority-data scheduler-profile 64kbps host1(config-qos-profile)#exit Copyright © 2010, Juniper Networks, Inc.

  • Page 162: Example: Port-Type Qos Profile Attachment

    ATM 11/0.2—QoS profile qp2 is attached ATM 11/0.3—No QoS profile is attached The major ATM interface, 11/0, does not have a QoS profile explicitly attached. Therefore, by default the atm-default QoS port-type profile is attached. Copyright © 2010, Juniper Networks, Inc.

  • Page 163: Figure 37: Attaching Qos Profiles To Atm Subinterfaces

    Display the QoS interface hierarchy for ATM interface 11/0. This display shows all QoS attachments above interface 11/0. If no QoS profiles are attached above the specified interface, the router shows the first attachment below the specified interface. Copyright © 2010, Juniper Networks, Inc.
  • Page 164 In this case, attachment@ indicates the ATM major interface (11/0) below the subinterface. host1# show qos interface-hierarchy interface atm 11/0.3 attachment@ atm ATM11/0: interface rule traffic scheduler queue t-class profile type type class profile profile group Copyright © 2010, Juniper Networks, Inc.

  • Page 165: Example: Qos Profile Attachment To Port

    Create and configure QoS profile qp2. Copyright © 2010, Juniper Networks, Inc.
  • Page 166 QoS profile attached closest to the leaf node is used, however. Traffic class tc3 comes from QoS profile qp2, which is attached to ATM subinterface ATM 11/0.2. Queues for traffic classes tc4 and tc5 come from QoS profile qp1, which is attached at the ATM major interface. Copyright © 2010, Juniper Networks, Inc.

  • Page 167: Example: Diffserv Configuration With Multiple Traffic-Class Groups

    Create scheduler profiles for the assured forwarding, expedited forwarding, and best-effort groups. Specify strict priority scheduling for the expedited forwarding traffic and shape it to 20 Mbps. (config)#scheduler-profile expeditedGroup (config-scheduler-profile)#strict-priority (config-scheduler-profile)#shaping-rate 20000000 (config-scheduler-profile)#assured-rate 20000000 (config-scheduler-profile)#exit Copyright © 2010, Juniper Networks, Inc.
  • Page 168 (config-qos-profile)#ip node group assured-fwd scheduler-profile default (config-qos-profile)#ip node group expedited-fwd scheduler-profile default (config-qos-profile)#ip node group best-effort scheduler-profile default (config-qos-profile)#ip queue traffic-class voice scheduler-profile voice (config-qos-profile)#ip queue traffic-class video scheduler-profile video (config-qos-profile)#ip queue traffic class best-effort scheduler-profile best-effort (config-qos-profile)#exit Copyright © 2010, Juniper Networks, Inc.

  • Page 169: Figure 39: Diffserv Configuration With Multiple Traffic-Class Groups

    When you specify a group rule within an attached QoS profile, nodes and queue may be attached to group nodes. If the qpDiffServExample QoS profile used in the preceding example did not contain group rules, then the groups would exist with no attachments. Copyright © 2010, Juniper Networks, Inc.

  • Page 170: Figure 40: Diffserv Configuration Without Traffic-Class Groups

    Figure 40: Diffserv Configuration Without Traffic-Class Groups Because the BE, AF, and EF groups have no queues, their scheduler attributes (weight, assured rate, shaping rate) do not affect the HRR scheduler's distribution of bandwidth. Copyright © 2010, Juniper Networks, Inc.

  • Page 171: Configuring Shadow Nodes For Queue Management

    Phantom nodes have the same weight as the associated queues and are not shaped, which preserves the behavior of the queues as if they are at their original level. Figure 41 on page 142 compares a scheduler hierarchy with and without phantom nodes. Copyright © 2010, Juniper Networks, Inc.

  • Page 172: Shadow Nodes And Scheduler Behavior

    Shadow nodes can be configured for all interface types available for nodes. NOTE: Shadow nodes ignore any shared-shaping rates in a scheduler profile. Figure 42 on page 143 compares a scheduler hierarchy with and without shadow nodes. Copyright © 2010, Juniper Networks, Inc.

  • Page 173: Managing System Resources For Shadow Nodes

    Each ASIC hardware type provides different node and queue resources. Level 1 queues stack directly above the port; level 2 queues stack above a node and the port. The router implicitly creates the level 1 and level 2 queues. Copyright © 2010, Juniper Networks, Inc.

  • Page 174: Configuring Shadow Nodes

    Configure a shadow node for each interface of the specified type. host1(config-qos-profile)#atm shadow-node scheduler-profile default Configure a queue for interfaces in the specified traffic class. host1(config-qos-profile)#atm queue traffic-class strict-priority scheduler-profile scheduler1 Copyright © 2010, Juniper Networks, Inc.

  • Page 175: Example: Shadow Nodes Over Vlan And Ip Queues

    In the second part, you specify an Ethernet node, a VLAN node, a shadow node, and a VLAN queue. The system creates the shadow node so that the VLAN queue is at the proper scheduler level. host1(config-qos-profile)#ethernet node host1(config-qos-profile)#vlan node host1(config-qos-profile)#vlan shadow-node host1(config-qos-profile)#vlan queue traffic-class best-effort scheduler-profile default Copyright © 2010, Juniper Networks, Inc.

  • Page 176: Example: Shadow Nodes On The Same Traffic-Class Group

    Copyright © 2010, Juniper Networks, Inc.

  • Page 177: Monitoring A Scheduler Hierarchy On An Interface With Qos Profiles

    Monitoring the Configuration of QoS Port-Type Profiles on page 321 Monitoring the Configuration of QoS Profiles on page 321 Monitoring the Configuration of Scheduler Profiles on page 309 Monitoring QoS Parameter Instances on page 332 Copyright © 2010, Juniper Networks, Inc.
  • Page 178 JunosE 11.3.x Quality of Service Configuration Guide Copyright © 2010, Juniper Networks, Inc.

  • Page 179: Interface Solutions For Qos

    Configuring QoS for Gigabit Ethernet Interfaces and VLAN Subinterfaces on page 169 Configuring QoS for 802.3ad Link Aggregation Groups on page 175 Configuring QoS for L2TP Sessions on page 187 Configuring Interface Sets for QoS on page 195 Copyright © 2010, Juniper Networks, Inc.
  • Page 180 JunosE 11.3.x Quality of Service Configuration Guide Copyright © 2010, Juniper Networks, Inc.

  • Page 181: Configuring An Integrated Scheduler To Provide Qos For Atm

    The integrated scheduler enables you to configure QoS on your ATM networks using the HRR scheduler that is used on all E Series ASIC-enabled line modules. In addition, you can use the commercial SAR scheduler to configure traditional ATM cell-based QoS. Copyright © 2010, Juniper Networks, Inc.

  • Page 182: Backpressure And The Integrated Scheduler

    SAR VC backpressure mechanism. If the SAR scheduler is operating in default integrated mode, this command must be in QoS profiles that are attached to ATM ports. Copyright © 2010, Juniper Networks, Inc.

  • Page 183: Vp Shaping

    ATM contract rates. SAR VP shaping is configured for the physical port using the atm vp-tunnel command. Related Integrating the HRR Scheduler and SAR Scheduler on page 154 Documentation Per-Packet Queuing on the SAR Scheduler Overview on page 155 Copyright © 2010, Juniper Networks, Inc.

  • Page 184: Integrating The Hrr Scheduler And Sar Scheduler

    See “Configuring the QoS Shaping Mode for ATM Interfaces” on page 166. Configure low-CDV QoS port mode to ensure that the HRR and SAR schedulers are configured at the same rate. See “Configuring Low-CDV Mode for Per-Port Queuing on ATM Interfaces” on page 163. Copyright © 2010, Juniper Networks, Inc.

  • Page 185: Per-Packet Queuing On The Sar Scheduler Overview

    SAR scheduler and the HRR scheduler; low-cdv mode works with cell shaping mode only and enables relative weighted VCs and hierarchical shaping in the HRR scheduler. The SAR scheduler performs normal buffering and can shape either the VC or VP, but not both. Copyright © 2010, Juniper Networks, Inc.

  • Page 186: Operational Qos Shaping Mode For Atm Interfaces Overview

    (set by the qos-mode-port command) is low-cdv, the operational shaping mode is cell; otherwise the operational shaping mode is frame. Table 17 on page 157 lists the possible combinations of the two commands and the resultant operational shaping mode. Copyright © 2010, Juniper Networks, Inc.

  • Page 187: E120 Router And E320 Router

    (set by the qos-mode-port command) is low-cdv, the operational shaping mode is cell; otherwise the operational shaping mode is frame. Table 18 on page 158 lists the possible combinations of the two commands and the resultant operational shaping mode. Copyright © 2010, Juniper Networks, Inc.

  • Page 188: Guidelines For Configuring Qos Over Atm

    ATM VC node and the nodes and queues stacked above it in the scheduler hierarchy. VC backpressure is disabled in low-latency QoS port mode and low-cdv QoS port mode. Copyright © 2010, Juniper Networks, Inc.
  • Page 189 Configuring Default Integrated Mode for ATM Interface on page 160 Configuring Low-Latency Mode for Per-Port Queuing on ATM Interfaces on page 161 Configuring Low-CDV Mode for Per-Port Queuing on ATM Interfaces on page 163 Copyright © 2010, Juniper Networks, Inc.

  • Page 190: Configuring Default Integrated Mode For Atm Interface

    From the desired port, set the QoS port mode to default integrated mode. host1(config)#interface atm 2/0 host1(config-if)#no qos-mode-port TIP: For ATM interfaces on ERX7xx models, ERX14xx models, and the ERX310 router, you must specify port 0. Copyright © 2010, Juniper Networks, Inc.

  • Page 191: Configuring Low-Latency Mode For Per-Port Queuing On Atm Interfaces

    When you configure low-latency mode: VC backpressure is disabled. Port backpressure is enabled as aggressive. SAR scheduler performs minimal buffering. HRR scheduler is dominant. This procedure creates the low-latency mode configuration shown in Figure 45 on page 162. Copyright © 2010, Juniper Networks, Inc.

  • Page 192: Figure 45: Low-Latency Mode

    From the desired port, set the QoS port mode to low latency. host1(config)#interface atm 2/0 host1(config-if)#qos-mode-port low-latency host1(config-if)#qos-profile low-latency-q-p Copyright © 2010, Juniper Networks, Inc.

  • Page 193: Configuring Low-Cdv Mode For Per-Port Queuing On Atm Interfaces

    SAR scheduler performs more buffering than in low-latency mode. Use cell QoS shaping mode. This procedure creates the low-CDV mode with per-VP CDVT configuration shown in Figure 46 on page 164. Figure 47 on page 164 shows low-CDV mode with per-VC CDVT. Copyright © 2010, Juniper Networks, Inc.

  • Page 194: Figure 46: Low-Cdv Mode (Per-Vp Cdvt)

    JunosE 11.3.x Quality of Service Configuration Guide Figure 46: Low-CDV Mode (per-VP CDVT) Figure 47: Low-CDV Mode (per-VC CDVT) To configure low-CDV mode with a strict-priority queue and a best-effort queue: Copyright © 2010, Juniper Networks, Inc.
  • Page 195 2/0.7 host1(config-subif)#atm pvc 7 1 7 aal5snap host1(config-subif)#interface atm 2/0.8 host1(config-subif)#atm pvc 8 1 8 aal5snap TIP: For ATM interfaces on ERX7xx models, ERX14xx models, and the ERX310 router, you must specify port 0. Copyright © 2010, Juniper Networks, Inc.

  • Page 196: Configuring The Qos Shaping Mode For Atm Interfaces

    Configure the shaping mode and specify either frame or cell. host1(config-if)#qos-shaping-mode cell BEST PRACTICE: We recommend that you clear the statistics counters whenever you change the QoS shaping mode. Otherwise, the statistics contain a mixture of frame-based and cell-based values. Copyright © 2010, Juniper Networks, Inc.

  • Page 197: Disabling Per-Port Queuing On Atm Interfaces

    Monitoring the QoS Profiles Attached to an Interface on page 320 Monitoring the Configuration of QoS Port-Type Profiles on page 321 Monitoring the Configuration of QoS Profiles on page 321 Monitoring the QoS Scheduler Hierarchy on page 303 Monitoring Shared Shapers on page 310 Copyright © 2010, Juniper Networks, Inc.
  • Page 198 JunosE 11.3.x Quality of Service Configuration Guide Copyright © 2010, Juniper Networks, Inc.

  • Page 199: Subinterfaces

    Creating a QoS Interface Hierarchy for Bulk-Configured VLAN Subinterfaces with RADIUS on page 172 To configure subscriber-based QoS for 802.3ad link aggregation interfaces, see QoS for 802.3ad Link Aggregation Interfaces Overview on page 175 Copyright © 2010, Juniper Networks, Inc.

  • Page 200: Qos Shaping Mode For Ethernet Interfaces Overview

    Other Ports Shaping Mode Cell Cell Cell Frame Frame Frame Cell Frame Frame Frame Cell Cell Frame No shaping mode Frame Cell No shaping mode Cell No shaping mode No shaping mode Frame Copyright © 2010, Juniper Networks, Inc.

  • Page 201: Configuring The Qos Shaping Mode For Ethernet Interfaces

    BEST PRACTICE: We recommend that you clear the statistics counters whenever you change the QoS shaping mode. Otherwise, the statistics contain a mixture of frame-based and cell-based values. Related QoS Shaping Mode for Ethernet Interfaces Overview on page 170 Documentation interface gigabitEthernet qos-shaping-mode Copyright © 2010, Juniper Networks, Inc.

  • Page 202: Creating A Qos Interface Hierarchy For Bulk-Configured Vlan Subinterfaces

    (Optional) IETF VSA [22]—Framed-Route Verify that the attributes are being used by RADIUS. The highlighted output from this debug log message shows the QoS profile, virtual router, and framed route attributes configured through RADIUS. Copyright © 2010, Juniper Networks, Inc.
  • Page 203 0.0.0.0 for the next hop. The E Series router then assigns the subinterface associated with the user as the next hop in the routing table. Verify that the correct QoS profile is attached to the VLAN subinterface. Copyright © 2010, Juniper Networks, Inc.

  • Page 204: Monitoring Qos Configurations For Ethernet

    Monitoring the QoS Profiles Attached to an Interface on page 320 Monitoring the Configuration of QoS Port-Type Profiles on page 321 Monitoring the Configuration of QoS Profiles on page 321 Monitoring the QoS Scheduler Hierarchy on page 303 Monitoring Shared Shapers on page 310 Copyright © 2010, Juniper Networks, Inc.

  • Page 205: Configuring Qos For 802.3Ad Link Aggregation Groups

    LAG, the hash algorithm is based on the IP Source Address and Destination Address in the IP header. For subscriber load balancing, you configure the scheduler hierarchy with IP, VLAN, and S-VLAN queues and the system allocates them to individual ports in the LAG. The system Copyright © 2010, Juniper Networks, Inc.

  • Page 206: Munged Qos Profiles And Load Balancing

    For example, a LAG instance can specify a shaping rate of 100 Mbps on an Ethernet port or a group node. The system shapes all Ethernet ports or group nodes to the same rate within the LAG. Using load balancing, the system strives to balance the traffic each link equally. Copyright © 2010, Juniper Networks, Inc.

  • Page 207: Qos And Ethernet Link Redundancy

    Hashed Load Balancing for 802.3ad Link Aggregation Groups Overview To configure hashed load balancing, you configure a scheduler hierarchy with Ethernet queues and the system replicates the queues for each link within the LAG. The system Copyright © 2010, Juniper Networks, Inc.

  • Page 208: Sample Scheduler Hierarchy For Hashed Load Balancing

    S-VLANs and Subscriber Load Balancing The system clones S-VLAN nodes and queues on each link in the LAG. The system clone S-VLANs so it can allocate subscribers that share a common S-VLAN ID to different links Copyright © 2010, Juniper Networks, Inc.

  • Page 209: Pppoe Over Vlans And Subscriber Load Balancing

    LAG. In this example, the scheduler nodes for VLAN 0,0 are all allocated to Gigabit Ethernet interface in slot 3, port 0. S-VLAN nodes and queues are cloned for each link in the LAG. S-VLAN nodes in each traffic-class group are shown identically on both ports. Copyright © 2010, Juniper Networks, Inc.

  • Page 210: Subscriber Allocation In 802.3Ad Link Aggregation Groups

    For this purpose, the system counts each upper-layer interface as a single subscriber, regardless of the number of forwarding interfaces stacked above it. Figure 51 on page 181 displays a sample allocation of subscribers. Copyright © 2010, Juniper Networks, Inc.

  • Page 211: Guidelines For Configuring Qos Over 802.3Ad Link Aggregation Groups

    The typical defaults in QoS profiles such as ethernet-default and atm-default Copyright © 2010, Juniper Networks, Inc.

  • Page 212: Configuring The Scheduler Hierarchy For Hashed Load Balancing In 802.3Ad Link Aggregation Groups

    Related QoS for 802.3ad Link Aggregation Interfaces Overview on page 175 Documentation Hashed Load Balancing for 802.3ad Link Aggregation Groups Overview on page 177 interface lag node qos-profile queue Copyright © 2010, Juniper Networks, Inc.

  • Page 213: Groups

    QoS for 802.3ad Link Aggregation Interfaces Overview on page 175 Documentation Subscriber Load Balancing for 802.3ad Link Aggregation Groups Overview on page 178 Enabling Default Subscriber Load Balancing for 802.3ad Link Aggregation Groups on page 183 interface lag Copyright © 2010, Juniper Networks, Inc.

  • Page 214: Configuring Load Rebalancing For 802.3Ad Link Aggregation Groups

    Table 20 on page 184 describes the load balancing algorithm parameters that you can configure. Table 20: Load Balancing Algorithm Parameters Keyword Description period Specifies the time period for rebalancing. For example, a period of 120 specifies that rebalancing occurs once every 2 minutes. Copyright © 2010, Juniper Networks, Inc.

  • Page 215: Configuring The System To Dynamically Rebalance The Lag

    For example, specifying maximum-improvement 40 subscribers indicates that the algorithm rebalances 40 subscribers per period. Configuring the System to Dynamically Rebalance the LAG To configure the system to dynamically rebalance the LAG: Specify the LAG interface. Copyright © 2010, Juniper Networks, Inc.

  • Page 216: Monitoring Qos Configurations For 802.3Ad Link Aggregation Groups

    Monitoring the QoS Profiles Attached to an Interface on page 320 Monitoring the Configuration of QoS Port-Type Profiles on page 321 Monitoring the Configuration of QoS Profiles on page 321 Monitoring the QoS Scheduler Hierarchy on page 303 Monitoring Shared Shapers on page 310 Copyright © 2010, Juniper Networks, Inc.

  • Page 217: Configuring Qos For L2Tp Sessions

    QoS over L2TP. The type of networking architecture in which the QoS profile is used determines the actual hierarchy that is built. Figure 52 on page 188 through Figure 56 on page 189 show scheduler hierarchies for different networking architectures. Copyright © 2010, Juniper Networks, Inc.

  • Page 218: Figure 52: Lns (Non-Mlppp) Scheduler Hierarchy

    JunosE 11.3.x Quality of Service Configuration Guide Figure 52: LNS (Non-MLPPP) Scheduler Hierarchy Figure 53: LNS (MLPPP) QoS Scheduler Hierarchy Figure 54: LAC over Ethernet (Without VLANs) Scheduler Hierarchy Copyright © 2010, Juniper Networks, Inc.

  • Page 219: Configuring Qos For An L2Tp Session

    L2TP session interfaces have default QoS profiles and scheduler nodes. The default configuration includes the following settings: host1(config)# show qos-profile l2tp-session-default t-class interface rule traffic scheduler queue drop statistics group type type class profile profile profile profile Copyright © 2010, Juniper Networks, Inc.

  • Page 220: Configuring Qos For An L2Tp Lns Session

    Add queues for L2TP session interfaces to the QoS profile. host1(config-qos-profile)#lt2p-session queue traffic-class best-effort scheduler-profile 400k host1(config-qos-profile)#lt2p-session queue traffic-class voice scheduler-profile 100k host1(config-qos-profile)#exit host1(config)# Attach the QoS profile to the interface on which you have configured L2TP. Copyright © 2010, Juniper Networks, Inc.

  • Page 221: Configuring Qos For An L2Tp Lac Session

    -------- --------- ----- --------- --------- ------- ------- ---------- l2tp-session queue best-effort 400k default default default tcGroup1 l2tp-session queue voice 100k default default default Copyright © 2010, Juniper Networks, Inc.

  • Page 222: Configuring Qos For Tunnel-Server Ports For L2Tp Lns Sessions

    To configure QoS for the tunnel-server port: Create the QoS profile. host1(config)#qos-profile lns-tsport Configure group nodes for the tunnel-server ports. host1(config-qos-profile)#ip queue traffic-class best-effort scheduler-profile business-data queue-profile data host1(config-qos-profile)#ip queue traffic-class video scheduler-profile video queue-profile video Copyright © 2010, Juniper Networks, Inc.

  • Page 223: Qos And L2Tp Tx Speed Avp 24 Overview

    For each logical interface, QoS determines the rate of the interface using either the shaping rate or the shared-shaping rate, if one is configured. The numeric value of the Copyright © 2010, Juniper Networks, Inc.

  • Page 224: Shaping Mode

    Monitoring the QoS Profiles Attached to an Interface on page 320 Monitoring the Configuration of QoS Port-Type Profiles on page 321 Monitoring the Configuration of QoS Profiles on page 321 Monitoring the QoS Scheduler Hierarchy on page 303 Monitoring Shared Shapers on page 310 Copyright © 2010, Juniper Networks, Inc.

  • Page 225: Configuring Interface Sets For Qos

    Interface sets are also useful for grouping a large number of subscribers into a particular service class or for defining traffic engineering aggregates for DSLAMs. Interface Set Terms Table 21 on page 196 lists the terminology used for interface sets Copyright © 2010, Juniper Networks, Inc.

  • Page 226: Architecture Of Interface Sets For Qos

    Architecture of Interface Sets for QoS on page 196 Documentation Configuring Interface Sets for Scheduling and Queuing on page 199 Architecture of Interface Sets for QoS To configure groups of logical interfaces, you must configure both interface sets and interface supersets. Copyright © 2010, Juniper Networks, Inc.

  • Page 227: Interface Set Parents And Types

    Sample Interface Columns and Scheduler Hierarchies Figure 57 on page 198 shows a sample interface column using interface sets and interface supersets for VLANs. Copyright © 2010, Juniper Networks, Inc.

  • Page 228: Scheduling And Shaping Interface Sets

    You can apply QoS to interface sets and interface supersets in the same way as a logical interface. Each interface set or interface superset can have a shared shaper applied to it. The constituents of the shared shaper are the scheduler nodes and queues associated with the interface set. Copyright © 2010, Juniper Networks, Inc.

  • Page 229: Configuring Interface Sets For Scheduling And Queuing

    (Optional) Monitor the configuration of interface sets and supersets. See “Monitoring the Configuration of QoS Interface Sets” on page 330 and “Monitoring the Configuration of QoS Interface Supersets” on page 331. Related Interface Sets for QoS Overview on page 195 Documentation Copyright © 2010, Juniper Networks, Inc.

  • Page 230: Configuring Interface Supersets For Qos

    2/0/0 atm-vp 2 Related To add members to the interface superset, see Configuring Interface Sets for QoS on Documentation page 201 Monitoring the Configuration of QoS Interface Supersets on page 331 qos-interface-superset qos-interface-parent Copyright © 2010, Juniper Networks, Inc.

  • Page 231: Configuring Interface Sets For Qos

    Delete the interface set from the interface superset. host1(config-qos-interface-superset)#no qos-interface-set atm-vc-data Related For more information about configuring interface supersets, see Configuring Interface Documentation Supersets for QoS on page 200 Monitoring the Configuration of QoS Interface Sets on page 330 member-interface-type Copyright © 2010, Juniper Networks, Inc.

  • Page 232: Adding Member Interfaces To An Interface Set

    When multiple subscribers exist in one interface set, such as PPPoE subscribers over the same VLAN, they are joined with the first subscriber’s VSA. The system generates an error message if one of the subscribers attempts to join another interface set using another VSA. Copyright © 2010, Juniper Networks, Inc.

  • Page 233: Changing And Deleting Interface Members In An Interface Set

    For example: host1(config)#interface gigabitEthernet 4/0/0.1 host1(config-sub-if)#svlan id 3 1 host1(config-sub-if)#qos-interface-parent vlan-business host1(config-sub-if)#ip address 1.2.3.4/24 Related For more information about RADIUS VSAs, see the JunosE Broadband Access Documentation Configuration Guide qos-interface-parent Copyright © 2010, Juniper Networks, Inc.

  • Page 234: Creating A Qos Parameter On An Interface Superset Or Interface Set

    Creating a QoS Parameter Instance for an Interface Superset To create a QoS parameter instance for an interface superset: Specify the QoS interface superset. host1(config)#qos-interface-superset vlan-superset Create the QoS parameter instance. host1(config-qos-interface-superset)#qos-parameter business-data Attach the QoS profile. host1(config-qos-interface-superset)#qos-profile vlan Copyright © 2010, Juniper Networks, Inc.

  • Page 235: Creating A Qos Parameter Instance For An Interface Set

    To configure a QoS profile to manage the scheduler resources for an interface superset or an interface set: Configure the QoS profile. hos1(config)#qos-profile vlan Specify an interface superset or an interface set as a queue. For interface supersets: Copyright © 2010, Juniper Networks, Inc.

  • Page 236: Attaching A Qos Profile To An Interface Superset

    Related Monitoring the QoS Profiles Attached to an Interface on page 320 Documentation Monitoring the QoS Scheduler Hierarchy on page 303 Monitoring Shared Shapers on page 310 node qos-interface-set qos-interface-superset qos-profile queue Copyright © 2010, Juniper Networks, Inc.

  • Page 237: Deleting An Interface Superset Or An Interface Set

    For more information about deleting an interface set from an interface superset, see Documentation Configuring Interface Supersets for QoS on page 200 For more information about deleting interface members of an interface set, seeConfiguring Interface Sets for QoS on page 201 qos-interface-parent qos-interface-set qos-interface-superset Copyright © 2010, Juniper Networks, Inc.

  • Page 238: Example: Configuring Interface Sets For 802.3Ad Link Aggregation Groups

    Configure the interface superset. host1(config)#interface superset lag Assign the parent interface as LAG. host1(config)#qos-interface-parent interface lag Restrict the interface superset to the Ethernet parent interface. host1(config-interface-superset)#restricted interface gigabitEthernet 4/0/0 Related qos-interface-parent Documentation qos-interface-superset restricted Copyright © 2010, Juniper Networks, Inc.

  • Page 239: Managing Queuing And Scheduling With Qos Parameters

    Configuring the Shaping Mode for Ethernet with QoS Parameters on page 265 Configuring Byte Adjustment for Shaping Rates with QoS Parameters on page 275 Configuring the Downstream Rate Using QoS Parameters on page 283 Copyright © 2010, Juniper Networks, Inc.
  • Page 240 JunosE 11.3.x Quality of Service Configuration Guide Copyright © 2010, Juniper Networks, Inc.

  • Page 241: Qos Parameter Overview

    This topic collection contains QoS parameter configuration information for two types of QoS users: QoS administrators and QoS clients. QoS administrators are responsible for implementing a QoS queuing architecture by defining the scheduler profiles and referencing them from QoS profiles. QoS administrators Copyright © 2010, Juniper Networks, Inc.

  • Page 242: Qos Parameter Terms

    Parameter instance Parameter name and value that a QoS client associates with a logical interface. Parameter value 32-byte unsigned integer value associated with a parameter instance. Copyright © 2010, Juniper Networks, Inc.

  • Page 243: Relationship Among Qos Parameters, Scheduler Profiles, And Qos Profiles

    The QoS administrator defines the attributes that the QoS client can modify by configuring a parameter definition. The QoS administrator specifies the parameter definition name in a scheduler profile. The QoS administrator references the scheduler profile in a QoS profile rule. Copyright © 2010, Juniper Networks, Inc.

  • Page 244: Qos Client Tasks

    After the QoS administrator defines parameter definitions: The QoS client creates a parameter instance and associates it with a logical interface. The QoS client attaches a QoS profile to the logical interface. Related QoS Parameter Audience on page 211 Documentation Copyright © 2010, Juniper Networks, Inc.

  • Page 245: Configuring A Qos Parameter

    Controlled-interface type Interface types that specify resources that the parameter instance can control. The QoS administrator can specify up to four controlled-interface types for each parameter definition. Copyright © 2010, Juniper Networks, Inc.

  • Page 246: Naming Guidelines For Qos Parameters

    Shaping rate for the same priority data service queue as min-data-sw In addition, parameter names cannot be the same as an arithmetic operator. Table 25 on page 217 lists examples of valid and invalid parameter names that use operators. Copyright © 2010, Juniper Networks, Inc.

  • Page 247: Interface Types And Qos Parameters

    In this example, you configure a parameter definition for a scheduler hierarchy in which a VLAN represents a subscriber. The parameter definition specifies that the parameter controls VLAN nodes and queues and sets the maximum rate for any parameter instance. Copyright © 2010, Juniper Networks, Inc.

  • Page 248: Instance-Interface Types

    VLAN. You then enable QoS clients to create a parameter instances at VLAN, SVLAN, and Ethernet interfaces by configuring instance-interface types of vlan, svlan, and ethernet. host1(config)#qos-parameter-define max-subscriber-bandwidth host1(config-qos-parameter-define)#controlled-interface-type vlan host1(config-qos-parameter-define)#instance-interface-type vlan host1(config-qos-parameter-define)#instance-interface-type svlan Copyright © 2010, Juniper Networks, Inc.

  • Page 249: Subscriber-Interface Types

    A RADIUS administrator can enter multiple QoS parameter name and value pairs when configuring the RADIUS server with the Juniper Networks VSA [26-82]. This means that the RADIUS can return multiple instances of the same VSA in a single request. For more information about Juniper Networks VSA [26-82], see Juniper Networks VSAs.

  • Page 250: Applications And Qos Parameters

    QoS Cell Mode Byte Adjustment (Cell and Frame) QoS Downstream Rate Related Configuring a Basic Parameter Definition for QoS Administrators on page 223 Documentation IP Multicast Bandwidth Adjustment for QoS Overview on page 253 Copyright © 2010, Juniper Networks, Inc.

  • Page 251: Scheduler Profiles And Parameter Expressions For Qos Administrators

    Operand values can be a parameter name or an integer. You specify an expression consisting of an operand, followed by zero or more [ operator, operand ] pairs. Copyright © 2010, Juniper Networks, Inc.

  • Page 252: Operators And Precedence

    5 * maxBandwidth Division maxBandwidth / 64000 Addition max-subscriber-bw + 50000 max-subscriber-bw + l2c-rate Subtraction max-subscriber-bw - 50000 max-subscriber-bw - l2c-rate Minimum max-subscriber-bw min 50000 max-subscriber-bw min l2c-rate Maximum max-subscriber-bw max 50000 max-subscriber-bw max l2c-rate Copyright © 2010, Juniper Networks, Inc.

  • Page 253: Specifying A Range In Expressions

    Configuring a Basic Parameter Definition for QoS Administrators on page 223 Configuring a Basic Parameter Definition for QoS Administrators This section describes how to configure an individual parameter definition and how to associate it with an application. Copyright © 2010, Juniper Networks, Inc.
  • Page 254 Reference the parameter within a scheduler profile parameter expression and configure an assured rate, shaping rate, shared-shaping rate, or weight. host1(config)#scheduler-profile business-data host1(config-scheduler-profile)#shaping-rate max-subscriber-bandwidth % 25 Add the scheduler profile to a QoS profile and configure the QoS profile. Copyright © 2010, Juniper Networks, Inc.

  • Page 255: Parameter Instances For Qos Clients Overview

    CLI or through client software such as RADIUS or SRC. As a QoS client, you can use QoS parameter instances to set the following attributes of a node or queue: Assured rate Shaping rate Copyright © 2010, Juniper Networks, Inc.

  • Page 256: Global Qos Parameter Instance Overview

    QoS profile attachment lower down the interface stack, providing a subscriber-specific value. You can attach QoS profiles and QoS parameters to a logical interface in either order. If a scheduler profile calls for a parameter and no parameter instance is defined, the system Copyright © 2010, Juniper Networks, Inc.

  • Page 257: Creating Parameter Instances

    To create a parameter instance for an ATM VP: Configure the ATM VP. host1(config)#interface atm 2/0 host1(config-if)#atm vp-tunnel 4 Do either of the following: Attach the parameter instance to an ATM VP on the interface. Copyright © 2010, Juniper Networks, Inc.

  • Page 258: Creating A Parameter Instance For An S-Vlan

    The example includes procedures for both QoS administrators and QoS clients. Through QoS parameter definitions, the QoS administrator defines a QoS scheduler hierarchy that corresponds to the physical network topology shown in Figure 60 on page 229. Copyright © 2010, Juniper Networks, Inc.

  • Page 259: Figure 60: Physical Network Topology

    6 Mbps of combined voice, video, and best-effort data traffic. The service limits video traffic to 2 Mbps and enables low-latency bandwidth for one 100 Kbps voice call. The QoS client then assigns this subscriber a scheduler weight value of 3, enabling this Copyright © 2010, Juniper Networks, Inc.

  • Page 260: Procedure For Qos Administrators

    The remaining traffic classes, best-effort and video, remain in the default traffic-class group. Configuring the After configuring the traffic classes and traffic-class groups, the QoS administrator Parameter Definitions configures the parameter definitions for Subscribers 1, 2, and 3. Copyright © 2010, Juniper Networks, Inc.
  • Page 261 Specify the valid range of this parameter as 1 Mbps–5 Mbps. host1(config)#qos-parameter-define max-subscriber-video-bandwidth host1(config-qos-parameter-define)#controlled-interface-type vlan host1(config-qos-parameter-define)#instance-interface-type vlan host1(config-qos-parameter-define)#instance-interface-type svlan host1(config-qos-parameter-define)#range 1000000 5000000 host1(config-qos-parameter-define)#exit Configure a parameter definition for the maximum number of 100 Kbps voice calls supported for the subscriber. Copyright © 2010, Juniper Networks, Inc.
  • Page 262 Configure a scheduler profile for the subscriber's voice service. a. Configure the scheduler profile named subscriber-voice. b. Configure the shaping rate by referencing the max-100Kbps-voice-calls parameter and multiplying it by 100 Kbps of voice calls. Copyright © 2010, Juniper Networks, Inc.
  • Page 263 Specify a queue for VLAN subinterfaces, referencing the video traffic class and the subscriber-video scheduler profile. g. Specify a queue for VLAN subinterfaces, referencing the voice traffic-class and the subscriber-voice scheduler profile. host1(config)#qos-profile subscriber-triple-play host1(config-qos-profile)#svlan node host1(config-qos-profile)#vlan node scheduler-profile subscriber-weight Copyright © 2010, Juniper Networks, Inc.
  • Page 264 9/0.1 host1(config-subif)#svlan id 2 1 host1(config-subif)#ip address 192.1.1.1 255.255.255.0 host1(config)#interface fastEthernet 9/0.2 host1(config-subif)#svlan id 2 2 host1(config-subif)#ip address 192.2.1.1 255.255.255.0 host1(config-subif)#exit host1(config)#interface fastEthernet 9/0.3 host1(config-subif)#svlan id 2 3 host1(config-subif)#ip address 192.3.1.1 255.255.255.0 host1(config-subif)#exit Copyright © 2010, Juniper Networks, Inc.

  • Page 265: Procedure For Qos Clients

    Configure the basic-data service for Subscriber 1. Subscribers a. Specify the Fast Ethernet interface in slot 9, port 0. b. Attach the QoS profile subscriber-data-service to the subscriber’s Fast Ethernet interface. host1(config)#interface fastEthernet 9/0.1 host1(config-subif)#qos-profile subscriber-data-service host1(config-subif)#exit Copyright © 2010, Juniper Networks, Inc.
  • Page 266 Create a parameter instance for max-100Kbps-voice-calls, enabling up to three 100 Kbps voice calls. e. Attach the QoS profile subscriber-triple-play to the subscriber's interface. host1(config)#interface fastEthernet 9/0.3 host1(config-if)#qos-parameter max-subscriber-bandwidth 8000000 host1(config-if)#qos-parameter subscriber-weight 6 host1(config-if)#qos-parameter max-subscriber-video-bandwidth 3000000 host1(config-if)#qos-parameter max-100Kbps-voice-calls 3 Copyright © 2010, Juniper Networks, Inc.

  • Page 267: Monitoring The Subscriber Configuration

    To display the shaping rates and burst for the four scheduler profiles (subscriber-best-effort, subscriber-video, subscriber-weight, and subscriber-voice, issue the show scheduler-profile command. host1#show scheduler-profile shaping scheduler shaping rate burst ---------------------- -------------------------------- ------- default <none> <none> subscriber-best-effort <none> <none> subscriber-video max-subscriber-video-bandwidth default subscriber-weight <none> <none> Copyright © 2010, Juniper Networks, Inc.
  • Page 268 ---------------------- ------------- default <none> subscriber-best-effort auto implicit subscriber-video <none> subscriber-weight <none> subscriber-voice <none> To display the settings for the QoS profile subscriber-triple-play, issue the show qos-profile command. host1#show qos-profile subscriber-triple-play Copyright © 2010, Juniper Networks, Inc.
  • Page 269 FastEthernet9/0 svlan 1 max-subscriber-video-bandwidth 1000000 Global parameter instances: Parameter instances reported: 13 To display the queue forwarding rates for the VLANs on the Fast Ethernet interface in slot 9, port 0, issue the show egress-queue rates command. Copyright © 2010, Juniper Networks, Inc.
  • Page 270 1 vlan Eth9/0.1 vlan queue best-effort 2000000 wgt 8 vlan Eth9/0.2 vlan node wgt 3 vlan Eth9/0.2 vlan queue video 2000000 wgt 8 vlan Eth9/0.2 vlan queue best-effort 6000000 wgt 8 Copyright © 2010, Juniper Networks, Inc.

  • Page 271: Complete Configuration Example

    512000 8192000 exit !Configure the subscriber-weight parameter definition. qos-parameter-define subscriber-weight controlled-interface-type vlan instance-interface-type vlan range 1 6 exit !Configure the max-subscriber-video parameter definition. qos-parameter-define max-subscriber-video-bandwidth controlled-interface-type vlan Copyright © 2010, Juniper Networks, Inc.
  • Page 272 ! Attach the QoS profile to the VLAN and S-VLAN subinterfaces. interface fastEthernet 9/0 encapsulation vlan exit interface fastEthernet 9/0.1 svlan id 2 1 ip address 192.1.1.1 255.255.255.0 interface fastEthernet 9/0.2 svlan id 2 2 ip address 192.2.1.1 255.255.255.0 Copyright © 2010, Juniper Networks, Inc.

  • Page 273: Qos Client Configuration

    2000000 qos-parameter max-100Kbps-voice-calls 1 qos-profile subscriber-triple-play exit ! Configure the enhanced triple-play service for Subscriber 3. interface fastEthernet 9/0.3 qos-parameter max-subscriber-bandwidth 8000000 qos-parameter subscriber-weight 6 qos-parameter max-subscriber-video-bandwidth 3000000 qos-parameter max-100Kbps-voice-calls 3 qos-profile subscriber-triple-play exit Copyright © 2010, Juniper Networks, Inc.
  • Page 274 JunosE 11.3.x Quality of Service Configuration Guide Copyright © 2010, Juniper Networks, Inc.

  • Page 275: Configuring Hierarchical Qos Parameters

    For information about the IP multicast bandwidth adjustment application, see IP Multicast Bandwidth Adjustment for QoS Overview on page 253 Guidelines for Configuring Hierarchical Parameters Use the following guidelines when specifying a hierarchical parameter: Copyright © 2010, Juniper Networks, Inc.

  • Page 276: Configuring A Parameter Definition To Calculate Hierarchical Instances

    The system computes the values of an implicit instance as the sum of the values of the explicit instances stacked above the implicit instance. To configure a hierarchical QoS parameter definition: Copyright © 2010, Juniper Networks, Inc.

  • Page 277: Example: Qos Parameter Configuration For Hierarchical Parameters

    10 that equals the total rate at the VLANs (3072000). Figure 62: Hierarchical Parameters Scheduler Hierarchy Procedure for QoS Administrators This section describes the procedures to configure the scheduler hierarchy shown in Figure 62 on page 247 by using QoS parameters. Copyright © 2010, Juniper Networks, Inc.
  • Page 278 Configure the QoS profile for the VLAN interfaces. a. Configure the QoS profile named qp-shape-cvlan. b. Configure the VLAN queue and reference the best-effort traffic class. c. Configure the VLAN node and reference the scheduler profile for shaping VLANs. Copyright © 2010, Juniper Networks, Inc.

  • Page 279: Procedure For Qos Clients

    Attach the max-sub-bw QoS parameter to the subinterface with a value of 2048000. d. Attach the qp-shape-cvlan QoS profile to the subinterface. host1(config-if)#interface gigabitEthernet 2/0.101 host1(config-if)#svlan id 10 101 host1(config-if)#qos-parameter max-sub-bw 2048000 host1(config-if)#qos-profile qp-shape-cvlan Copyright © 2010, Juniper Networks, Inc.

  • Page 280: Monitoring Hierarchical Qos Parameters

    QoS Administrator Configuration From Global Configuration mode: ! Configure the max-sub-bw QoS parameter definition. qos-parameter-define max-sub-bw hierarchical controlled-interface-type svlan controlled-interface-type vlan instance-interface-type vlan subscriber-interface-type vlan exit ! Configure the sp-shape-cvlan and sp-shape-svlan scheduler profiles. scheduler-profile sp-shape-cvlan Copyright © 2010, Juniper Networks, Inc.

  • Page 281: Qos Client Configuration

    10 101 qos-parameter max-sub-bw 2048000 qos-profile qp-shape-cvlan ! Attach the QoS profile to the S-VLAN subinterface 10. interface gigabitEthernet 2/0 svlan 10 qos-profile qp-shape-svlan Related Hierarchical QoS Parameters Overview on page 245 Documentation Copyright © 2010, Juniper Networks, Inc.
  • Page 282 JunosE 11.3.x Quality of Service Configuration Guide Copyright © 2010, Juniper Networks, Inc.

  • Page 283: Configuring Ip Multicast Bandwidth Adjustment With Qos Parameters

    VLAN node can be configured using a parameter expression such as max-subscriber-bandwidth - ip-multicast-bandwidth. In a typical IP multicast bandwidth adjustment configuration, the shaping rate or shared-shaping rate is determined by calculating the total subscriber bandwidth of the Copyright © 2010, Juniper Networks, Inc.
  • Page 284 For more information about multicast bandwidth maps and QoS adjustment, see JunosE Multicast Routing Configuration Guide For more information about configuring scheduler rates for QoS parameters, see Scheduler Profiles and Parameter Expressions for QoS Administrators on page 221 Copyright © 2010, Juniper Networks, Inc.

  • Page 285: Guidelines For Configuring Ip Multicast Adjustment For Qos

    To associate a parameter instance with the IP multicast bandwidth adjustment application: Configure traffic classes. host1(config)#traffic-class voice host1(config-traffic-class)#exit host1(config)#traffic-class best-effort host1(config-traffic-class)#exit Create a parameter definition. a. Configure the QoS parameter name and the application. host1(config)#qos-parameter-define ipm application ip-multicast hierarchical Copyright © 2010, Juniper Networks, Inc.

  • Page 286: Example: Qos Parameter Configuration For Ip Multicast Bandwidth

    IP Multicast Bandwidth Adjustment for QoS Overview on page 253 Documentation Example: QoS Parameter Configuration for IP Multicast Bandwidth Adjustment on page 257 controlled-interface-type encapsulation vlan interface gigabitEthernet node qos-parameter-define qos-profile queue scheduler-profile shared-shaping-rate Copyright © 2010, Juniper Networks, Inc.

  • Page 287: Adjustment

    The QoS administrator configures the traffic classes and traffic-class groups for Classes and best-effort data and voice services. The QoS administrator does not need to configure Traffic-Class Groups a traffic class for the video service because it is transmitted through the IP multicast connection. Copyright © 2010, Juniper Networks, Inc.
  • Page 288 Within a Scheduler instance, it enables the IP multicast bandwidth adjustment application to adjust the Profile subscriber bandwidth to account for the video traffic. The QoS administrator then configures the scheduler profile to shape voice traffic. Copyright © 2010, Juniper Networks, Inc.
  • Page 289 Attach the QoS profile vc-subscriber to the subinterface. Configure the IP address for the ATM subinterface. host1(config)#interface atm 2/0 host1(config-if)#interface atm 2/0.1 point-to-point host1(config-subif)#atm pvc 100 0 100 aal5snap host1(config-subif)#qos-profile ipm-adjusted host1(config-subif)#ip address 1.1.1.1 255.255.255.0 Copyright © 2010, Juniper Networks, Inc.

  • Page 290: Monitoring The Configuration

    10000000 - ipm 50 bytes <none> simple implicit 192k <none> <none> <none> <none> To display the attachments on all QoS profiles, including ipm-adjust, issue the show qos-profile references command. host1#show qos-profile references qos profile attachment Copyright © 2010, Juniper Networks, Inc.
  • Page 291 IP multicast parameter instances: Parameter instances reported: To display the queue forwarding rates for the ATM VC and IP interfaces on the ATM interface in slot 2, port 0, issue the show egress-queue rates command. Copyright © 2010, Juniper Networks, Inc.

  • Page 292: Complete Configuration Example

    ! Create the ipm QoS parameter definition. qos-parameter-define ipm application ip-multicast hierarchical controlled-interface-type atm-vc exit ! Create a global parameter instance of the ipm QoS parameter. qos-parameter ipm 0 ! Configure the vc-subscriber and 192K scheduler profiles. Copyright © 2010, Juniper Networks, Inc.
  • Page 293 ! Attach the parameter definition to an interface. interface atm 2/0.1 point-to-point atm pvc 100 0 100 aal5snap qos-profile ipm-adjusted ip address 1.1.1.1 255.255.255 Related IP Multicast Bandwidth Adjustment for QoS Overview on page 253 Documentation Copyright © 2010, Juniper Networks, Inc.
  • Page 294 JunosE 11.3.x Quality of Service Configuration Guide Copyright © 2010, Juniper Networks, Inc.

  • Page 295: Configuring The Shaping Mode For Ethernet With Qos Parameters

    For example, all of the interfaces stacked above the Gigabit Ethernet interface configured on slot 6, adapter 0, port 2 have cell shaping mode: host1(config)#interface gigabitEthernet 6/0/2 host1(config-if)#qos-shaping-mode cell Copyright © 2010, Juniper Networks, Inc.

  • Page 296: Module Types And Capabilities For Qos Cell Mode Application

    The internal cell-taxing mechanism does not perform the cell mode adjustment on certain interface types. On these interfaces, the system uses a parameter expression associated with the qos-cell-mode application to determine whether the cell adjustment is required. Copyright © 2010, Juniper Networks, Inc.

  • Page 297: Relationship With Qos Downstream Rate Application

    You can have only one parameter definition with the QoS cell mode application configured. You must specify a controlled-interface type. You can specify only instance-interface types of atm, atm-vp, atm-vc, ethernet, svlan, and vlan. Copyright © 2010, Juniper Networks, Inc.

  • Page 298: Mode

    Create the parameter instance and configure the shaping mode. When you create the parameter instance and configure the shaping mode, the value of frame shaping mode is 0; the value for cell shaping mode is 1. host1(config)#interface gigabitEthernet 6/0/2 host1(config-if)#encapsulation vlan Copyright © 2010, Juniper Networks, Inc.

  • Page 299: Example: Qos Parameter Configuration For Qos Cell Mode And Byte Adjustment For Cell Shaping

    2 encapsulations and the ATM cell pad, header, and trailer. Figure 64 on page 270 displays the Ethernet network to which the QoS administrator applies the byte adjustment. Copyright © 2010, Juniper Networks, Inc.

  • Page 300: Figure 64: Byte Adjustment For Vc1 And Vc2

    The QoS administrator then enables the QoS client to create a parameter instance of the byte adjustment from VLAN interfaces. All interfaces above the VLAN use the same byte adjustment value. Configure a parameter definition named byte-adjustment. Copyright © 2010, Juniper Networks, Inc.
  • Page 301 Configure the scheduler profile for the video service. a. Configure the scheduler profile named voice. b. Configure the shared-shaping rate of 8000000 with a burst of 10 milliseconds. host1(config)#scheduler-profile video host1(config-scheduler-profile)#shaping-rate 8000000 burst 10 milliseconds Copyright © 2010, Juniper Networks, Inc.
  • Page 302 Configure the VLAN major interface. c. Configure the Gigabit Ethernet interface in slot 6, adapter 0, port 0, subinterface d. Assign VLAN ID of 1. e. Create a parameter instance for byte-adjustment with a value of -28. Copyright © 2010, Juniper Networks, Inc.

  • Page 303: Complete Configuration Example

    JunosE System Basics Configuration Guide. From Global Configuration mode: ! Configure the traffic-classes for video and voice. traffic-class voice exit traffic-class video exit ! Create the byte-adjustment QoS parameter definition. qos-parameter-define byte-adjustment application qos-byte-adjustment controlled-interface-type vlan controlled-interface-type ip Copyright © 2010, Juniper Networks, Inc.
  • Page 304 -28 qos-parameter cell-mode 1 qos-profile vc1 interface gigabitEthernet 6/0/1.1 vlan id 2 qos-parameter byte-adjustment -2 qos-parameter cell-mode 1 qos-profile vc2 Related Cell Shaping Mode Using QoS Parameters Overview on page 265 Documentation Copyright © 2010, Juniper Networks, Inc.

  • Page 305: Configuring Byte Adjustment For Shaping Rates With Qos Parameters

    Managing the bandwidth of downstream ATM traffic to Ethernet interfaces is difficult because of the different layer 2 encapsulations. To reduce the number of packet drops in the Ethernet network, you can use the byte adjustment applications to account for the different encapsulations. Copyright © 2010, Juniper Networks, Inc.

  • Page 306: Calculation And Example Of Byte Adjustment For Cell Shaping

    Header Number of Bytes EnetHeader 14 bytes (6-SA, 6-DA, 2-ethertype) Vstack 8 bytes (2-vmanTci, 2-ethertype, 2-vlanTci, 2-ethertype) PppoeHeader 6 bytes (1-version/type, 1-code, 2-session id, 2-length) 2 bytes (2-protocol id) 4 bytes Total 34 bytes Copyright © 2010, Juniper Networks, Inc.

  • Page 307: Byte Adjustment For Frame Shaping Of Vdsl Traffic Overview

    Table 31: Byte Adjustment Values for Frame and Cell Shaping Modes Configured Configured Final Byte Shaping Mode qos-frame-byte-adjustment qos-byte-adjustment Adjustment on Port 0 Value Value Value Cell Any value Cell Any value Undefined Copyright © 2010, Juniper Networks, Inc.

  • Page 308: Guidelines For Configuring Byte Adjustment Of Cell And Frame Shaping Rates Using Qos Parameters

    On the ES2 10G LM, the shaping rate adjustment is performed more efficiently by the TFA ASIC than ASICS on other modules. The TFA ASIC performs an internal adjustment Copyright © 2010, Juniper Networks, Inc.

  • Page 309: Traffic

    Configure the QoS parameter name and the application. host1(config)#qos-parameter-define byteadjust1 application qos-byte-adjustment b. Configure a controlled-interface type. host1(config-qos-parameter-define)#controlled-interface-type vlan host1(config-qos-parameter-define)#controlled-interface-type ip c. Configure an instance-interface type. host1(config-qos-parameter-define)#instance-interface-type vlan Do one of the following: Copyright © 2010, Juniper Networks, Inc.

  • Page 310: Traffic

    For more information about configuring shaping modes for Ethernet, see QoS Shaping Mode for Ethernet Interfaces Overview on page 170 and Cell Shaping Mode Using QoS Parameters Overview on page 265 controlled-interface-type encapsulation vlan instance-interface-type ip address node qos-parameter qos-parameter-define qos-profile queue Copyright © 2010, Juniper Networks, Inc.

  • Page 311: Traffic

    % 2 * (1 - sp-qos-cell-mode)) TIP: To determine the expression value and the byte adjustment required, you must account for the actual segmentation header overhead added by the DSLAM. DSLAMs have different segmentation header overheads. Copyright © 2010, Juniper Networks, Inc.
  • Page 312 8 NOTE: The ancp-downstream rate and sp-qos-cell-mode QoS parameters are dynamically applied to QoS by ANCP. Related Byte Adjustment for ADSL and VDSL Traffic Overview on page 275 Documentation qos-parameter qos-parameter-define qos-profile scheduler-profile shaping-rate Copyright © 2010, Juniper Networks, Inc.

  • Page 313: Configuring The Downstream Rate Using Qos Parameters

    For VLANs configured on all other E Series Broadband Services Routers, you must also configure a parameter expression to configure the cell mode adjustment. Copyright © 2010, Juniper Networks, Inc.

  • Page 314: Qos Adaptive Mode And Downstream Rate

    For more information about configuring byte adjustment for downstream rates, see Byte Adjustment for ADSL and VDSL Traffic Overview on page 275 For information about configuring the shaping mode for ATM interfaces, see Configuring the QoS Shaping Mode for ATM Interfaces on page 166 Copyright © 2010, Juniper Networks, Inc.

  • Page 315: Guidelines For Configuring Qos Downstream Rate

    Configure traffic classes. host1(config)#traffic-class voice host1(config-traffic-class)#exit host1(config)#traffic-class best-effort host1(config-traffic-class)#exit Create a parameter definition for the QoS downstream rate application. a. Configure the QoS parameter name and the application. host1(config)#qos-parameter-define downstreamVLAN application qos-downstream-rate b. Configure controlled-interface types. Copyright © 2010, Juniper Networks, Inc.
  • Page 316 1 host1(config-if)#qos-profile vlan1 host1(config-if)#ip address 6.10.10.10 255.255.255.255 Related Example: QoS Parameter Configuration for QoS Downstream Rate on page 287 Documentation For information about downstream rate and RADIUS, see JunosE Broadband Access Configuration Guide Copyright © 2010, Juniper Networks, Inc.

  • Page 317: Example: Qos Parameter Configuration For Qos Downstream Rate

    Table 33: Shaping Rate and Shaping Mode VLAN1 VLAN2 Shaping mode Cell Cell Shaping rate 10000000 bps 100000 bps Configuring Traffic The QoS administrator configures the traffic classes for voice and video services. Classes Configure the traffic class named voice. Copyright © 2010, Juniper Networks, Inc.
  • Page 318 Define the subscriber-interface types for vlan and ethernet. host1(config-qos-parameter-define)#subscriber-interface-type vlan host1(config-qos-parameter-define)#subscriber-interface-type ethernet host1(config-qos-parameter-define)#exit Enabling QoS Adaptive The QoS administrator enables QoS adaptive mode for ANCP. Mode Enter Layer 2 Control Configuration mode. host1(config)#l2c Enable QoS adaptive mode for the system. Copyright © 2010, Juniper Networks, Inc.
  • Page 319 VLAN1 and VLAN2 subscribers. Profile Configure the vlan1 QoS profile with a shared-shaping rate that matches the downstream rate. a. Configure the QoS profile named vlan1. b. Configure the vlan node and reference the scheduler profile vlan1. Copyright © 2010, Juniper Networks, Inc.
  • Page 320 Specify the Gigabit Ethernet interface in slot 6, adapter 0, port 1. b. Assign a VLAN ID of 2. c. Attach the QoS profile vlan2 to the interface. host1(config-if)#interface gigabitEthernet 6/0/1.1 host1(config-if)#vlan id 2 host1(config-if)#qos-profile vlan2 host1(config-if)#exit Copyright © 2010, Juniper Networks, Inc.

  • Page 321: Complete Configuration Example

    8000000 burst 10 milliseconds exit scheduler-profile vlan2 shaping-rate ancpVlan burst 10 milliseconds exit ! Add the scheduler profiles to the vlan1 and vlan2 QoS profiles. qos-profile vlan1 vlan node scheduler-profile vlan1 vlan queue traffic-class voice scheduler-profile voice Copyright © 2010, Juniper Networks, Inc.
  • Page 322 ! Configure the QoS downstream rate adjustment for VLAN1 and VLAN2. interface gigabitEthernet 6/0/0 encapsulation vlan interface gigabitEthernet 6/0/1.1 vlan id 1 qos-profile vlan1 exit interface gigabitEthernet 6/0/1.1 vlan id 2 qos-profile vlan2 exit Related QoS Downstream Rate Application Overview on page 283 Documentation Copyright © 2010, Juniper Networks, Inc.

  • Page 323: Monitoring And Troubleshooting Qos

    PART 7 Monitoring and Troubleshooting QoS Monitoring QoS on E Series Routers on page 295 Troubleshooting QoS on page 337 Copyright © 2010, Juniper Networks, Inc.
  • Page 324 JunosE 11.3.x Quality of Service Configuration Guide Copyright © 2010, Juniper Networks, Inc.

  • Page 325: Monitoring Qos On E Series Routers

    Monitoring the QoS Configuration of ATM Interfaces on page 324 Monitoring the QoS Configuration of IP Interfaces on page 326 Monitoring the QoS Configuration of Fast Ethernet, Gigabit Ethernet, and 10-Gigabit Ethernet Interfaces on page 328 Copyright © 2010, Juniper Networks, Inc.

  • Page 326: Monitoring Service Levels With Traffic Classes

    Table 34: show traffic-class Output Fields Field Name Field Description traffic class Name of the traffic class fabric weight Weight of the queue in the fabric fabric strict priority Setting strict-priority queues in the fabric Copyright © 2010, Juniper Networks, Inc.

  • Page 327: Monitoring Service Levels With Traffic-Class Groups

    Table 35: show traffic-class-group Output Fields Field Name Field Description traffic-class group Name of the traffic-class group traffic-class Name of the traffic class Referenced in qos-profiles Number of times group is referenced by QoS profiles Copyright © 2010, Juniper Networks, Inc.

  • Page 328: Monitoring Queue Thresholds

    3456 bytes. While memory fills beyond the last region, all frames are dropped except control traffic, until the queues are drained and memory usage falls back into one of the regions. To display the router’s memory management: Copyright © 2010, Juniper Networks, Inc.
  • Page 329 7, only 80 percent of the 32-MB memory is allocated. To display oversubscription in region 7: host1#show qos queue-thresholds egress-slot 9 region 7 region 7 (28MB - 32MB) oversubscription 80% total exceeded conformed committed queue committed queue-profile length length length count memory Copyright © 2010, Juniper Networks, Inc.
  • Page 330 You can configure video queues with a buffer weight of 16 and Internet and multicast queues with a buffer weight of 8 to ensure that video queues get to queue twice as much traffic as Internet and multicast queues. Copyright © 2010, Juniper Networks, Inc.

  • Page 331: Monitoring Queue Profiles

    31 times in qos-profiles To display a list of QoS profiles that reference the queue profile: host1#show queue-profile references queue-profile default Referenced by QoS profiles: atm-default serial-default ethernet-default server-default Copyright © 2010, Juniper Networks, Inc.

  • Page 332: Monitoring Drop Profiles For Red And Wred

    0, <none>, <none> 0, <none>, <none> drop9 0, 750000, 80% 0, <none>, <none> 0, <none>, <none> drop10 0, 750000, 80% 0, <none>, <none> 0, <none>, <none> drop11 0, 750000, 80% 0, <none>, <none> 0, <none>, <none> Copyright © 2010, Juniper Networks, Inc.

  • Page 333: Monitoring The Qos Scheduler Hierarchy

    Action To display the scheduler hierarchy for a particular interface: host1# show qos scheduler-hierarchy interface fastEthernet 9/0 Scheduler hierarchy for the default traffic-class group assured shared rate shaping shaping Copyright © 2010, Juniper Networks, Inc.
  • Page 334 To display the QoS scheduler hierarchy for a specified interface rather than those stacked above the interface: host1#show qos scheduler-hierarchy interface fastEthernet 9/0.2 explicit Scheduler hierarchy for the default traffic-class group assured shared rate shaping shaping interface resource rate rate weight ------------- ---------------------------- ------- ------- ------- Copyright © 2010, Juniper Networks, Inc.
  • Page 335 Eth9/0.1 vlan queue best-effort vlan Eth9/0.2 vlan node vlan Eth9/0.2 vlan queue video vlan Eth9/0.2 vlan queue best-effort vlan Eth9/0.3 vlan node vlan Eth9/0.3 vlan queue video vlan Eth9/0.3 vlan queue best-effort Copyright © 2010, Juniper Networks, Inc.
  • Page 336 8 set vlanset1 set node 300000000 wgt 8 vlan Eth1/0/0.1 vlan queue best-effort wgt 8 vlan Eth1/0/0.2 vlan queue best-effort wgt 8 Scheduler hierarchy for traffic-class group EF assured shared rate shaping shaping Copyright © 2010, Juniper Networks, Inc.
  • Page 337 Eth1/0/0 ethernet port wgt 8 superset cluster superset node 800000000 wgt 8 set vlanset1 set node 300000000 wgt 8 vlan Eth1/0/0.1 vlan queue best-effort wgt 8 vlan Eth1/0/0.2 vlan queue best-effort wgt 8 Copyright © 2010, Juniper Networks, Inc.
  • Page 338 AF AF wgt 8 set vlanset2 set node AF wgt 8 vlan Eth1/0/0.3 vlan queue AF AF wgt 8 Meaning Table 39 on page 309 lists the show qos scheduler-hierarchy command output fields. Copyright © 2010, Juniper Networks, Inc.

  • Page 339: Monitoring The Configuration Of Scheduler Profiles

    39 times in qos-profiles scheduler-profile wf100 referenced 1 time in qos-profiles scheduler-profile spSV25 referenced 2 times in qos-profiles To display a list of QoS profiles that reference the scheduler profile: Copyright © 2010, Juniper Networks, Inc.

  • Page 340: Monitoring Shared Shapers

    Display information about the configured shared shapers. The best-effort queue is listed as the first resource for shared shapers that are queue controlled. The best-effort scheduler node is listed as the first resource for shared shapers that are node controlled. Copyright © 2010, Juniper Networks, Inc.

  • Page 341: Table 41: Show Qos Shared-Shaper Output Fields

    Configured shared-shaping rate in bits per second shaping rate Individual shaping rate of a traffic resource in bits per second other Actual current shaping rate in bits per second Total shared shapers Total number of shared shapers Copyright © 2010, Juniper Networks, Inc.

  • Page 342: Monitoring Shared Shaper Algorithm Variables

    Name of the simple shared shaper control control value Value of the simple shared shaper control; default values are displayed if none specified units Expressed units for the value of the simple shared shaper control Copyright © 2010, Juniper Networks, Inc.

  • Page 343: Monitoring Forwarding And Drop Events On The Egress Queue

    1/0 event-exceeding forwarded Meaning Table 43 on page 313 lists the show egress-queue events command output fields. Table 43: show egress-queue events Output Fields Field Name Field Description interface Name of the interface Copyright © 2010, Juniper Networks, Inc.

  • Page 344: Monitoring Forwarding And Drop Rates On The Egress Queue

    The S-VLAN node which is not shaped has a maximum rate of 100 Mbps. The Fast Ethernet port with a bandwidth of 100 Mbps has a maximum rate of 100 Mbps. Action To display rate statistics only for queues that have queue rate statistics enabled: Copyright © 2010, Juniper Networks, Inc.
  • Page 345 11/0 svlan 0 traffic forwarded aggregate minimum interface class rate drop rate rate --------------------------------- ----------- --------- --------- --------- svlan GigabitEthernet 11/0 svlan 0 tc1 166666666 vlan GigabitEthernet 11/0.1 166666666 ip GigabitEthernet 11/0.1 best-effort Copyright © 2010, Juniper Networks, Inc.
  • Page 346 To display rate statistics for queues belonging to a specific traffic class: host1#show egress-queue rates interface gigabitEthernet 11/0 svlan 0 traffic-class voice To filter output based on the number of queues with rates that exceed the specified value. Copyright © 2010, Juniper Networks, Inc.

  • Page 347: Table 44: Show Egress-Queue Rates Output Fields

    Queues disabled (no resources) Number of queues not displayed because no resources were available Total queues Total number of queues within the hierarchical scope of the command Copyright © 2010, Juniper Networks, Inc.

  • Page 348: Monitoring Queue Statistics For The Fabric

    Number of forwarded bytes dropped packets Number of dropped packets dropped bytes Number of dropped bytes Related Configuring Rate Statistics on page 39 Documentation Configuring Event Statistics on page 40 show fabric-queue Copyright © 2010, Juniper Networks, Inc.

  • Page 349: Monitoring The Configuration Of Statistics Profiles

    Threshold above which exceeded-drop-events are counted rate period Time frame during which statistics are gathered Related Configuring Rate Statistics on page 39 Documentation Configuring Event Statistics on page 40 show statistics-profile Copyright © 2010, Juniper Networks, Inc.

  • Page 350: Monitoring The Qos Profiles Attached To An Interface

    Interface for which the hierarchy is being displayed qos profile Name of the QoS profile and its attachment point t-class group Traffic-class groups associated with the interface interface type Type of interface to which the profile is attached Copyright © 2010, Juniper Networks, Inc.

  • Page 351: Monitoring The Configuration Of Qos Port-Type Profiles

    Attaching a QoS Profile to an Interface on page 128 Creating Parameter Instances Example: Port-Type QoS Profile Attachment on page 132 show qos-port-type-profile Monitoring the Configuration of QoS Profiles Purpose Display information about QoS profiles, including attachments to interfaces or port types. Copyright © 2010, Juniper Networks, Inc.
  • Page 352 To display information about the QoS profiles attached to a specific tunnel interface, specify the interface at the root of the scheduler hierarchy located on the tunnel-service interface or at the same hierarchy for LNS GRE tunnel traffic: Copyright © 2010, Juniper Networks, Inc.

  • Page 353: Table 48: Show Qos-Profile Output Fields

    Number of QoS profiles attached to port types DCM Profile attachments Number of QoS profiles attached to profiles for Service Manager Interface attachments Number of QoS profiles attached to interfaces Not attached Number of QoS profiles that are unattached Copyright © 2010, Juniper Networks, Inc.

  • Page 354: Monitoring The Qos Configuration Of Atm Interfaces

    Table 49 on page 324 lists the related show interfaces atm command output fields. Table 49: show interfaces atm Output Fields Field Name Field Description Administrative qos-mode-port Per-port queuing mode status: disabled, low-latency, low-cdv, none Operational qos-mode-port Per-port queuing mode status: disabled, low-latency, low-cdv, none Copyright © 2010, Juniper Networks, Inc.
  • Page 355 Configuring a QoS Profile on page 126 Attaching a QoS Profile to an Interface on page 128 Creating Parameter Instances For more information about other fields displayed with this command, see JunosE Link Layer Configuration Guide show atm interface Copyright © 2010, Juniper Networks, Inc.

  • Page 356: Monitoring The Qos Configuration Of Ip Interfaces

    Attached QoS profile QoS profile attachment at or below the displayed interface. For example, if the interface being displayed is an IP interface, and the attachment is at the VC, the VC interface attachment is displayed. Copyright © 2010, Juniper Networks, Inc.
  • Page 357 Average queue length Average length of queue in bytes Related Configuring a QoS Profile on page 126 Documentation Attaching a QoS Profile to an Interface on page 128 Creating Parameter Instances show ip interface Copyright © 2010, Juniper Networks, Inc.

  • Page 358: Monitoring The Qos Configuration Of Fast Ethernet, Gigabit Ethernet, And 10-Gigabit Ethernet Interfaces

    Reports statistics in bytes within cells and also accounts for cell encapsulation and padding overhead. none—Shaping mode is not configured. Copyright © 2010, Juniper Networks, Inc.

  • Page 359: Bundles

    Duplex Mode: Operational Full Duplex Speed: Operational 100 Mbps System Priority 32768 System MAC Address is 0090.1a00.00e0 key 8 Partner System Priority 0 System MAC Address is 0000.0000.0000 key 0 QoS parameter: vlan 1500000 Attached QoS profile: eth1 Copyright © 2010, Juniper Networks, Inc.

  • Page 360: Monitoring The Configuration Of Qos Interface Sets

    To display detailed information about a specific interface set: host1#show qos-interface-set vlan-set detail interface member member restricted parent port type count interface --------- ------- --------- ------ ------ ---------- vlan-set vlan-ss lag test1 vlan none Children: vlan lag test1.1 vlan lag test1.4 Copyright © 2010, Juniper Networks, Inc.

  • Page 361: Monitoring The Configuration Of Qos Interface Supersets

    --------- --------- ------ ---------- vlan-ss lag test1 none Children: set set Meaning Table 54 on page 332 lists the show qos-interface-superset command output fields. Copyright © 2010, Juniper Networks, Inc.

  • Page 362: Monitoring The Aaa Downstream Rate For Qos

    Documentation show aaa qos downstream-rate Monitoring QoS Parameter Instances Purpose Display the QoS parameter instances for QoS clients. Action To display information about the QoS parameters attached to a specific interface or port type: Copyright © 2010, Juniper Networks, Inc.
  • Page 363 ------------------ --------- ----- ------- ------- ----------- GigabitEthernet6/0 video default none persistent Global parameter instances: Parameter instances reported: 1 To display information about global parameter instance attachments in condensed format: Copyright © 2010, Juniper Networks, Inc.

  • Page 364: Table 56: Show Qos-Parameter Output Fields

    NVS and are deleted after a chassis reset Global parameter instances Number of parameter instances assigned to the chassis Parameter instances reported Total number of parameter instances assigned Copyright © 2010, Juniper Networks, Inc.

  • Page 365: Monitoring Qos Parameter Definitions

    Name of the parameter definition controlled interface types Types of controlled-interface types that are available for the parameter definition instance interface types Types of instance-interface types that are available for the parameter definition Copyright © 2010, Juniper Networks, Inc.
  • Page 366 Range assigned to the parameter definition properties Applications and hierarchical settings assigned to the parameter definition Related Configuring a Basic Parameter Definition for QoS Administrators on page 223 Documentation show qos-parameter-define Copyright © 2010, Juniper Networks, Inc.

  • Page 367: Troubleshooting Qos

    To display the number of queues that are disabled because of no resources, issue the show egress-queue rates command. Related Monitoring Forwarding and Drop Rates on the Egress Queue on page 314 Documentation show egress-queue rates Copyright © 2010, Juniper Networks, Inc.
  • Page 368 JunosE 11.3.x Quality of Service Configuration Guide Copyright © 2010, Juniper Networks, Inc.

  • Page 369: Index

    PART 8 Index Index on page 341 Copyright © 2010, Juniper Networks, Inc.
  • Page 370 JunosE 11.3.x Quality of Service Configuration Guide Copyright © 2010, Juniper Networks, Inc.

  • Page 371: Index

    QoS parameters........228, 247, 257 minimizing latency on the SAR........60 QoS profiles..............132 oversubscribing..............60 configuring. See specific feature, product, or ATM SAR shaping, QoS............158 protocol ATM VP conformed drop threshold...........37 interface attachments..........128 conformed-drop-threshold command......40 audience for QoS...............4 conformed-fraction command..........23 Copyright © 2010, Juniper Networks, Inc.
  • Page 372 QoS.............189 exceeded-length command..........23 monitoring for QoS............194 exceeded-threshold command........27, 31 overview for QoS............187 expressions...............48, 221 L2TP sessions QoS..................187 latency...................6 fabric-strict-priority command..........15 layer 2 control. See ANCP fabric-weight command............15 Copyright © 2010, Juniper Networks, Inc.
  • Page 373 QoS cell mode......266 phantom nodes..............141 QoS interface sets port shaping................51 terms.................196 port-type profile, QoS.............6 QoS parameters attachments..............129 802.3ad link aggregation...........176 audience................211 configuration examples......228, 247, 257 configuring for QoS administrators.......215 configuring for QoS clients........225 overview................211 Copyright © 2010, Juniper Networks, Inc.
  • Page 374 127, 144, 182, 183, 189, 223 profile.................45, 221 queue length..............20, 24 configuring...............47 queue profiles................17 SAR..................151 color-based thresholds..........18 scheduler hierarchy configuring................22 monitoring..............303 monitoring.................24 scheduler map. See QoS profile overview................17 scheduler-profile command......48, 189, 223 queue-profile command............23 Copyright © 2010, Juniper Networks, Inc.
  • Page 375 ..........319 selection............103, 111 show traffic-class............296 implicit constituents show traffic-class-group .........297 example at best-effort node......105 show qos commands example at best-effort queue......106 show qos interface-hierarchy.........320 example for mixed interface types....107 show qos queue-thresholds ........298 Copyright © 2010, Juniper Networks, Inc.
  • Page 376 JTAC............xxix text and syntax conventions..........xxviii traffic classes configuring.................14 monitoring.................16 multiple, configuration example......137 overview................13 traffic flow..................4 traffic-class command.........14, 16, 189, 224 traffic-class groups monitoring.................16 multiple................14 overview................14 traffic-class-group command..........15 triple play configurations...........98, 229 Copyright © 2010, Juniper Networks, Inc.

This manual is also suitable for:

Junose 11.3

Table of Contents