Swconfig Qos
Swconfig Qos
Swconfig Qos
Release
12.1.x
Published: 2011-03-17
Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, California 94089 USA 408-745-2000 www.juniper.net Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners. Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice. 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.
JunosE Software for E Series Broadband Services Routers Quality of Service Configuration Guide Release 12.1.x Copyright 2011, Juniper Networks, Inc. All rights reserved. Revision History April 2011FRS JunosE 12.1.x The information in this document is current as of the date listed in the revision history. YEAR 2000 NOTICE Juniper Networks hardware and software products are Year 2000 compliant. The Junos OS has no known time-related limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036.
ii
iii
Software in any manner that extends or is broader than the uses purchased by Customer from Juniper or an authorized Juniper reseller; (i) use Embedded Software on non-Juniper equipment; (j) use Embedded Software (or make it available for use) on Juniper equipment that the Customer did not originally purchase from Juniper or an authorized Juniper reseller; (k) disclose the results of testing or benchmarking of the Software to any third party without the prior written consent of Juniper; or (l) use the Software in any manner other than as expressly provided herein. 5. Audit. Customer shall maintain accurate records as necessary to verify compliance with this Agreement. Upon request by Juniper, Customer shall furnish such records to Juniper and certify its compliance with this Agreement. 6. Confidentiality. The Parties agree that aspects of the Software and associated documentation are the confidential property of Juniper. As such, Customer shall exercise all reasonable commercial efforts to maintain the Software and associated documentation in confidence, which at a minimum includes restricting access to the Software to Customer employees and contractors having a need to use the Software for Customers internal business purposes. 7. Ownership. Juniper and Junipers licensors, respectively, retain ownership of all right, title, and interest (including copyright) in and to the Software, associated documentation, and all copies of the Software. Nothing in this Agreement constitutes a transfer or conveyance of any right, title, or interest in the Software or associated documentation, or a sale of the Software, associated documentation, or copies of the Software. 8. Warranty, Limitation of Liability, Disclaimer of Warranty. The warranty applicable to the Software shall be as set forth in the warranty statement that accompanies the Software (the Warranty Statement). Nothing in this Agreement shall give rise to any obligation to support the Software. Support services may be purchased separately. Any such support shall be governed by a separate, written support services agreement. TO THE MAXIMUM EXTENT PERMITTED BY LAW, JUNIPER SHALL NOT BE LIABLE FOR ANY LOST PROFITS, LOSS OF DATA, OR COSTS OR PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, OR FOR ANY SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THIS AGREEMENT, THE SOFTWARE, OR ANY JUNIPER OR JUNIPER-SUPPLIED SOFTWARE. IN NO EVENT SHALL JUNIPER BE LIABLE FOR DAMAGES ARISING FROM UNAUTHORIZED OR IMPROPER USE OF ANY JUNIPER OR JUNIPER-SUPPLIED SOFTWARE. EXCEPT AS EXPRESSLY PROVIDED IN THE WARRANTY STATEMENT TO THE EXTENT PERMITTED BY LAW, JUNIPER DISCLAIMS ANY AND ALL WARRANTIES IN AND TO THE SOFTWARE (WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE), INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT DOES JUNIPER WARRANT THAT THE SOFTWARE, OR ANY EQUIPMENT OR NETWORK RUNNING THE SOFTWARE, WILL OPERATE WITHOUT ERROR OR INTERRUPTION, OR WILL BE FREE OF VULNERABILITY TO INTRUSION OR ATTACK. In no event shall Junipers or its suppliers or licensors liability to Customer, whether in contract, tort (including negligence), breach of warranty, or otherwise, exceed the price paid by Customer for the Software that gave rise to the claim, or if the Software is embedded in another Juniper product, the price paid by Customer for such other product. Customer acknowledges and agrees that Juniper has set its prices and entered into this Agreement in reliance upon the disclaimers of warranty and the limitations of liability set forth herein, that the same reflect an allocation of risk between the Parties (including the risk that a contract remedy may fail of its essential purpose and cause consequential loss), and that the same form an essential basis of the bargain between the Parties. 9. Termination. Any breach of this Agreement or failure by Customer to pay any applicable fees due shall result in automatic termination of the license granted herein. Upon such termination, Customer shall destroy or return to Juniper all copies of the Software and related documentation in Customers possession or control. 10. Taxes. All license fees payable under this agreement are exclusive of tax. Customer shall be responsible for paying Taxes arising from the purchase of the license, or importation or use of the Software. If applicable, valid exemption documentation for each taxing jurisdiction shall be provided to Juniper prior to invoicing, and Customer shall promptly notify Juniper if their exemption is revoked or modified. All payments made by Customer shall be net of any applicable withholding tax. Customer will provide reasonable assistance to Juniper in connection with such withholding taxes by promptly: providing Juniper with valid tax receipts and other required documentation showing Customers payment of any withholding taxes; completing appropriate applications that would reduce the amount of withholding tax to be paid; and notifying and assisting Juniper in any audit or tax proceeding related to transactions hereunder. Customer shall comply with all applicable tax laws and regulations, and Customer will promptly pay or reimburse Juniper for all costs and damages related to any liability incurred by Juniper as a result of Customers non-compliance or delay with its responsibilities herein. Customers obligations under this Section shall survive termination or expiration of this Agreement. 11. Export. Customer agrees to comply with all applicable export laws and restrictions and regulations of any United States and any applicable foreign agency or authority, and not to export or re-export the Software or any direct product thereof in violation of any such restrictions, laws or regulations, or without all necessary approvals. Customer shall be liable for any such violations. The version of the Software supplied to Customer may contain encryption or other capabilities restricting Customers ability to export the Software without an export license.
iv
12. Commercial Computer Software. The Software is commercial computer software and is provided with restricted rights. Use, duplication, or disclosure by the United States government is subject to restrictions set forth in this Agreement and as provided in DFARS 227.7201 through 227.7202-4, FAR 12.212, FAR 27.405(b)(2), FAR 52.227-19, or FAR 52.227-14(ALT III) as applicable. 13. Interface Information. To the extent required by applicable law, and at Customer's written request, Juniper shall provide Customer with the interface information needed to achieve interoperability between the Software and another independently created program, on payment of applicable fee, if any. Customer shall observe strict obligations of confidentiality with respect to such information and shall use such information in compliance with any applicable terms and conditions upon which Juniper makes such information available. 14. Third Party Software. Any licensor of Juniper whose software is embedded in the Software and any supplier of Juniper whose products or technology are embedded in (or services are accessed by) the Software shall be a third party beneficiary with respect to this Agreement, and such licensor or vendor shall have the right to enforce this Agreement in its own name as if it were Juniper. In addition, certain third party software may be provided with the Software and is subject to the accompanying license(s), if any, of its respective owner(s). To the extent portions of the Software are distributed under and subject to open source licenses obligating Juniper to make the source code for such portions publicly available (such as the GNU General Public License (GPL) or the GNU Library General Public License (LGPL)), Juniper will make such source code portions (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 94089, ATTN: General Counsel. You may obtain a copy of the GPL at http://www.gnu.org/licenses/gpl.html, and a copy of the LGPL at http://www.gnu.org/licenses/lgpl.html . 15. Miscellaneous. This Agreement shall be governed by the laws of the State of California without reference to its conflicts of laws principles. The provisions of the U.N. Convention for the International Sale of Goods shall not apply to this Agreement. For any disputes arising under this Agreement, the Parties hereby consent to the personal and exclusive jurisdiction of, and venue in, the state and federal courts within Santa Clara County, California. This Agreement constitutes the entire and sole agreement between Juniper and the Customer with respect to the Software, and supersedes all prior and contemporaneous agreements relating to the Software, whether oral or written (including any inconsistent terms contained in a purchase order), except that the terms of a separate written agreement executed by an authorized Juniper representative and Customer shall govern to the extent such terms are inconsistent or conflict with terms contained herein. No modification to this Agreement nor any waiver of any rights hereunder shall be effective unless expressly assented to in writing by the party to be charged. If any portion of this Agreement is held invalid, the Parties agree that such invalidity shall not affect the validity of the remainder of this Agreement. This Agreement and associated documentation has been written in the English language, and the Parties agree that the English version will govern. (For Canada: Les parties aux prsents confirment leur volont que cette convention de mme que tous les documents y compris tout avis qui s'y rattach, soient redigs en langue anglaise. (Translation: The parties confirm that this Agreement and all related documentation is and will be in the English language)).
vi
Part 1
Chapter 1
Part 2
Chapter 2 Chapter 3 Chapter 4 Chapter 5
Part 3
Chapter 6 Chapter 7 Chapter 8 Chapter 9 Chapter 10 Chapter 11 Chapter 12 Chapter 13 Chapter 14
Part 4
Chapter 15 Chapter 16 Chapter 17 Chapter 18
Part 5
Chapter 19 Chapter 20 Chapter 21
vii
Chapter 22 Chapter 23
Configuring QoS for L2TP Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Configuring Interface Sets for QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Part 6
Chapter 24 Chapter 25 Chapter 26 Chapter 27 Chapter 28 Chapter 29 Chapter 30
Part 7
Chapter 31 Chapter 32
Part 8
Index
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
viii
Table of Contents
About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii
E Series and JunosE Documentation and Release Notes . . . . . . . . . . . . . . . . . . xxvii Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii E Series and JunosE Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . xxvii Obtaining Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxx Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxx
Part 1
Chapter 1
Part 2
Chapter 2
Chapter 3
ix
Color-Based Thresholding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Memory Requirements for Queue and Buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Guidelines for Managing Queue Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Guidelines for Configuring a Maximum Threshold . . . . . . . . . . . . . . . . . . . . . . 19 Guidelines for Configuring a Minimum Threshold . . . . . . . . . . . . . . . . . . . . . . 20 Guidelines for Managing Buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Guidelines for Managing Buffer Starvation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Configuring Queue Profiles to Manage Buffers and Thresholds . . . . . . . . . . . . . . . 22 Monitoring Queues and Buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Chapter 4
Chapter 5
Part 3
Chapter 6
Table of Contents
Chapter 7
Chapter 8
Chapter 9
Chapter 10
xi
Simple Shared Shaping for Triple-Play Networks . . . . . . . . . . . . . . . . . . . . . . 76 Configuring Simple Shared Shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Example: Simple Shared Shaping for ATM VCs . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Example: Simple Shared Shaping for ATM VPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Example: Simple Shared Shaping for Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Chapter 11
Chapter 12
Chapter 13
Chapter 14
Part 4
Chapter 15
Chapter 16
xii
Table of Contents
Attaching a QoS Profile to an S-VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Attaching a QoS Profile to a Port Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Munged QoS Profile Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Sample Munged QoS Profile Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Example: Port-Type QoS Profile Attachment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Example: QoS Profile Attachment to Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Example: Diffserv Configuration with Multiple Traffic-Class Groups . . . . . . . . . . 137
Chapter 17
Chapter 18
Part 5
Chapter 19
Chapter 20
Configuring QoS for Gigabit Ethernet Interfaces and VLAN Subinterfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Providing QoS for Ethernet Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 QoS Shaping Mode for Ethernet Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . 172 Configuring the QoS Shaping Mode for Ethernet Interfaces . . . . . . . . . . . . . . . . . 173 Creating a QoS Interface Hierarchy for Bulk-Configured VLAN Subinterfaces with RADIUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Monitoring QoS Configurations for Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
xiii
Chapter 21
Chapter 22
Chapter 23
xiv
Table of Contents
Scheduling and Shaping Interface Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Configuring Interface Sets for Scheduling and Queuing . . . . . . . . . . . . . . . . . . . 203 Configuring Interface Supersets for QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Configuring an Interface Superset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Restricting an Interface Superset to an S-VLAN ID or an ATM VP . . . . . . . . 204 Configuring Interface Sets for QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Configuring an Interface Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Deleting an Interface Set from an Interface Superset . . . . . . . . . . . . . . . . . . 205 Adding Member Interfaces to an Interface Set . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Adding Interfaces to an Interface Set with the CLI . . . . . . . . . . . . . . . . . . . . 206 Adding Interfaces to an Interface Set with RADIUS . . . . . . . . . . . . . . . . . . . 206 Changing and Deleting Interface Members in an Interface Set . . . . . . . . . . . 207 Changing Interface Members with Upper-Layer Protocols in an Interface Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Creating a QoS Parameter on an Interface Superset or Interface Set . . . . . . . . . 208 Configuring a QoS Parameter Definition for an Interface Superset or an Interface Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Creating a QoS Parameter Instance for an Interface Superset . . . . . . . . . . 208 Creating a QoS Parameter Instance for an Interface Set . . . . . . . . . . . . . . . 209 Attaching a QoS Profile to an Interface Superset or an Interface Set . . . . . . . . . 209 Configuring a QoS Profile for an Interface Superset or an Interface Set . . . 209 Attaching a QoS Profile to an Interface Superset . . . . . . . . . . . . . . . . . . . . . 210 Attaching a QoS Profile to an Interface Set . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Deleting an Interface Superset or an Interface Set . . . . . . . . . . . . . . . . . . . . . . . . . 211 Deleting an Interface Superset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Deleting an Interface Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Example: Configuring Interface Sets for 802.3ad Link Aggregation Groups . . . . . 212
Part 6
Chapter 24
Chapter 25
xv
Applications and QoS Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Scheduler Profiles and Parameter Expressions for QoS Administrators . . . . . . . 225 Referencing a Parameter Definition in a Scheduler Profile . . . . . . . . . . . . . . 225 Removing or Modifying a Scheduler Profile . . . . . . . . . . . . . . . . . . . . . . 225 Using Expressions for QoS Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Operators and Precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Specifying a Range in Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Configuring a Basic Parameter Definition for QoS Administrators . . . . . . . . . . . . 227 Parameter Instances for QoS Clients Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Global QoS Parameter Instance Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 230 QoS Parameters for Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Creating Parameter Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Creating a Global Parameter Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Creating a Parameter Instance for an Interface . . . . . . . . . . . . . . . . . . . . . . . 231 Creating a Parameter Instance for an ATM VP . . . . . . . . . . . . . . . . . . . . . . . . 231 Creating a Parameter Instance for an S-VLAN . . . . . . . . . . . . . . . . . . . . . . . 232 Example: QoS Parameter Configuration for Controlling Subscriber Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Procedure for QoS Administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Procedure for QoS Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Monitoring the Subscriber Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 Complete Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 QoS Administrator Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 QoS Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Chapter 26
Chapter 27
Chapter 28
Configuring the Shaping Mode for Ethernet with QoS Parameters . . . . . 269
Cell Shaping Mode Using QoS Parameters Overview . . . . . . . . . . . . . . . . . . . . . 269 Overriding the QoS Shaping Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 Module Types and Capabilities for QoS Cell Mode Application . . . . . . . . . . 270
xvi
Table of Contents
Cell Tax Adjustment Using QoS Cell Mode . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Relationship with QoS Downstream Rate Application . . . . . . . . . . . . . . . . . . 271 Guidelines for Configuring the Cell Shaping Mode with QoS Parameters . . . . . . 271 Configuring a Parameter Definition to Shape Ethernet Traffic Using Cell Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 Example: QoS Parameter Configuration for QoS Cell Mode and Byte Adjustment for Cell Shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 Complete Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Chapter 29
Configuring Byte Adjustment for Shaping Rates with QoS Parameters . . 279
Byte Adjustment for ADSL and VDSL Traffic Overview . . . . . . . . . . . . . . . . . . . . 279 Byte Adjustment for Cell Shaping of ADSL Traffic Overview . . . . . . . . . . . . 279 Calculation and Example of Byte Adjustment for Cell Shaping . . . . . . 280 Byte Adjustment for Frame Shaping of VDSL Traffic Overview . . . . . . . . . . 281 System Calculation for Byte Adjustment of ADSL and VDSL Traffic . . . . . . . 281 Guidelines for Configuring Byte Adjustment of Cell and Frame Shaping Rates Using QoS Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Configuring a Parameter Definition to Adjust Cell Shaping Rates for ADSL Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 Configuring a Parameter Definition to Adjust Frame Shaping Rates for VDSL Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Chapter 30
Part 7
Chapter 31
xvii
Monitoring the Configuration of QoS Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 Monitoring the QoS Configuration of ATM Interfaces . . . . . . . . . . . . . . . . . . . . . . 328 Monitoring the QoS Configuration of IP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . 330 Monitoring the QoS Configuration of Fast Ethernet, Gigabit Ethernet, and 10-Gigabit Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 Monitoring the QoS Configuration of IEEE 802.3ad Link Aggregation Group Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 Monitoring the Configuration of QoS Interface Sets . . . . . . . . . . . . . . . . . . . . . . . 334 Monitoring the Configuration of QoS Interface Supersets . . . . . . . . . . . . . . . . . . 335 Monitoring the AAA Downstream Rate for QoS . . . . . . . . . . . . . . . . . . . . . . . . . . 336 Monitoring QoS Parameter Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 Monitoring QoS Parameter Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Chapter 32
Part 8
Index
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
xviii
List of Figures
Part 1
Chapter 1
Part 2
Chapter 4
Part 3
Chapter 6
Chapter 7
Chapter 8
Chapter 9
Chapter 10
Chapter 11
xix
Figure 22: Simple Shared Shaper Behavior Without Algorithm Controls . . . . . . . 85 Figure 23: Less Conservative Simple Shared Shaper Behavior . . . . . . . . . . . . . . . 86 Figure 24: More Liberal Simple Shared Shaper Behavior . . . . . . . . . . . . . . . . . . . . 86 Figure 25: Dynamic Rate When Video Flow Starts . . . . . . . . . . . . . . . . . . . . . . . . . 92 Figure 26: Dynamic Rate When Video Flow Stops . . . . . . . . . . . . . . . . . . . . . . . . . 93
Chapter 12
Chapter 13
Part 4
Chapter 16
Chapter 17
Part 5
Chapter 19
Chapter 21
Chapter 22
xx
List of Figures
Figure 52: LNS (Non-MLPPP) Scheduler Hierarchy . . . . . . . . . . . . . . . . . . . . . . . 190 Figure 53: LNS (MLPPP) QoS Scheduler Hierarchy . . . . . . . . . . . . . . . . . . . . . . . 190 Figure 54: LAC over Ethernet (Without VLANs) Scheduler Hierarchy . . . . . . . . . 190 Figure 55: LAC over Ethernet (With LANs) Scheduler Hierarchy . . . . . . . . . . . . . . 191 Figure 56: LAC over ATM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Chapter 23
Part 6
Chapter 24
Chapter 25
Chapter 26
Chapter 27
Chapter 28
Configuring the Shaping Mode for Ethernet with QoS Parameters . . . . . 269
Figure 64: Byte Adjustment for VC1 and VC2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Chapter 29
Configuring Byte Adjustment for Shaping Rates with QoS Parameters . . 279
Figure 65: Byte Adjustment Calculation for Ethernet and ATM Encapsulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
xxi
xxii
List of Tables
About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii
Table 1: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxviii Table 2: Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxviii
Part 1
Chapter 1
Part 2
Chapter 3
Part 3
Chapter 9
Chapter 11
Chapter 13
Part 4
Chapter 16
Chapter 17
xxiii
Part 5
Chapter 19
Chapter 20
Configuring QoS for Gigabit Ethernet Interfaces and VLAN Subinterfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Table 19: Operational Shaping Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Chapter 21
Chapter 23
Part 6
Chapter 24
Chapter 25
Chapter 28
Configuring the Shaping Mode for Ethernet with QoS Parameters . . . . . 269
Table 27: Supported Interfaces for qos-shaping-mode and qos-cell-mode Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Table 28: Byte Adjustment for Subscribers VC1 and VC2 . . . . . . . . . . . . . . . . . . . 274
Chapter 29
Configuring Byte Adjustment for Shaping Rates with QoS Parameters . . 279
Table 29: Header Lengths for Ethernet Encapsulation . . . . . . . . . . . . . . . . . . . . 280 Table 30: Header Lengths for ATM Encapsulation . . . . . . . . . . . . . . . . . . . . . . . . 281 Table 31: Byte Adjustment Values for Frame and Cell Shaping Modes . . . . . . . . 281
Chapter 30
Part 7
Chapter 31
xxiv
List of Tables
Table 41: show qos shared-shaper Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . 315 Table 42: show qos shared-shaper-control Output Fields . . . . . . . . . . . . . . . . . . 316 Table 43: show egress-queue events Output Fields . . . . . . . . . . . . . . . . . . . . . . . 317 Table 44: show egress-queue rates Output Fields . . . . . . . . . . . . . . . . . . . . . . . . 321 Table 45: show fabric-queue Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 Table 46: show statistics-profile Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 323 Table 47: show qos interface-hierarchy Output Fields . . . . . . . . . . . . . . . . . . . . . 324 Table 48: show qos-profile Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 Table 49: show interfaces atm Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 Table 50: show ip interface Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 Table 51: show interfaces Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 Table 52: show interfaces lag members Output Fields . . . . . . . . . . . . . . . . . . . . 334 Table 53: show qos-interface-set Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . 335 Table 54: show qos-interface-superset Output Fields . . . . . . . . . . . . . . . . . . . . . 336 Table 55: show aaa qos downstream-rate Output Fields . . . . . . . . . . . . . . . . . . 336 Table 56: show qos-parameter Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 Table 57: show qos-parameter-define Output Fields . . . . . . . . . . . . . . . . . . . . . 339
xxv
xxvi
E Series and JunosE Documentation and Release Notes on page xxvii Audience on page xxvii E Series and JunosE Text and Syntax Conventions on page xxvii Obtaining Documentation on page xxix Documentation Feedback on page xxix Requesting Technical Support on page xxix
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.
xxvii
Description
Indicates important features or instructions.
Caution
Warning
Laser warning
Table 2 on page xxviii defines text and syntax conventions that we use throughout the E Series and JunosE documentation.
Description
Represents commands and keywords in text.
Examples
Represents text that the user must type. Represents information as displayed on your terminals screen.
Routing Process OSPF 2 with Router ID 5.5.0.250 Router is an Area Border Router (ABR) Italic text like this
Emphasizes words. Identifies variables. Identifies chapter, appendix, and book names.
There are two levels of access: user and privileged. clusterId, ipAddress. Appendix A, System Specifications
Press Ctrl + b.
xxviii
Description
Represents a choice to select one keyword or variable to the left or to the right of this symbol. (The keyword or variable can be either optional or required.) Represent optional keywords or variables. Represent optional keywords or variables that can be entered more than once. Represent required keywords or variables.
Examples
diagnostic | line
{ } (braces)
Obtaining Documentation
To obtain the most current version of all Juniper Networks technical documentation, see the Technical Documentation page on the Juniper Networks Web site at http://www.ju niper.net/. To download complete sets of technical documentation to create your own 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 athttp://www.juniper.net/.
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can improve the documentation to better meet your needs. Send your comments to techpubs-comments@juniper.net, or fill out the documentation feedback form at ht tps://www.juniper.net/cgi-bin/docbugreport/. If you are using e-mail, be sure to include the following information with your comments:
xxix
or are covered under warranty, and need post-sales technical support, you can access our tools and resources online or open a case with JTAC.
JTAC policiesFor a complete understanding of our JTAC procedures and policies, review the JTAC User Guide located at http://www.juniper.net/us/en/local/pdf/resourceguides/7100059-en.pdf . Product warrantiesFor product warranty information, visit http://www.juniper.net/sup port/warranty/ . JTAC hours of operationThe JTAC centers have resources available 24 hours a day, 7 days a week, 365 days a year.
Find CSC offerings: http://www.juniper.net/customers/support/ Search for known bugs: http://www2.juniper.net/kb/ Find product documentation: http://www.juniper.net/techpubs/ Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/ Download the latest versions of software and review release notes: http://www.juni
per.net/customers/csc/software/
To verify service entitlement by product serial number, use our Serial Number Entitlement (SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/
Use the Case Management tool in the CSC at http://www.juniper.net/cm/ . Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).
For international or direct-dial options in countries without toll-free numbers, see ht tp://www.juniper.net/support/requesting-support.html .
xxx
PART 1
CHAPTER 1
QoS on the E Series Router Overview on page 3 QoS Audience on page 4 QoS Platform Considerations on page 4 QoS Terms on page 5 QoS Features on page 7 Configuring QoS on the E Series Router on page 9 QoS References on page 9
IETF architecture for differentiated services Assured forwarding per-hop-behavior (PHB) groups Expedited forwarding PHB groups
The router supports configurable queuing and scheduling. It has an application-specific integrated circuit (ASIC) scheduler that supports thousands of queues in a hierarchical
round-robin (HRR) scheduler. The scheduler allows the router to allocate separate queues for each forwarding interface. Separate queues enable fair access to buffers and bandwidth for each subscriber connected to the router. Allocating queues per interface allows an Internet service provider (ISP) to shape an individual subscribers traffic flows to specified rates independent of the underlying Layer 2 network type. Related Documentation
For a list of related RFCs, see Configuring QoS on the E Series Router on page 9
QoS Audience
This topic collection contains 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 drop profiles, queue profiles, scheduler profiles, QoS profiles, and QoS parameter definitions. QoS clients are responsible for configuring services for individual subscribers by creating parameter instances. The parameter instances that QoS clients can create depend on the settings defined in parameter definitions by the QoS administrator. Related Documentation
For information about QoS users and QoS parameters, see QoS Parameter Audience on page 215
E Series router
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.
Interface Specifiers
The majority of the configuration task examples in this topic collection use the slot/port format to specify an interface. However, the interface specifier format that you use depends on the router that you are using. For ERX7xx models, ERX14xx models, and ERX310 routers, use the slot/port format. For example, the following command specifies an ATM interface on slot 0, port 1 of an ERX7xx model, ERX14xx model, or ERX310 router.
host1(config)#interface gigabitEthernet 0/1
For E120 and E320 routers, use the slot/adapter/port format, which includes an identifier for the bay in which the I/O adapter (IOA) resides. In the software, adapter 0 identifies the right IOA bay (E120 router) and the upper IOA bay (E320 router); adapter 1 identifies the left IOA bay (E120 router) and the lower IOA bay (E320 router). For example, the following command specifies a10-Gigabit Ethernet interface on slot 5, adapter 0, port 0 of an E320 router.
host1(config)#interface tenGigabitEthernet 5/0/0
Related Documentation
For more information about supported interface types and specifiers on E Series routers, see Interface Types and Specifiers.
QoS Terms
Table 3 on page 5 defines terms used in this discussion of QoS.
Description
Bandwidth guaranteed until the node below in the scheduler hierarchy is oversubscribed. Network forwards as many packets as possible in as reasonable a time as possible. This is the default per-hop behavior (PHB) for packet transmission. For a logical interface, the queue associated with the best-effort traffic class for that logical interface, The scheduler node associated with a logical interface and traffic class group pair, and where the traffic class group contains the best-effort traffic class. Also known as best-effort node. Cell delay variation. Measures the difference between a cells expected and actual transfer delay. Determines the amount of jitter. Cell delay variation tolerance. Specifies the acceptable tolerance of CDV (jitter).
Best effort
Best-effort queue
CDV
CDVT
Description
The result of a weight or an assured rate. Users configure the scheduler node by specifying either an assured rate or a weight within a scheduler profile. An assured rate, in bits per second, is translated into a weight. The resultant weight is referred to as an effective weight. A scheduler node associated with a {port interface, traffic-class group} pair. Because the logical interface is the port, only one such scheduler node can exist for each traffic-class group above the port. This node aggregates all traffic for traffic classes in the group. Hierarchical assured rate. Dynamically adjusts bandwidth for scheduler nodes. Hierarchical round-robin. Allocates bandwidth to queues in proportion to their weights. Delay in the transmission of a packet through a network from beginning to end. Supported on the E Series router.
Group node
HAR
HRR
Latency
First-in-first-out (FIFO) set of buffers that control packets on the data path. Supplies the QoS information for forwarding interfaces stacked above ports of the associated interface type. Applies the rules in the QoS profile to a specific interface. Allows you to throttle a queue to a specified rate. Random early detection congestion avoidance technique. A hierarchical, tree-like arrangement of scheduler nodes and queues. The router supports up to three levels of scheduler nodes stacked above a port. The port scheduler is at level 0, with two levels of scheduler nodes at levels 1 and 2. A final level of queues is stacked above the nodes. An element within the hierarchical scheduler that implements bandwidth controls for a group of queues. Queues are stacked above scheduler nodes in a hierarchy. The root node is associated with a channel or physical port. Bandwidth in a queue or node can be throttled to a specified rate.
Scheduler node
Shaping rate
Description
All nodes and queues that are associated with a logical interface that is being shared shaped are considered potential constituents of the shared shaper. Specifies the relative weight for queues in the traffic class. Weighted random early detection congestion avoidance technique.
Weight WRED
QoS Features
Table 4 on page 7 describes the major QoS features supported on the E Series router.
Description
Default traffic class for packets being forwarded across the device. Packets that are not assigned to a specific traffic class are assigned to the best-effort traffic class.
Differentiated services
Drop profile
Template that specifies active queue management in the form of WRED behavior of an egress queue. Shapes the aggregate traffic through a port or channel to a rate that is less than the line or port rate. Creates a queuing architecture without the numeric subscriber rates and weights in scheduler profiles. You then use the same QoS and scheduler profiles across all subscribers who use the same services but at different bandwidths, reducing the total number of QoS profiles and scheduler profiles required. QoS profile that is automatically attached to ports of the corresponding type if you do not explicitly attach a QoS profile. Collection of QoS commands that specify queue profiles, drop profiles, scheduler profiles, and statistics profiles in combination with interface types. Template that specifies the buffering and tail-dropping behavior of an egress queue.
Port shaping
QoS parameters
QoS profile
Queue profile
Description
Mechanism that throttles the rate at which an interface can transmit packets. Note: Rate shaping as presented in policy management in releases before JunosE Release 4.0 is deprecated and converted to QoS profiles and scheduler profiles.
Provides strict-priority scheduling within a shaped aggregate rate. For example, it lets you provide 1 Mbps of aggregate bandwidth to a subscriber, with up to 500 Kbps of the bandwidth for low-latency traffic. If there is no strict-priority traffic, the low-latency traffic can use up to the full aggregate rate of 1 Mbps. Configures the bandwidth at which queues drain as a function of relative weight, assured rate, and shaping rate. Mechanism for shaping a logical interface's aggregate traffic to a rate when the traffic for that logical interface is queued through more than one scheduler hierarchy. Template that specifies rate statistics and event-gathering characteristics. Designates the traffic class (queue) that receives top priority for transmission of its packets through a port. It is implemented with a special strict-priority scheduler node that is stacked directly above the port. A chassis-wide grouping of queues and buffers that support transmission of a designated set of traffic across the chassis, from ingress line module, through the switch fabric, and onto the egress line module. The router supports up to eight traffic classes, and therefore up to eight queues per logical interface.
Scheduler profile
Statistics profile
Strict-priority scheduling
Traffic class
Traffic-class group
Separate hierarchy of scheduler nodes and queues over a port. A traffic-class group uses one level of the scheduler hierarchy, level 1. Traffic classes belong to the default group unless they are specifically assigned to a named group. All queues are stacked in a single scheduler hierarchy above the physical port. When you configure a traffic class inside a group, its queues are stacked separately. The most common reason for creating separate scheduler hierarchies is to implement strict priority scheduling for all queues in the group. The router supports up to four traffic-class groups. A traffic class cannot belong to more than one group.
WRED
Signals end-to-end protocols such as TCP that the router is becoming congested along a particular egress path. 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.
Create and configure a traffic class. See Traffic Class and Traffic-Class Groups Overview on page 13.
Configure shaping and shared shaping using the scheduler profile. See Rate Shaping and Port Shaping Overview on page 51, Simple Shared Shaping Overview on page 75, and Compound Shared Shaping Overview on page 95.
Configure shaping rates independent of the QoS profile and scheduler profile using QoS parameters. See Parameter Definition Attributes for QoS Administrators Overview on page 219.
8. Create a QoS profile. QoS profiles reference queue, drop, statistics, and scheduler
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:
RFC 2474Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers (December 1998) RFC 2475An Architecture for Differentiated Services (December 1998) RFC 2597Assured Forwarding PHB Group (June 1999) RFC 2598An Expedited Forwarding PHB (June 1999) RFC 2698A Two Rate Three Color Marker (September 1999) RFC 2990Next Steps for the IP QoS Architecture (November 2000) RFC 2998A Framework for Integrated Services Operation over Diffserv Networks (November 2000) RFC 3246An Expedited Forwarding PHB (Per-Hop Behavior) (March 2002) RFC 3260New Terminology and Clarifications for Diffserv (April 2002) DSL Forum Technical Report (TR)-059DSL 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
10
PART 2
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
11
12
CHAPTER 2
Traffic Class and Traffic-Class Groups Overview on page 13 Configuring Traffic Classes That Define Service Levels on page 14 Configuring Traffic-Class Groups That Define Service Levels on page 15 Monitoring Traffic Classes and Traffic-Class Groups for Defined Levels of Service on page 16
Classified into a traffic class on ingress or egress by input policies Queued on fabric queues that are specific to the traffic class Queued on the egress line module on queues that are specific to the traffic class Scheduled for transmission by the scheduler
Best-Effort Forwarding
The router has a default traffic class called best-effort. You cannot delete this class. You can add the best-effort class to a traffic-class group. 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.
13
Packets arrive at an egress line module that has no queues allocated for their traffic class.
Configuring Traffic Classes That Define Service Levels on page 14 Configuring Traffic-Class Groups That Define Service Levels on page 15
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)#
14
Chapter 2: Defining Service Levels with Traffic Classes and Traffic-Class Groups
2. (Optional) Specify strict-priority scheduling across the fabric for queues in the traffic
class.
host1(config-traffic-class)#fabric-strict-priority
3. (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. It does not control the weight of egress queues associated with the traffic class. If multiple traffic classes are strict priority, the fabric weight determines which class gets more bandwidth. The weight value is in the range 163. The default is 8. Zero is not a valid weight. Related Documentation
Monitoring Traffic Classes and Traffic-Class Groups for Defined Levels of Service on page 16 fabric-strict-priority fabric-weight traffic-class
Create a traffic-class group by assigning a name that represents the type of service and enter Traffic Class Group Configuration mode.
host1(config)#traffic-class-group assured slot 9 extended host1(config-traffic-class-group)#
The traffic class name can be up to 31 characters. It cannot include spaces. If you do not specify a keyword, the group is strict-priority by default. You can use the auto-strict-priority keyword to explicitly configure a single traffic-class group with strict-priority scheduling, regardless of the scheduler profile associated with the group node. You can use the extended keyword to configure up to three extended traffic-class groups. Scheduling for these groups is determined by the scheduler profile associated with the group node. If an explicitly configured strict-priority group exists, the scheduler for the extended groups may not specify strict-priority scheduling.
15
Use the slot slotNumber option to associate a pre-existing global traffic-class group with the module occupying that slot. Characteristics configured for the local group on the line module override those of the global group.
2. Add traffic classes to the traffic-class group.
host1(config-traffic-class-group)#traffic-class low-latency-traffic-class
Related Documentation
Configuring Traffic Classes That Define Service Levels on page 14 Monitoring Traffic Classes and Traffic-Class Groups for Defined Levels of Service on page 16 traffic-class traffic-class-group
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 300 Monitoring Service Levels with Traffic-Class Groups on page 301
16
CHAPTER 3
Queuing and Buffer Management Overview on page 17 Memory Requirements for Queue and Buffers on page 19 Guidelines for Managing Queue Thresholds on page 19 Guidelines for Managing Buffers on page 20 Configuring Queue Profiles to Manage Buffers and Thresholds on page 22 Monitoring Queues and Buffers on page 24
17
The router dynamically varies queue lengths for all queues as the real-time demand on the egress packet memory changes. You can configure limits to prevent the router from setting queue lengths too low or too high.
Static Oversubscription
The router uses static oversubscription to vary queue thresholds based on the number of queues currently configured, which is relatively static. Static oversubscription is based on the assumption that, when a few queues are configured, many of the queues are likely to be active at the same time. When a large number of queues are configured, fewer queues are likely to be active at the same time. When few queues are configured, buffer memory is strictly partitioned between queues to ensure that buffers are available for all queues. As the number of configured queues increases, buffer memory is increasingly oversubscribed to allow more buffer sharing. Reserving buffer space for all queues when many are expected to be idle is unnecessary and wasteful.
Dynamic Oversubscription
The router uses dynamic oversubscription to vary queue thresholds based on the amount of egress buffer memory in use. The router divides egress buffer memory into eight regions. The size of the region depends on the ASIC type. For more information, see Memory Requirements for Queue and Buffers on page 19. When buffer memory is in low demand, queues are given large amounts of buffer memory. As the demand for buffer memory increases, queues are given progressively smaller amounts of buffer memory.
Color-Based Thresholding
Packets within the router are tagged with a drop precedence:
When the queue fills above the exceeded threshold, the router drops red packets, but still queues yellow and green packets. When the queue fills above the conformed drop threshold, the router queues only green packets.
NOTE: All color-based thresholds vary in proportion to the dynamic queue length.
Related Documentation
Configuring Queue Profiles to Manage Buffers and Thresholds on page 22 Guidelines for Managing Queue Thresholds on page 19 Guidelines for Managing Buffers on page 20
18
Line Module
All EFA line modules GE-2 and GE-HDE OC48 ES2 4G LM
TFA
ES2 10G LM
Related Documentation
Guidelines for Managing Queue Thresholds on page 19 Guidelines for Managing Buffers on page 20 To identify the type of ASIC used by a line module, see the ERX Module Guide and the E120 and E320 Module Guide
19
You might want to limit latency of your multicast traffic by bounding the queue length using a maximum committed threshold. The following example configures the multicast queues so that the committed threshold never exceeds 20 KB, even when the egress memory is lightly loaded. The forfeited buffers are allocated to other queues.
host1(config)#queue-profile multicast host1(config-queue)#committed-length 0 20000 host1(config-queue)#exit
Related Documentation
Memory Requirements for Queue and Buffers on page 19 Configuring Queue Profiles to Manage Buffers and Thresholds on page 22
Queues that back up and consume too many buffers Queues that cannot obtain buffers when they need them (called buffer starvation)
You can set the buffer weight to ensure that some sets of queues get higher thresholds than others. Buffer weight is analogous to weight in a scheduler profile. It directs the router to set the queue thresholds proportionately. This feature provides graceful buffer allocation as the global utilization goes higher; queues with more buffer weight always obtain more buffers, but they do not undergo a dramatic drop in threshold when the system moves from region to region. JunosE Software uses 128-byte buffers. When setting very small queue thresholds, keep the following guidelines in mind:
20
Specifying a maximum queue length of 0 bytes disables queuing of packets on the queue. Specifying a maximum queue length of 1128 bytes creates a single 128-byte buffer for the queue. Specifying a maximum queue length of 129256 bytes creates two 128-byte buffers for the queue. Packets and cells consume at least one buffer. For example, a 64-byte packet consumes a single 128-byte buffer. If you specify a maximum queue length of 256 bytes, then either two packets of 64128 bytes in length or a single packet of 129256 bytes can be queued.
For example, suppose a line module with 4000 IP interfaces is configured with four queues per IP interface, corresponding to four traffic classes. Suppose that queues in two of the traffic classes are configured with a buffer weight of 24 to increase burst tolerance. The following example configures the video queue:
host1(config)#queue-profile video host1(config-queue)#buffer-weight 24 host1(config-queue)#exit host1(config)#
When the egress memory is fully loaded, dynamic oversubscription is 0 percent, and the 8000 queues with the default buffer weight strictly partition 25 percent of the 32-MB memory, leaving 75 percent of the memory for the queues weighted 24 (corresponding to the ratio 75 percent:25 percent, or 24:8). Therefore, these queues have committed thresholds of 1 KB each, and queues with the buffer weight of 24 have committed thresholds of 3 KB each. As the egress memory becomes progressively less loaded, all the queue thresholds increase proportionally, based on dynamic oversubscription, but the queues with buffer weight 24 are always set with thresholds three times larger than the default thresholds.
21
To manage buffer starvation, configure buffer weights on queues so they are in the same ratio as the expected bandwidth for the queues. For example, if two queues have scheduler weight (or assured-rate) in the ratio of 2:1, then set the buffer weights to the same ratio. To manage buffer starvation, set the maximum-committed-threshold on queues that do not need buffering, and increase the buffer-weight for the heavily weighted queues in the round robin. The system calculates the correct ratio for you. Issue the show egress queue rates command to see the ratio:
host1# show egress-queue rates brief interface fastEthernet 9/0.2 traffic forwarded aggregate minimum maximum interface class rate drop rate rate rate ---------------------- ----------------------- --------- --------- ------- ------ip FastEthernet9/0.2 best-effort 0 0 25000 1000000 videoTrafficClass 0 0 375000 1000000 multicastTrafficClass 0 0 925000 1000000 internetTrafficClass 0 0 50000 1000000 Total: 0 0 Queues reported: Queues filtered (under threshold): Queues disabled (no rate period): Queues disabled (no resources): Total queues: 4 0 0 0 4
The minimum rate for each queue is the approximate rate the queue achieves if all configured queues in the line module run infinite traffic. Configure the buffer weights in proportion to the minimum rate displayed by the system. Related Documentation
Memory Requirements for Queue and Buffers on page 19 Configuring Queue Profiles to Manage Buffers and Thresholds on page 22 Monitoring Forwarding and Drop Rates on the Egress Queue on page 318
NOTE: If the sum of the queue minimum lengths is greater than the amount of egress buffer memory, then the egress buffer memory is oversubscribed.
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
22
very small queues, set the maximum queue length to 256 bytes. The system queues no more than 256 bytes. If you do not set the queue lengths, the router varies the queue length dynamically in the range 1 KB7 MB.
1.
host1(config-queue)#buffer-weight 16 Queues with a buffer weight of 16 are twice as long as queues with a buffer weight of 8. The range is 163; the default is 8.
3. (Optional) Set a minimum or maximum queue length for committed packets.
host1(config-queue)#committed-length 11000 15000 The range of minimum and maximum lengths is 01 GB. By default, there is no minimum or maximum length. The color for committed packets is green.
4. (Optional) Set a minimum or maximum queue length for conformed packets.
host1(config-queue)#conformed-length 10000 14000 The range of minimum and maximum lengths is 01 GB. By default, there is no minimum or maximum length. The color for conformed packets is yellow.
5. (Optional) Set a minimum or maximum queue length for exceeded packets.
host1(config-queue)#exceeded-length 9000 10000 The range of minimum and maximum lengths is 01 GB. By default, there is no minimum or maximum length. The color for exceeded packets is red.
6. (Optional) Set the conformed drop threshold as a percentage of the committed
threshold.
host1(config-queue)#conformed-fraction 60
threshold.
host1(config-queue)#exceeded-fraction 40
Queuing and Buffer Management Overview on page 17 Guidelines for Managing Queue Thresholds on page 19
23
Guidelines for Managing Buffers on page 20 Memory Requirements for Queue and Buffers on page 19 buffer-weight committed-length conformed-fraction conformed-length exceeded-fraction exceeded-length queue-profile
Monitoring Queue Thresholds on page 302 Monitoring Queue Profiles on page 305
24
CHAPTER 4
Dropping Behavior Overview on page 25 RED and WRED Overview on page 26 Configuring RED on page 27 Example: Configuring Average Queue Length for RED on page 28 Example: Configuring Dropping Thresholds for RED on page 28 Example: Configuring Color-Blind RED on page 29 Configuring WRED on page 30 Example: Configuring Different Treatment of Colored Packets for WRED on page 32 Example: Defining Different Drop Behavior for Each Traffic Class for WRED on page 32 Example: Configuring WRED and Dynamic Queue Thresholds on page 33 Monitoring RED and WRED on page 35
25
By default, tail dropping occurs when the length of a queue exceeds a threshold. Drop profiles allow you to employ active queue management by specifying RED and WRED parameters to be applied to an egress queue. Congestion of an egress queue occurs when the rate of traffic destined for the queue exceeds the rate of traffic draining from the queue; the queue fills to its limit, and any further traffic destined to it must be discarded until there is room in the queue. RED and WRED monitor average queue length over time to detect incipient congestion. You can combine drop profiles and queue profiles within a queue rule of a QoS profile to specify up to 256 unique queuing behaviors within the router. You can then associate these queuing behaviors in any combination with any of the egress queues. Related Documentation
Small exponent values weight the current queue length heavily, so the average queue length is more responsive to transient bursts. Large exponent values weight the current queue length lightly, so the average queue length is less responsive to bursts.
When the average queue length exceeds the minimum threshold, RED begins randomly dropping packets. While the average queue length increases toward the maximum threshold, 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.
26
WRED is an extension of RED that allows you to assign different RED drop thresholds to each color of traffic. The router assigns a color to each packet. Committed means green, conformed means yellow, and exceeded means red. When the queue fills above the exceeded threshold, the router drops red packets, but still queues yellow and green packets. When the queue fills above the conformed drop threshold, the router queues only green packets. Related Documentation
Configuring RED
Each line module supports a default drop profile and 15 configurable drop profiles. You can configure the default drop profile on all E Series line modules except for the ES2 10G LM. To configure RED:
1.
Specifying an average-length exponent enables the RED average queue length computation. A higher value smooths out the average and slows WRED reaction to congestion and decongestion, accommodating short bursts without dropping. Too large a value can smooth the average to the point that WRED does not react at all. A lower value speeds up WRED reaction. Too low a value can cause overreaction to short bursts, dropping packets unnecessarily.
3. (Optional) Set the minimum and maximum threshold for committed traffic.
host1(config-drop-profile)#committed-threshold percent 30 90 4
4. (Optional) Set the minimum and maximum threshold for conformed traffic.
host1(config-drop-profile)#conformed-threshold percent 25 90 5
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.
27
You can express thresholds as either percentages of maximum queue size by including the keyword percent, or as absolute byte values by omitting the keyword. Related Documentation
Configuring WRED on page 30 Monitoring RED and WRED on page 35 average-length-exponent committed-threshold conformed-threshold drop-profile exceeded-threshold
Related Documentation
Configuring RED on page 27 Dropping Behavior Overview on page 25 RED and WRED Overview on page 26
28
host1(config)#drop-profile colorblind2 host1(config-drop-profile)#committed-threshold percent 30 90 5 host1(config-drop-profile)#conformed-threshold percent 30 90 5 host1(config-drop-profile)#exit host1(config)#drop-profile colorblind3 host1(config-drop-profile)#committed-threshold percent 30 90 5 host1(config-drop-profile)#conformed-threshold percent 30 90 5 host1(config-drop-profile)#exceeded-threshold percent 30 90 5
Related Documentation
Configuring RED on page 27 Dropping Behavior Overview on page 25 RED and WRED Overview on page 26
In the following example, the drop profile and queue profile combine to specify the following:
When the average queue length is between 30 percent full (30 KB) and 90 percent full (90 KB), up to 5 percent of the packets are randomly dropped regardless of their color. When the average queue length is greater than 90 percent, all packets are dropped regardless of color.
host1(config)#drop-profile nocolor host1(config-drop-profile)#c ommitted-threshold percent 30 90 5 host1(config-drop-profile)#exit host1(config)#queue-profile colorless host1(config-queue)#committed-length 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.
29
In the following example, the drop profile and queue profile combine to specify the following:
When the average queue length is between 30 percent full (30 KB) and 90 percent full (90 KB), up to 5 percent of the packets are dropped randomly. In this case, the maximum queue length is 100 KB for green packets, 50 KB for yellow packets, and 25 KB for red packets. Therefore, the router randomly drops:
Red packets when the average queue length is between 7.5 KB and 22.5 KB Yellow packets when the average queue length is between 15 KB and 45 KB Green packets when the average queue length is between 30 KB and 90 KB
When the average queue length is greater than 90 percent of the maximum queue length, all packets are dropped. Therefore, the router drops:
Red packets when the average queue length is greater than 22.5 KB Yellow packets when the average queue length is greater than 45 KB Green packets when the average queue length is greater than 90 KB
host1(config)#drop-profile colorblindRed host1(config-drop-profile)#committed-threshold percent 30 90 5 host1(config-drop-profile)#exit host1(config)#queue-profile colorSensitive host1(config-queue)#committed-length 100000 100000
Related Documentation
Configuring RED on page 27 Dropping Behavior Overview on page 25 RED and WRED Overview on page 26
Configuring WRED
The main difference between RED and WRED is that WRED deals with different colored packets. The router assigns a color to each packet. Committed means green, conformed means yellow, and exceeded means red. Each line module supports a default drop profile and 15 configurable drop profiles. 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.
30
To enable support for 32,000 subscribers with 128,000 QoS queues on ES2 10G ADV LMs, scheduler memory enhancements have reduced the number of QoS rate counters that are supported per egress queue rom 7 to 5:
1 is used for forwarding events 3 are used for tail dropping behavior 1 is used for WRED functionality (an aggregate of all colors)
Each line module supports a default drop profile and 15 configurable drop profiles. On the ES2 10G ADV LM, you must configure WRED in one of the 15 configurable drop profiles; you cannot configure its default drop profile. Queue rate statistics measure the forwarding and drop rates of each queue in bits per second. Queue event statistics configure the E Series router to count the number of times that forwarding or drop rates exceed a specific threshold. To display information about the number of committed packets and bytes dropped by WRED for ES2 10G ADV LMs, see the number displayed in the Dropped by WRED committed field in the output of the show ip interface command. The Dropped by WRED confirmed and Dropped by WRED exceeded fields always display a value of zero because of the single counter being used for WRED functionality being calculated and displayed in the Dropped by WRED committed field of the output. To configure WRED:
1.
Specifying an average-length exponent enables the RED average queue length computation. A higher value smooths out the average and slows WRED reaction to congestion and decongestion, accommodating short bursts without dropping. Too large a value can smooth the average to the point that WRED does not react at all. A lower value speeds up WRED reaction. Too low a value can cause overreaction to short bursts, dropping packets unnecessarily.
3. (Optional) Set the minimum and maximum threshold for committed traffic.
host1(config-drop-profile)#committed-threshold percent 30 90 4
4. (Optional) Set the minimum and maximum threshold for conformed traffic.
host1(config-drop-profile)#conformed-threshold percent 25 90 5
5. (Optional) Set the minimum and maximum threshold for exceeded traffic.
host1(config-drop-profile)#exceeded-threshold percent 20 90 6
31
The thresholds specify a linear relationship between average queue length and drop probability. You can express thresholds as either percentages of maximum queue size by including the keyword percent, or as absolute byte values by omitting the keyword. Related Documentation
Configuring RED on page 27 Monitoring RED and WRED on page 35 average-length-exponent committed-threshold conformed-threshold drop-profile exceeded-threshold
Related Documentation
Configuring WRED on page 30 Dropping Behavior Overview on page 25 RED and WRED Overview on page 26
Example: Defining Different Drop Behavior for Each Traffic Class 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
32
that classifies packets into one of four traffic classes. Each traffic class has a different queueing behavior, drop treatment, and scheduler treatment.
Related Documentation
Configuring WRED on page 30 Dropping Behavior Overview on page 25 RED and WRED Overview on page 26
Fixed-size queues on core routers and core-facing interfaces where the number of queues is relatively small (tens or hundreds, but not thousands).
33
Dynamic queues on edge-facing interfaces where the number of queues is relatively large (thousands).
As shown in Figure 7 on page 35, queue lengths extend to oversubscribe memory when aggregate memory utilization is low, and contract to strictly partition memory when memory utilization is high. Dynamic thresholding enforces fairness when free buffers are scarce and promotes sharing when buffers are plentiful. Dynamic queue thresholds are discussed in Queuing and Buffer Management Overview on page 17. Figure 7 on page 35 illustrates WRED behavior with dynamic queue thresholding. 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
34
Related Documentation
Configuring WRED on page 30 Dropping Behavior Overview on page 25 RED and WRED Overview on page 26
35
36
CHAPTER 5
QoS Statistics Overview on page 37 Configuring Statistic Profiles for QoS on page 39 Configuring Rate Statistics on page 39 Configuring Event Statistics on page 40 Clearing QoS Statistics on the Egress Queue on page 41 Clearing QoS Statistics on the Fabric Queue on page 42 Monitoring QoS Statistics for Rates and Events on page 42
Rate periodTime period, in seconds, over which statistics are gathered. For example, a 30-second rate period results in rate statistics being gathered over 30-second time segments. Forwarding rate thresholdThreshold for forwarding rate events. A forwarding-rate event is counted whenever the forwarding rate exceeds the specified threshold.
37
Committed drop thresholdThreshold above which committed drop rate events are counted. Conformed drop thresholdThreshold above which conformed drop rate events are counted. Exceeded drop thresholdThreshold above which exceeded drop rate events are counted.
Rate Statistics
You can configure the E Series router to gather statistics for the rate at which queues forward and drop packets. Queue rate statistics measure the forwarding and drop rates of each queue in bits per second. All bytes in the Layer 2 encapsulation are included in the rate calculation. For example, rates for a queue on Ethernet include the Ethernet and VLAN encapsulations. For ATM modules, you can optionally configure queue statistics and queue rates to include the cell encapsulation and padding. Cell encapsulation and padding are referred to as the cell tax. The QoS shaping mode that you set on ATM line modules determines whether queue rate statistics include cell tax.
If the interface is configured with frame-based QoS shaping mode, the egress queue measures frame rate statistics; an ATM cell tax is not included. If the interface is configured with cell-based QoS shaping mode, the egress queue measures cell rate statistics; cell rates include ATM Adaptation Layer 5 (AAL5) encapsulation and cell padding. If the interface is configured with byte adjustment, the egress queue measures rate statistics that are adjusted to the byte adjustment value.
NOTE: If you change the QoS shaping mode value in the middle of a rate period, the gathered rates are a mixture of cell- and frame-based rates for that one rate period. The next rate period uses a rate based on the new QoS shaping mode setting.
Event Statistics
You can configure the E Series router to count the number of times that forwarding or drop rates exceed a specific threshold. Events can be useful when you are monitoring service level agreements. For example, you might count the number of times that the drop rate of a queue is nonzero.
38
The bulk statistics application provides components to configure and organize network accounting data in a flexible manner. The application reduces the consumption of network bandwidth by collecting queue-level statistics and periodically transferring the data to a remote server. You can configure the bulk statistics schemas to export network accounting data. In particular, the QoS schema supports the export of queue-level QoS statistics on egress queues for various interface types. Configuring QoS schemas helps service providers monitor their network and report congestion and oversubscription by obtaining queue-level statistics and configuration information for each logical interface. For information about schemas and configuring a bulk statistics schema to export queue-level QoS statistics for egress queues on the router, see JunosE System Basics Configuration Guide, Chapter 4, Configuring SNMP.
Configuring Rate Statistics on page 39 Configuring Event Statistics on page 40 Monitoring QoS Statistics for Rates and Events on page 42 statistics-profile
host1(config)#qos-profile qospro-3 host1(config-qos-profile)#ip queue traffic-class tc1 scheduler-profile sp1 statistics-profile statpro-5
4. Attach the QoS profile to the appropriate interface.
39
Related Documentation
Configuring Statistic Profiles for QoS on page 39 Configuring a QoS Profile on page 126 Monitoring QoS Statistics for Rates and Events on page 42 interface qos-profile queue rate-period statistics-profile
host1(config-statistics-profile)#forwarding-rate-threshold 10000000 Forwarding rate threshold range is 01073741824 bps; default is no threshold.
4. (Optional) Set a threshold for committed (green) packets.
host1(config-statistics-profile)#committed-drop-threshold 2000000 Drop rate threshold range is 01073741824 bps; default is no threshold.
40
host1(config-statistics-profile)#conformed-drop-threshold 4000000 Drop rate threshold range is 01073741824 bps; default is no threshold.
6. (Optional) Set a threshold for exceeded (red) packets.
host1(config-statistics-profile)#exceeded-drop-threshold 6000000 Drop rate threshold range is 01073741824 bps; default is no threshold.
7. Reference the statistics profile in a QoS profile.
host1(config)#qos-profile qospro-1 host1(config-qos-profile)#ip queue traffic-class tc1 scheduler-profile sp1 statistics-profile statpro-1
8. Attach the QoS profile to the appropriate interface.
Related Documentation
Configuring Statistic Profiles for QoS on page 39 Configuring a QoS Profile on page 126 Monitoring QoS Statistics for Rates and Events on page 42 committed-drop-threshold conformed-drop-threshold exceeded-drop-threshold forwarding-rate-threshold qos-profile queue rate-period statistics-profile
Use the explicit keyword to clear queues only on the specified interface and not queues stacked above the interface.
41
Related Documentation
Monitoring QoS Statistics for Rates and Events on page 42 clear egress-queue
By default, statistics for all traffic classes and all slots are cleared. Related Documentation
Monitoring QoS Statistics for Rates and Events on page 42 clear fabric-queue
Monitoring Forwarding and Drop Events on the Egress Queue on page 317 Monitoring Forwarding and Drop Rates on the Egress Queue on page 318 Monitoring Queue Statistics for the Fabric on page 322 Monitoring the Configuration of Statistics Profiles on page 323
42
PART 3
QoS Scheduler Hierarchy Overview on page 45 Configuring Rates and Weights in the Scheduler Hierarchy on page 51 Configuring Strict-Priority Scheduling on page 57 Shared Shaping Overview on page 67 Configuring Simple Shared Shaping of Traffic on page 75 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
43
44
CHAPTER 6
Scheduler Hierarchy Overview on page 45 Configuring a Scheduler Hierarchy on page 47 Configuring a Scheduler Profile for a Scheduler Node or Queue on page 48 Using Expressions for Bandwidth and Burst Values in a Scheduler Profile on page 48
The scheduler selects a first-level node based on the allocated bandwidth. 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.
45
When the scheduler is not congested, the shaping rates determine which node or queue can claim the bandwidth. The shaping rate specifies the maximum bandwidth to the node or queue. When the scheduler is congested, either the hierarchical or static assured rate or the weight specifies the minimum bandwidth.
If the scheduler is configured to use a static assured rate and the assured rate is other than none (the default), it is used to determine the allocated bandwidth, and the weight setting is ignored. If the assured rate is zero, the weight setting is used to determine the bandwidth. The static assured rate specifies the desired bandwidth. This rate is guaranteed until the bandwidth becomes oversubscribed.
If the scheduler is configured to use hierarchical assured rate, the scheduler dynamically adjusts the amount of allocated bandwidth for service delivery based on the sum of the assured rates of all child nodes and queues. The assured rate also specifies that if bandwidth is over- or undersubscribed, all adjustments are made in proportion to the original assured-rate specification. For example, if Node A is configured to receive 40 Mbps and Node B receives 20 Mbps, any available bandwidth above the subscribed total of 60 Mbps would be allocated to the two nodes at the same 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.
46
NOTE: For E Series ASIC modules, strict priority is supported only for a single first-level scheduler node.
When determining the shaping rate, the system includes all bytes in Layer 2 encapsulations. The packets that are included in the rate depend on the Layer 2 node that is specified in the QoS profile. For example, the shaping rate for an Ethernet node includes bytes from the Ethernet and VLAN encapsulations. Related Documentation
Static and Hierarchical Assured Rate Overview on page 53 Rate Shaping and Port Shaping Overview on page 51 Shared Shaping Overview on page 67 Configuring a Scheduler Hierarchy on page 47
Configure a scheduler profile. See Configuring a Scheduler Profile for a Scheduler Node or Queue on page 48.
Configure a shaping rate for rate shaping or port shaping. See Configuring Rate Shaping for a Scheduler Node or Queue on page 52 or Configuring Port Shaping on page 52.
Configure an assured rate. See Configuring an Assured Rate for a Scheduler Node or Queue on page 54.
Configure the HRR weight. See Configuring the HRR Weight for a Scheduler Node or Queue on page 56.
Configure shared shaping. See Configuring Simple Shared Shaping on page 77 and Configuring Compound Shared Shaping on page 96.
Configure implicit and explicit constituent selection. 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.
47
See Configuring a QoS Profile on page 126 and Attaching a QoS Profile to an Interface on page 128. Related Documentation
Scheduler Hierarchy Overview on page 45 For information about configuring a scheduling hierarchy with QoS parameters, see Parameter Definition Attributes for QoS Administrators Overview on page 219
Create a scheduler profile by assigning a name that represents the type of service and enter Scheduler Profile Configuration mode.
host1(config)#scheduler-profile sp-1mbs host1(config-scheduler-profile)#
Configuring Rate Shaping for a Scheduler Node or Queue on page 52 Configuring Port Shaping on page 52 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
48
When calculating constant shaping rates, use the following formula to translate burst values from bytes to milliseconds (ms):
The shaping rate is calculated when the QoS profile is attached based on the parameter instance. For example:
host1(config)# scheduler-profile sp-1mbs (config-scheduler-profile)# shaping-rate video-bandwidth % 100 burst 500 milliseconds
When the shaping rate for video-bandwidth is 2 Mbps, the burst value is calculated using the following formula:
Related Documentation
For more information about using expressions within scheduler profiles that are used for QoS parameters, see Scheduler Profiles and Parameter Expressions for QoS Administrators on page 225 Configuring Rate Shaping for a Scheduler Node or Queue on page 52 Configuring Port Shaping on page 52
49
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
50
CHAPTER 7
Rate Shaping and Port Shaping Overview on page 51 Configuring Rate Shaping for a Scheduler Node or Queue on page 52 Configuring Port Shaping on page 52 Static and Hierarchical Assured Rate Overview on page 53 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
51
The per-port shaping feature provides the ability to shape the output of a port. Related Documentation
Configuring Rate Shaping for a Scheduler Node or Queue on page 52 Configuring Port Shaping on page 52
The range for the shared-shaping rate is 10001000000000 bps (1 Kbps1000 Kbps); the default is the minimum shaping rate (1 Kbps). The router rounds the rate to the next higher 8 Kbps. Use the operator and operandValue variables to configure a shaping rate with an expression. You can use the bps or kbps keywords to specify the unit of the shaping rate. By default, the shaping rate is configured in bps. Use the burst keyword to specify the catch-up number associated with the shaper; the range is 0522240. Specifying 0 enables the router to select an applicable default value. Use the milliseconds or bytes keywords to specify the unit of the burst size. Related Documentation
Rate Shaping and Port Shaping Overview on page 51 Configuring a Scheduler Profile for a Scheduler Node or Queue on page 48 scheduler-profile shaping-rate
52
2. Configure a QoS profile, specify the node command, and reference the
scheduler-profile.
host1(config)#qos-profile 80mbps host1(config-qos-profile)#ethernet node scheduler-profile 80mbps host1(config-qos-profile)#exit
3. Attach the QoS profile to the port.
The sample configuration shapes Fast Ethernet port 2/0 to a rate no higher than 80 Mbps. Using the following configuration, you can shape the corresponding HDLC channel down to 20 Mbps:
host1(config)#scheduler-profile 20mbps host1(config-scheduler-profile)#shaping-rate 20000000 host1(config-scheduler-profile)#exit host1(config)#qos-profile 20mbps host1(config-qos-profile)#serial node scheduler-profile 20mbps host1(config-qos-profile)#exit host1(config)#interface serial 2/0:1/1 host1(config-if)#qos-profile 20mbps
Related Documentation
Rate Shaping and Port Shaping Overview on page 51 Configuring a Scheduler Profile for a Scheduler Node or Queue on page 48 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
53
bandwidth-on-demand. Eventually, this complicated manual recalculation process becomes unreasonable and virtually impossible. HAR replaces the manual recalculation process by directing the router to dynamically calculate the assured rate for a scheduler node based on the sum of the assured rates of all its child nodes and queues. For example, you might use HAR to increase the effective weight of an ATM-VC scheduler node when a video queue is created, and to later restore the effective rate of the node when the video queue is deleted. HAR is applicable only to level 1 and level 2 scheduler nodes, and is not applicable to queues or ports. When you configure HAR, the changes take place immediately. When you disable HAR, the scheduler nodes previous weight is restored. Figure 10 on page 54 shows an application of HAR for VC nodes. In the example, VCs, which are configured for HAR, are stacked over virtual path (VP) nodes. The VP nodes are in turn stacked over an OC-3 ATM port. Each VC has a best-effort data queue, which currently has an assured rate of 20 Kbps. The VCs share equal portions of their parent VP's bandwidth. However, when the video queue is added to VC2, HAR enables VC2's share of the VP bandwidth to increase in proportion to the 1-Mbps video queue that was created. The bandwidth of sibling VC nodes, which have only a data queue, is decreased in equal proportions.
Related Documentation
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
54
By default, the HRR weight is configured for the scheduler profile. If the assured rate setting is other than none (the default), then the assured rate is used instead of the HRR weight setting for the scheduler node or queue. Tasks to configure an assured rate are:
Configuring a Static Assured Rate on page 55 Configuring a Hierarchical Assured Rate on page 55 Changing the Assured Rate to an HRR Weight on page 55
2. Specify a numeric rate with the assured-rate command in the scheduler profile.
For a static assured rate, specify the bits per second value in the range 250001000000000 bps (25 Kbps to 1 Gbps); the default is none (no assured rate). Use the operator and operandValue variables to configure an assured rate with an expression.
2. Specify the hierarchical keyword with the assured-rate command in the scheduler
profile.
host1(config-scheduler-profile)#assured-rate hierarchical
host1(config-scheduler-profile)#no assured-rate
The assured rate in the scheduler profile reverts to using the HRR weight specification.
55
Related Documentation
Static and Hierarchical Assured Rate Overview on page 53 Configuring a Scheduler Profile for a Scheduler Node or Queue on page 48 Configuring the HRR Weight for a Scheduler Node or Queue on page 56 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 assured-rate scheduler-profile
The weight value is in the range 04080. The default weight is 8. Weight 0 (zero) is a special weight that is used for relative strict-priority scheduling. Use the operator and operandValue variables to configure a weight with an expression. Related Documentation
Static and Hierarchical Assured Rate Overview on page 53 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
56
CHAPTER 8
Strict-Priority and Relative Strict-Priority Scheduling Overview on page 57 Comparison of True Strict Priority with Relative Strict Priority Scheduling on page 59 Configuring Strict-Priority Scheduling on page 63 Configuring Relative Strict-Priority Scheduling for Aggregate Shaping Rates on page 65
57
One strict priority traffic-class group is called the auto-strict-priority group. The scheduler nodes and queues in the auto-strict-priority group receive strict-priority scheduling. If multiple queues above the strict-priority node have packets, the HRR algorithm selects which strict-priority queue is scheduled next.
NOTE: If you configured traffic shaping through traffic shape profiles in JunosE releases before Release 4.0, traffic shaping is replaced with the rate-shaping feature, which is configured when you configure a scheduler profile.
58
port will not become congested, and the latency caused by the round-robin behavior of both the HRR and cell schedulers is nominal. In these undersubscribed conditions, the latency of a strict-priority queue within each VC is calculated as if the VC were draining onto a wire with bandwidth equal to the shaped rate. Relative strict priority is carried out in the HRR scheduler on E Series ASIC line modules. Related Documentation
Comparison of True Strict Priority with Relative Strict Priority Scheduling on page 59 Configuring Strict-Priority Scheduling on page 63 Configuring Relative Strict-Priority Scheduling for Aggregate Shaping Rates on page 65
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
59
nonstrict packet is the propagation delay of a single large packet at the port rate. For a 1500 byte frame at OC3 rate, that latency is less than 100 microseconds. Because the strict and nonstrict packets for a VC are scheduled in separate round robins, the scheduler cannot enforce an aggregate rate for both of them.
This configuration provides a latency bound for the relative strict-priority queues. The worst-case latency caused by a nonstrict packet is the propagation delay of a single large packet at the VC rate. For a 1500 byte frame at a 2 Mbps rate, that delay is about 6 milliseconds. This configuration provides for shaping the aggregate of nonstrict and relative strict packets to a single rate, and it is consistent with the traditional ATM model. It does not scale as well as true strict priority, because the nonstrict and relative strict traffic together must not oversubscribe the port rate.
60
scheduler to a rate that is less than the aggregate VC rate. This shaping prevents the VC queue in the SAR scheduler from being congested with strict-priority traffic. The major difference between relative and true strict priority on ATM line modules is that relative strict priority shapes the aggregate for the VC to a precell tax rate, whereas true strict priority shapes the aggregate for the VC to a postcell tax rate. For example, shaping the VC to 1 Mbps in the HRR scheduler allows 1 Mbps of frame data, but cell tax adds anywhere from 100 Kbps to 1 Mbps additional bandwidth, depending on packet size. Shaping the VC to 1 Mbps in the SAR scheduler allows just 1 Mbps of cell bytes regardless of packet size.
NOTE: Controlling latency is not normally required. If you undersubscribe the port rate in the HRR scheduler, you can obtain latency bounds without modifying the SAR mode of operation.
61
sections describe additional configuration steps that will ensure that no more than a single nonstrict packet can precede a strict-priority packet on the VC.
Zero-Weight Queues
To reduce latency and jitter, you can configure the relative strict-priority queue with a weight of 0 (zero), which gives the queue a weight of 4080. When a packet arrives at a zero-weighted queue, the queue remains in the active WRR until it is exhausted, whereas competing queues must leave the active WRR because their weight credits are exhausted. To completely drain the queue, configure the maximum burst size. The zero-weighted queue is eventually alone in the active round robin and is effectively drained at strict priority. To configure more than one relative strict queue or node, simply configure a maximum weight, and the two relative strict queues or nodes will share bandwidth fairly. You can shape the nonstrict queue, as described in the next section, to keep latency bounded. Also, configure only a few nonstrict nodes or queues to prevent additional latency and jitter of the relative strict-priority traffic when the nodes or queues are in the round robin and a packet arrives in the zero-weighted queue. The number of nonstrict frames that precede a relative strict frame equals the number of nonzero weighted queues among the sibling scheduler nodes. Nonstrict queues must still exhaust their weight credits before they leave the active round robin. The result is that occasionally more than one nonstrict frame may precede a relative strict frame, causing more jitter than may be acceptable. You can eliminate this source of latency by shaping the nonstrict queue to the aggregate rate with a burst size of 1.
62
This shaping limits relative strict traffic to 500 Kbps, and prevents the relative strict-priority traffic from starving out the nonstrict traffic. The third shaper, on the nonstrict queue, is subtle. The rate is 1 Mbps, which allows the nonstrict traffic to consume up to the full aggregate rate of the VC. But the burst size is 1, which causes the nonstrict queue to always yield to the relative strict-priority queue after sending a packet. This burst size limits the number of nonstrict packets that can precede a relative strict-priority packet to the minimum, one packet.
Related Documentation
Strict-Priority and Relative Strict-Priority Scheduling Overview on page 57 Configuring Strict-Priority Scheduling on page 63 Relative Strict-Priority Scheduling Overview on page 58
2. Configure the auto-strict-priority traffic-class group, and add the traffic classes that
63
host1(config)#qos-profile Example-qos-profile host1(config-qos-profile)#atm group default host1(config-qos-profile)#atm group Strict-priority scheduler-profile strictPriorityBandwidth host1(config-qos-profile)#atm-vc node group default host1(config-qos-profile)#atm-vc node group Strict-priority host1(config-qos-profile)#atm-vc queue traffic-class best-effort host1(config-qos-profile)#atm-vc queue traffic-class Low-loss-1 host1(config-qos-profile)#atm-vc queue traffic-class Low-latency-1 host1(config-qos-profile)#atm-vc queue traffic-class Low-latency-2 host1(config-qos-profile)#exit
5. Attach the QoS profile to an interface.
Related Documentation
Strict-Priority and Relative Strict-Priority Scheduling Overview on page 57 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
64
host1(config)# scheduler-profile be host1(config-scheduler-profile)# shaping-rate 1000000 burst 1 host1(config-scheduler-profile)# weight 8 host1(config-scheduler-profile)# exit
TIP: If you need to impose a shaping rate on the nonstrict queues to meet a functional requirement, you can specify a rate less than the aggregate rate. The key is that the burst size must be one, or small. The burst size determines the maximum-sized packet that can squeeze in front of a relative strict-priority packet in the round robin.
65
Related Documentation
Strict-Priority and Relative Strict-Priority Scheduling Overview on page 57 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
66
CHAPTER 9
Shared Shaping Overview on page 67 Shared Shaper Terms on page 68 How Shared Shaping Works on page 69 Guidelines for Configuring Simple and Compound Shared Shaping on page 70
67
Shared shaping is typically enabled on the access-facing line module, but you can enable the feature for any interface type recognized by QoS, on any line module and any E Series Broadband Services Routers. Related Documentation
Simple Shared Shaping Overview on page 75 Compound Shared Shaping Overview on page 95
Active constituent
Inactive constituent
Shared Shaping
Related Documentation
For definitions of other common QoS terms, see QoS Terms on page 5
68
Simple shared shaping is useful for triple-play configurations, because it manages voice and video queues in addition to data queues so that the shared rate cannot be exceeded. You can use line modules that have any ASIC hardware. Compound shared shaping is useful for triple-play configurations, because it manages voice and video queues in addition to data queues so that the shared rate cannot be exceeded. 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.
Compound
69
Simple Shared Shaping Overview on page 75 Compound Shared Shaping Overview on page 95 Constituent Selection for Shared Shaping Overview on page 103
If you configure a shaping rate higher than the shared-shaping rate, the rate never exceeds the shared rate, so the router issues the following error message:
% shaping-rate cannot be greater than the shared-shaping-rate
Although you can configure a shared-shaping rate and a shaping rate in the same scheduler profile, the shaping rate must not exceed the shared-shaping rate. A scheduler profile that includes a shaping rate must not contain a shared-shaping rate that specifies a constituent as weighted.
70
A scheduler profile that is referenced by nodes or queues that are not best effort cannot be modified to include a shared-shaping rate command. A scheduler profile that includes a shared-shaping rate command cannot be associated with a group node.
71
For more information about configuring low-CDV mode, see ATM Integrated Scheduler Overview on page 153.
Figure 17: Implicit Constituent Selection for Compound Shared Shaper: Mixed Interface Types
72
For example, the following scheduler profiles limit the subscriber's strict priority traffic to 1.0 Mbps and limits the subscriber's aggregate traffic to 1.5 Mbps. If scheduler profile strictOne specified a shaping rate greater than or equal to 1.5 Mbps, nonstrict traffic might face starvation.
host1(config)#scheduler-profile strictOne host1(config-scheduler-profile)#shaping-rate 1000000 host1(config-scheduler-profile)#exit host1(config)#scheduler-profile nonStrictOne host1(config-scheduler-profile)#shared-shaping-rate 1500000
Related Documentation
For a list of shared shaper terms, see Shared Shaper Terms on page 68 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
73
74
CHAPTER 10
Simple Shared Shaping Overview on page 75 Configuring Simple Shared Shaping on page 77 Example: Simple Shared Shaping for ATM VCs on page 79 Example: Simple Shared Shaping for ATM VPs on page 81 Example: Simple Shared Shaping for Ethernet on page 82
75
If you are configuring VP shared shaping, configure shared shaping on the best-effort scheduler node for the VP. Shaping the best-effort scheduler node for the VP has the effect of shaping all the VC best-effort queues for that VP. This enables you to retain the advantages of per-VC queuing in the hierarchical scheduler. If you are configuring VC shared shaping and the SAR is operating in low-CDV mode, we recommend you configure the shared-shaping rate on the best-effort scheduler node for the VP or VC. The router sets the SAR shaper for the VC or VP to match the shared-shaping rate on VC and VP nodes in the hierarchical scheduler; this is usually the desired behavior. A shared shaper configured on the best-effort queue does not trigger the matching shaper in the SAR.
76
In a typical triple-play network configuration over Ethernet, individual subscribers are represented on the B-RAS by VLANs and DSLAMs by SVLANs. Figure 19 on page 77 illustrates how to shape the subscriber aggregate of voice, video, and data to a single rate in Ethernet.
Related Documentation
For a list of shared shaper terms, see Shared Shaping Overview on page 67 Configuring Simple Shared Shaping on page 77 Constituent Selection for Shared Shaping Overview on page 103
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.
77
host1(config)#scheduler-profile shared-1mbps
2. Configure the shared-shaping rate.
The range for the shared-shaping rate is 1000100000000 bps (1 Kbps1000 Kbps); the default is the minimum shaping rate (1 Kbps). Use the operator and operandValue variables to specify the shared shaping rate as an expression. Use the bps or kbps keywords to specify the unit of the shaping rate. By default, the shaping rate is configured in bps. Use the burst keyword to configure the catch-up number associated with the shaper; the range is 0522240 (0510 KB). If you do not specify a burst value, the router selects an applicable default value. Use the milliseconds or bytes keywords to specify the unit of the burst size. You can specify simple to shape data queue rates to the value of the shared rate minus the combined voice and video traffic rate. By default, shared shaping is set to auto. In this mode, the router selects the type of shared shaping that is applied according to the type of line module. Compound shared shaping is hardware-dependent. If you specify compound for line modules that do not support it, an error message is generated and the router applies simple shared shaping.
3. Configure the QoS profile and reference the scheduler profile.
(config)#qos-profile subscriber-default-mode (config-qos-profile)#atm-vc node (config-qos-profile)#atm-vc node group AF (config-qos-profile)#atm-vc node group EF (config-qos-profile)#atm-vc queue traffic-class best-effort scheduler-profile shared-1mbps (config-qos-profile)#exit
TIP: The scheduler profile that you configured with the shared-shaping rate must be referenced in the best-effort queue or the best-effort scheduler node.
Related Documentation
Simple Shared Shaping Overview on page 75 Guidelines for Configuring Simple and Compound Shared Shaping on page 70
78
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 Example: Simple Shared Shaping for ATM VCs on page 79 Example: Simple Shared Shaping for ATM VPs on page 81 Example: Simple Shared Shaping for Ethernet on page 82 node qos-profile queue scheduler-profile shared-shaping-rate traffic-class traffic-class-group
(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
79
(config)#scheduler-profile shared-1mbps (config-scheduler-profile)#shared-shaping-rate 1000000 simple (config-scheduler-profile)#exit (config)#qos-profile subscriber-default-mode (config-qos-profile)#atm-vc node (config-qos-profile)#atm-vc node group AF (config-qos-profile)#atm-vc node group EF (config-qos-profile)#atm-vc queue traffic-class best-effort scheduler-profile shared-1mbps (config-qos-profile)#atm-vc queue traffic-class video scheduler-profile 300kbps (config-qos-profile)#atm-vc queue traffic-class voice scheduler-profile 200kbps (config-qos-profile)#exit
3. Delete the rule in the default port type profile that creates IP best-effort queues by
default.
(config)#qos-profile atm-default (config-qos-profile)#no ip queue traffic-class best-effort (config-qos-profile)#exit
4. Attach the profile to the ATM subinterface for VC 3.
The qos-profile subscriber-default-mode command shown in this example is appropriate if you have configured the SAR to be in default mode (by issuing the no qos-mode-port command). If this QoS profile is attached in low-CDV mode, the shaper is effective but the CDV is not correctly bounded, because the VC is not reshaped in the SAR. The following commands configure a QoS profile different from the one shown in the previous example. In this example, the best-effort scheduler node for VC 3 is shaped to a shared rate of 1 Mbps. The qos-profile subscriber-low-cdv-mode command is appropriate if you configure the SAR in low-CDV mode (by issuing the qos-mode-port low-cdv command). The VC is reshaped to 1 Mbps in the SAR. If this QoS profile is attached in the SAR default mode, the 1-Mbps shaper is disabled by VC backpressure from the SAR.
(config)#qos-profile subscriber-low-cdv-mode (config-qos-profile)#atm-vc node scheduler-profile shared-1mbps (config-qos-profile)#atm-vc node group AF (config-qos-profile)#atm-vc node group EF (config-qos-profile)#atm-vc queue traffic-class best-effort (config-qos-profile)#atm-vc queue traffic-class video scheduler-profile 300kbps (config-qos-profile)#atm-vc queue traffic-class voice scheduler-profile 200kbps (config-qos-profile)#exit
Related Documentation
Configuring Simple Shared Shaping on page 77 Simple Shared Shaping Overview on page 75
80
The following set of commands configures the shared shaper in Figure 20 on page 81.
(config)#scheduler-profile 2mbps (config-scheduler-profile)#shaping-rate 2000000 (config-scheduler-profile)#exit (config)#scheduler-profile 400kbps (config-scheduler-profile)#shaping-rate 400000 (config-scheduler-profile)#exit (config)#scheduler-profile shared-5mbps (config-scheduler-profile)#shared-shaping-rate 5000000 simple (config-scheduler-profile)#exit (config)#qos-profile vp-subscriber1 (config-qos-profile)#atm-vp node scheduler-profile shared-5mbps (config-qos-profile)#atm-vp node group AF (config-qos-profile)#atm-vp node group EF (config-qos-profile)#atm-vc node (config-qos-profile)#atm-vc queue traffic-class best-effort scheduler-profile default
81
(config-qos-profile)#atm-vp queue traffic-class video scheduler-profile 2mbps (config-qos-profile)#atm-vp queue traffic-class voice scheduler-profile 400kbps (config-qos-profile)#exit
In this example, the best-effort scheduler node for the VP is shaped to a shared rate of 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 rate of 400 Kbps. The AF queue claims up to the next 2 Mbps. The VC-level best-effort queues obtain whatever bandwidth remains of the 5 Mbps after the AF traffic and EF traffic have made their claims. This QoS profile is appropriate for low-CDV mode. If the provider configures a shapeless VP tunnel in the SAR, QoS sets the SAR shaper for the VP to match the 5-Mbps shared-shaping rate, and the CDV is bounded for the VP tunnel. Related Documentation
Configuring Simple Shared Shaping on page 77 Simple Shared Shaping Overview on page 75
In Figure 21 on page 82, the S-VLANs labeled 1, 2, and 3 indicate the possible constituents for 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.
82
1.
(config)#qos-parameter-define vlan-g1-max-rate (qos-parameter-define)#controlled-interface-type vlan (qos-parameter-define)#instance-interface-type vlan (qos-parameter-define)#exit (config)#qos-parameter-define svlan-g1-max-rate (qos-parameter-define)#controlled-interface-type svlan (qos-parameter-define)#instance-interface-type svlan (qos-parameter-define)#instance-interface-type ethernet (qos-parameter-define)#exit (config)#qos-parameter-define vlan-max-rate (qos-parameter-define)#controlled-interface-type vlan (qos-parameter-define)#instance-interface-type vlan (qos-parameter-define)#instance-interface-type svlan (qos-parameter-define)#exit (config)#qos-parameter-define svlan-max-rate (qos-parameter-define)#controlled-interface-type svlan (qos-parameter-define)#instance-interface-type svlan (qos-parameter-define)#instance-interface-type ethernet (qos-parameter-define)#exit
3. Configure the shared shaper by referencing parameter definitions in the shaping-rate
command.
(config)#scheduler-profile vlan-be (config-scheduler-profile)#shared-shaping-rate vlan-max-rate simple (config-scheduler-profile)#exit (config)#scheduler-profile svlan-be (config-scheduler-profile)# shared-shaping-rate svlan-max-rate simple (config-scheduler-profile)#exit (config)#scheduler-profile svlan-g1 (config-scheduler-profile)#shaping-rate svlan-g1-max-rate (config-scheduler-profile)#exit (config)#scheduler-profile vlan-g1 (config-scheduler-profile)#shaping-rate vlan-g1-max-rate (config-scheduler-profile)#exit (config)#scheduler-profile svlan-g2 (config-scheduler-profile)#shaping-rate svlan-max-rate % 50
83
(config-scheduler-profile)#exit
4. Configure the QoS profile.
(config)#qos-profile svlan-4.1 (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
5. Attach the QoS profile to the S-VLANs on Fast Ethernet interface 11/0.
(config)#interface fastEthernet 11/0 (config-if)#svlan 0 qos-parameter svlan-max-rate 4000000 (config-if)#svlan 0 qos-profile svlan-4.1 (config-if)#encapsulation vlan (config-if)#exit (config)#interface fastEthernet 11/0.1 (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 Documentation
Configuring Simple Shared Shaping on page 77 Simple Shared Shaping Overview on page 75
84
CHAPTER 11
Simple Shared Shaping Algorithm Overview on page 85 Variables of the Simple Shared Shaper Algorithm on page 87 Guidelines for Controlling the Simple Shared Shaper Algorithm on page 88 Configuring Simple Shared Shaper Algorithm Variables on page 89 Sample Process for Controlling the Simple Shared Shaper Algorithm on page 90
85
When the video stream starts in the example displayed by Figure 22 on page 85, the shared shaper reacts by drastically reducing best-effort traffic because it must avoid saturating downstream queues. In some cases, best-effort traffic is throttled for a few seconds. When the video stream stops, best-effort traffic can continually consume more bandwidth, up to the shared-shaping rate. By controlling the minimum dynamic rate in the simple shared shaper algorithm, you can configure the less conservative simple shared shaping behavior displayed in Figure 23 on page 86. In this example, as the video traffic starts, the best-effort rate is reduced less drastically, and best-effort traffic is not starved.
You can also configure the more liberal simple shared shaper behavior that is displayed in Figure 24 on page 86. In this example, the initial over-limit video traffic is ignored. When the video traffic stops, the system immediately allows best-effort traffic to consume the available bandwidth.
2. Calculates the virtual output queue length (VOQL). 3. Calculates the new dynamic rate. 4. Uses the larger value of the new dynamic rate (from Step 3) and a minimum dynamic
rate.
86
Related Documentation
Variables of the Simple Shared Shaper Algorithm on page 87 Configuring Simple Shared Shaper Algorithm Variables on page 89
newMeasuredRateSum of bytes enqueued to non-best-effort constituent queues, in bps. oldDynamicRateDynamic shaping rate from the previous rate period, in bits-per-second. sharedShapingRateConfigured shared shaper rate, in bps. The shared shaping rate is the total rate of all constituents of the shared shaper.
You can configure the following variables, which correspond to the commands described in Configuring Simple Shared Shaper Algorithm Variables on page 89.
convergenceFactorControls the convergence of the dynamic shaping rate to the calculated shaping rate, expressed as a percentage of the available bandwidth. The default value of 50 percent causes the dynamic shaping rate to converge by half of the available rate each period. For example, when the dynamic rate of a 5 Mbps simple shared shaper is 1 Mbps, and the measured rate goes from 4 Mbps to 0 Mbps, 4 Mbps of bandwidth becomes available. The simple shared shaper converges from 1 Mbps to 5 Mbps by half of the available bandwidth per period. In this example, the dynamic shaping rates for several periods are 1 Mbps, 3 Mbps, 4 Mbps, 4.5 Mbps, 4.75 Mbps, and so on.
maximumVOQLSets the maximum virtual output queue length (VOQL), expressed in milliseconds (ms) of the shared shaping rate. The default value of 4000 indicates that a 5 Mbps shared shaper does not allow the VOQL to exceed 20 Mbps. Smaller values reduce the effect of the VOQL in the simple shared shaper algorithm. A maximum VOQL of 0 indicates that the shared shaper ignores the VOQL. This setting is appropriate for configurations where exceeding the shared shaping rate for brief periods of time does not cause downstream queuing.
minimumDynamicRateSets the minimum value for the dynamic shaping rate, expressed as a percentage of the shared shaping rate. For example, a value of 25 for a 20 Mbps shared shaper specifies that the dynamic shaping rates never be set to a value less than 5 Mbps. The default value is 0. reactionFactorControls 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.
87
This section describes the algorithm tasks in detail. Step 1: Calculate the New Measured Rate The simple shared shaper uses the following formula to calculate the new measured rate:
The simple shared shaper maintains a VOQL, which cannot become less than zero, using the following formulas:
Each rate period, the simple shared shaper calculates the new dynamic rate (the shaping rate of the best-effort node or queue) using the following formula. The system prevents the new dynamic rate from becoming less than zero.
Step 4: Determine the Larger Value of the New Dynamic Rate and the Minimum Dynamic Rate
The simple shared shaper determines the larger of the new dynamic rate and a minimum dynamic rate, where the minimumDynamicRate is a fraction of the shared-shaping rate, using the following formula:
Related Documentation
Simple Shared Shaping Algorithm Overview on page 85 Sample Process for Controlling the Simple Shared Shaper Algorithm on page 90
88
Table 8 on page 89 displays guidelines for configuring the most liberal shared shaper to the most conservative shared shaper.
Most liberalAppropriate when over-queuing is not a concern LiberalAppropriate when over-queuing is not a concern and a smoother rate adjustments are desirable ModerateDefault settings ConservativeAppropriate when over-queuing is a major concern Most conservativeRarely appropriate.
Most Liberal
0 0 0
Liberal
25 25 50
Moderate
50 400 200
Conservative
75 600 300
Most Conservative
99 1000 1000
Related Documentation
Simple Shared Shaping Algorithm Overview on page 85 Configuring Simple Shared Shaper Algorithm Variables on page 89
2. (Optional) Configure the convergence factor for all simple shared shapers on the
router.
host1(config-qos-shared-shaper-control)#convergence-factor 25
The convergence factor determines how quickly the dynamic shaping rate converges with the calculated dynamic shaping rate, and is expressed as a percentage of the available bandwidth. The range for the convergence factor is 099 percent, with 0 being the most liberal and 99 the most conservative. The default value is 50.
3. (Optional) Configure the specify the reaction factor for all simple shared shapers on
the router.
host1(config-qos-shared-shaper-control)#reaction-factor 50
89
The reaction factor determines how the shared shaper reacts to changes in the measured rate. The range for the reaction factor is 01000; 0 is the most liberal and 1000 is the most conservative. The default value is 200.
4. (Optional) Specify the minimum value of the dynamic shaping rate as a percentage
of the shared shaping rate for all simple shared shapers on the router.
host1(config-qos-shared-shaper-control)#minimum-dynamic-rate-percent 50 The range for the minimum dynamic rate value is 0100 percent. The default value is 0.
5. (Optional) Configure a maximum value for the virtual output queue length (VOQL)
The VOQL tracks the amount of data over queued between simple shared-shaper rate periods. The range for the maximum VOQL value is 010000 milliseconds (ms). The default value is 4000. Related Documentation
Simple Shared Shaping Algorithm Overview on page 85 Variables of the Simple Shared Shaper Algorithm on page 87 Guidelines for Controlling the Simple Shared Shaper Algorithm on page 88 Sample Process for Controlling the Simple Shared Shaper Algorithm on page 90 Configuring Simple Shared Shaping on page 77 convergence-factor maximum-voql minimum-dynamic-rate-percent qos-shared-shaper-control reaction-factor
NOTE: The rates in this example are approximate and for illustrative purposes only. Your configuration might yield different results based on network variables.
90
Table 9 on page 91 lists the dynamic rate when the video flow is turned on for the five classes of simple shared shaper variables. Results vary because the amount of video measured in the first rising period is random, in the range 04 Mbps non-inclusive.
1
10 0 50
2
13080
3
11000
4
11000
5
11000
6
11000
7
11000
8
11000
9
11000
10
11000
10 0 50 10 0 50 10 0 50
In this example, a liberal maximum VOQL value is ineffective because the 15 Mbps shared-shaping rate is much higher than the 4 Mbps video rate. The video rate divided by the shared shaping rate is 26.6 percent, so any value higher than this has no effect.
NOTE: The rates in this example represent approximate egress-queue enqueue rates on an Ethernet line module; therefore, there is no ATM SAR or downstream devices are not used. More liberal configurations can be inappropriate when there might be queuing between the scheduler and the destination. VLAN queuing is used, and saturation rates are offered.
The most liberal case heavily reduces VOQL and changes of rate, leading to a shared shaper that quickly converges. 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.
91
Table 10 on page 92 lists the dynamic rate as the video flow stops for the five classes of simple shared shaper controls. Results might vary because the amount of video measured in the first falling period is random, in the range 04 Mbps non-inclusive.
1
11000
2
12132
3
15000
4
15000
5
15000
6
15000
7
15000
8
15000
9
15000
10
15000
Figure 26 on page 93 shows a graph of the dynamic rate when the video flow stops.
92
Related Documentation
Simple Shared Shaping Algorithm Overview on page 85 Variables of the Simple Shared Shaper Algorithm on page 87 Configuring Simple Shared Shaper Algorithm Variables on page 89
93
94
CHAPTER 12
Compound Shared Shaping Overview on page 95 Configuring Compound Shared Shaping on page 96 Example: Compound Shared Shaping for ATM VCs on page 98 Example: Compound Shared Shaping for ATM VPs on page 100
95
host1config)#ERROR 02/08/2005 14:06:36 qos: line card in slot 11: EFA2 hardware not installed. 1 compound shared shaper(s) converted to simple.
QoS automatically converts the compound shared shaper to a simple shared shaper.
NOTE: Compound shared shaping is not supported by the frame forwarding ASIC (FFA).
Priority constituents consume as much of the shared bandwidth as they can, subject to the bandwidth allocated to them by the hierarchical scheduler.
2. Priority constituents are ordered according to their priority. 3. The weighted constituents subdivide the remaining shared bandwidth in proportion
to their shared weights, again subject to the bandwidth allocated to them by the hierarchical scheduler. Related Documentation
For a list of shared shaper terms, see Shared Shaping Overview on page 67 Configuring Compound Shared Shaping on page 96
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.
96
The range for the shared-shaping rate is 10001000000000 bps (1 Kbps1000 Kbps); the default is no shaping rate. Use the operator and operandValue variables to specify the shared shaping rate as an expression. Burst is the catch-up number associated with the shaper; the range is 0522240 (0510 KB). Specifying 0 enables the router to select an applicable default value. By default, shared shaping is set to auto, where the router selects the type of shared shaping that is configured, depending on the line module. You must specify the compound keyword to actively shape voice and video traffic so that the shared rate cannot be exceeded, and shape data queue rates to the value of the shared rate minus the combined voice and video traffic rate. An error message is generated if you specify compound for line modules that do not support it, and the router applies simple shared shaping.
3. Configure the QoS profile and reference the scheduler profile.
(config)#qos-profile compound (config-qos-profile)#atm-vc node (config-qos-profile)#atm-vc node group AF (config-qos-profile)#atm-vc node group EF (config-qos-profile)#atm-vc queue traffic-class best-effort scheduler-profile shared-1mbps (config-qos-profile)#exit
TIP: The scheduler profile that you configured with the shared-shaping rate must be referenced in the best-effort queue or the best-effort scheduler node.
Related Documentation
Compound Shared Shaping Overview on page 95 Guidelines for Configuring Simple and Compound Shared Shaping on page 70 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 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
97
Configure the traffic classes, traffic-class groups, and additional scheduler profiles.
2. Configure the scheduler profile that defines the shared shaper and the profiles that
98
host1(config)#qos-profile vcSharedShaping
4. Create group nodes.
that defines the shared-shaping rate to the best-effort queue. Apply the legacy shaper profiles to the voice and video traffic queues.
host1(config-qos-profile)#atm-vc queue traffic-class best-effort scheduler-profile shared-1mbps host1(config-qos-profile)#atm-vc queue traffic-class video scheduler-profile 300Kbps host1(config-qos-profile)#atm-vc queue traffic-class voice scheduler-profile 200Kbps host1(config-qos-profile)#exit
7. Attach the QoS profile to an ATM subinterface.
In this example, the constituents of the VC shared shaper are the VC 1 best effort node, the VC 1 Group EF node, and the VC 1 Group AF node. The available bandwidth is strictly allocated in the following order:
1.
VC 1 EF group node
99
Related Documentation
Configuring Compound Shared Shaping on page 96 Compound Shared Shaping Overview on page 95
Configure the traffic classes, traffic-class groups, and additional scheduler profiles.
2. Configure the scheduler profile that defines the shared shaper and the profiles that
100
host1(config)#qos-profile vpSharedShaping
6. Create group nodes.
profile containing the shared-shaping rate is applied to the VP node that is in the default group and contains the best-effort queue.
host1(config-qos-profile)#atm-vp node scheduler-profile shared-5Mbps host1(config-qos-profile)#atm-vp node group AF scheduler-profile 2Mbps host1(config-qos-profile)#atm-vp node group EF scheduler-profile 400Kbps
8. Create a VC node for the default group.
host1(config-qos-profile)#atm-vc node
9. Create queues for the best-effort, video, and voice traffic.
host1(config-qos-profile)#atm-vc queue traffic-class best-effort host1(config-qos-profile)#atm-vc queue traffic-class AF host1(config-qos-profile)#atm-vc queue traffic-class EF host1(config-qos-profile)#exit
10. Attach the QoS profile to an ATM subinterface.
In this example, the constituents of the VP shared shaper are the VP 1 default group node, the VP 1 Group EF node, and the VP 1 Group AF node. The available bandwidth is strictly allocated in the following order:
1.
Related Documentation
Configuring Compound Shared Shaping on page 96 Compound Shared Shaping Overview on page 95
101
102
CHAPTER 13
Constituent Selection for Shared Shaping Overview on page 103 Implicit Constituent Selection Overview on page 105 Configuring Implicit Constituents for Simple or Compound Shared Shaping on page 110 Explicit Constituent Selection Overview on page 111 Configuring Explicit Constituents for Simple or Compound Shared Shaping on page 115
103
To use implicit constituent selection, you specify only the shared-shaping rate and the logical interface. The router identifies the constituents associated with the logical interface type and their allocated bandwidth. This method is appropriate for the typical case where the intent is to shape all subscriber queues to the shared rate. If you want instead to shape a subset of the queues for a subscriber to the shared rate, the explicit selection process is appropriate. Explicit selection is also useful when you want queues as the active constituents instead of the node below them. By choosing queues you can assign appropriate priority or weights.
Simple implicitConstituents are best-effort node or queues, and all nodes and queues in named traffic-class groups. Simple explicitThe software selects constituents based on the shared-shaping-constituent command. The weight and priority attributes of the shared-shaping-constituent command are ignored, because the simple shared shaper does not allocate bandwidth among constituents; instead it controls just the best-effort queue or node. Compound implicitConstituents are selected automatically by the software. If a node exists in a given traffic-class group, the node is active and the queues stacked above it are inactive constituents. The shared-shaping-constituent command does not affect constituent selection. However, if the command is present for a constituent that was implicitly selected, the software configures that constituent with the shared priority and shared weight as indicated. Compound explicitThe software selects constituents based on the shared priority and shared weight configured with the shared-shaping-constituent command. If no attributes are specified, the software supplies a shared priority consistent with the legacy scheduler configuration.
To specify the logical interface for shared shaping, associate a scheduler profile that includes the shared-shaping-rate command or the shared-shaping-rate simple command with a best-effort node or queue.
To specify the logical interface for shared shaping, associate a scheduler profile that includes the shared-shaping-rate rate explicit-constituents command or the shared-shaping-rate rate simple explicit-constituents command with a best-effort node or queue.
104
Chapter 13: Configuring Implicit and Explicit Constituent Selection for Shaping
Constituents consist of all nodes and queues for the same logical interface type. Active constituents are automatically selected from all constituents according to the implicit shared shaping rules.
Constituents consist of all nodes and queues for the same logical interface type. Active constituents are explicitly selected from all constituents by association with a scheduler profile that includes the shared-shaper-constituent command. If the scheduler profile associated with a constituent does not include this command, then the constituent is not active and is not shaped by the shared shaper.
Related Documentation
Implicit Constituent Selection Overview on page 105 Configuring Implicit Constituents for Simple or Compound Shared Shaping on page 110 Explicit Constituent Selection Overview on page 111 Configuring Explicit Constituents for Simple or Compound Shared Shaping on page 115
The point at which the scheduler profile that contains a shared-shaping-rate command is associated with a best-effort node or best-effort queue determines the logical interface type that the shared shaper applies to. Logical interface types include IP, VP, VC, VLAN, S-VLAN, and so on.
2. All nodes and queues for the same logical interface are potential constituents. 3. The best-effort node is selected if you configure node-based shared shaping. The
best-effort queue is selected if you configure queue-based shared shaping. If you configure both, then the best-effort node is selected over the best-effort queue.
4. Non-best-effort queues are selected.
The implicit selection process for compound shared shaping operates according to the following rules:
1.
The point at which the scheduler profile that contains a shared-shaping-rate command is associated with a best-effort node or best-effort queue determines the logical interface type that the shared shaper applies to. Logical interface types include IP, VP, VC, VLAN, and S-VLAN.
2. All nodes and queues for the same logical interface are potential constituents. 3. Nodes are selected over queues.
105
For example, suppose a shared shaper is associated with a particular interface type. A node for that interface type is present and has a queue for that interface type stacked above it. The node is selected and becomes an active constituent; the queue is not selected. Now suppose a shared shaper is associated with a logical interface at the best-effort node, and a second shared shaper is simultaneously associated with the same interface at the best-effort queue. In this case, the node is selected as the constituent, because nodes are selected over queues. In Figure 29 on page 106, scheduler profile A includes a shared-shaping rule, and is associated with the best-effort node for VC 2. The constituents are all the scheduler objects associated with VC 2: VC 2 nodes and VC 2 queues. Nodes are selected over queues, so the implicitly selected active constituents are the VC 2 default group node, the VC 2 Group EF node, and the VC 2 Group AF node.
Figure 29: Implicit Constituent Selection for Compound Shared Shaper at Best-Effort Node
In Figure 30 on page 107, scheduler profile B is associated with the best-effort queue for VC 3. This association indicates that the logical interface type being shared is VC. The constituents are all the scheduler objects associated with VC 3: VC 3 nodes and VC 3 queues. Nodes are selected over queues, so the implicitly selected active constituents for profile Bs 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.
106
Chapter 13: Configuring Implicit and Explicit Constituent Selection for Shaping
Figure 30: Implicit Constituent Selection for Compound Shared Shaper at Best-Effort Queue
Figure 30 on page 107 illustrates other examples of implicit constituent selection. It does not reflect typical configurations, but includes a mixture of interface types: IP, VC, and VP. If only scheduler profile A is applied, the associated interface is VC 1. The selected constituents then consist of the VC 1 best-effort node, the VC 1 TC voice queue, and the VC 1 TC video queue. If only scheduler profile B is applied, the associated interface is IP 1. The selected constituents then consist of the IP 1 best-effort queue, the IP 1 TC voice queue, and the IP 1 TC video queue. If only scheduler profile C is applied, the associated interface is VP 1. The selected constituents then consist of the VP 1 default group node, the VP 1 Group EF node, and the VP 1 Group AF node.
Auto-strict nodes and queues have the highest priority. Nodes and queues in extended traffic-class groups are next. Nodes and queues in the default traffic-class group have the lowest priority.
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
107
implicit shared shaping, the shared shaper assigns the voice queue all the 2 MB, the video queue the next priority, and the best-effort node the last priority. The voice queue is unlikely to drop because it has highest priority in the hierarchical scheduler as well as highest priority within its shared shaper. The video queue is less likely to drop, but you must still take care that the hierarchical scheduler is provisioned to allocate the proper assured bandwidth to video. The shared shaper can shape, or deny, bandwidth to its constituents, but it cannot allocate assured bandwidth in the hierarchical scheduler. The compound shared-shaper mechanism also works as follows. In the legacy scheduler, weight and shaping rate are independent attributes that together determine bandwidth allocation. The scheduler allocates bandwidth based on relative weights, and the shaper can deny that bandwidth when the shaping rate is reached. With the shared shaper in effect, two independent shaping rates must be satisfied for the queue or node to dequeue. A deficit in either type of shaping bounds the bandwidth. As a general way of predicting the scheduler behavior, if the physical port is congested because many queues and nodes are competing in the hierarchical scheduler, the legacy weights and shaping rates dominate the scheduler outcome. If the hierarchical scheduler is not congested, a shared shaper configured for a logical interface dominates the outcome for the traffic scheduled through that logical interface. The compound shared shaper orders constituents, and allocates shared bandwidth to them, according to the following rules:
1.
Strict constituents in the auto-strict-priority traffic-class group For multiple strict-priority traffic-class groups, bandwidth allocation order is the same order in which the additional strict traffic class groups were configured. You can issue the show traffic-class-groups command to view this order.
For multiple extended traffic class groups, bandwidth allocation order is the same order in which the traffic class groups were configured. You can issue the show traffic-class-groups command to view this order.
3. Strict constituents in the default group 4. Weighted constituents in the auto-strict-priority traffic class group 5. Weighted constituents in extended traffic class groups 6. Weighted constituents in the default group
By default, strict constituents transmit traffic at a rate up to the lesser of their shared-shaping rate or the legacy shaping rate. Individual strict constituents can be allocated any bandwidth value less than the shared rate. The sum of all constituent rate credits does not have to be less than the shared rate. Individual constituent rates are not capped, because a particular traffic class often does not exceed a limit because of admission control, or because the class is policed at some point in the path. 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
108
Chapter 13: Configuring Implicit and Explicit Constituent Selection for Shaping
in proportion to their shared-shaping-weight. A higher weight value grants the constituent a greater proportion of the available bandwidth. Although a shared shaper can be applied to up to eight constituents, only four of these can be weighted constituents. If you configure more than four weighted constituents as part of the same shared shaper, the first four are treated as weighted constituents but the remainder are handled as strict constituents, generating a warning message.
Scheduler profile A specifies the shared-shaping rate of 1Mbps for the best-effort node, which is associated with a VC logical interface. The node is further configured with a weight of 1. Scheduler profile B specifies the VC 1 AF node as a weighted constituent with a weight of 31. The implicitly selected constituents of the shared shaper are the VC 1 best-effort node, the VC 1 AF group node, and the VC 1 EF group node. Bandwidth is allocated as follows:
The VC 1 EF group node is strict and can transmit up to the shared-shaping rate of 1Mbps. Any remaining bandwidth is available to the remaining constituents. 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
g014385
109
31/32nds of the available bandwidth when both constituents are competing for bandwidth.
The VC 1 best-effort node is weighted with VC 1 AF group node. The sum of the constituent weights is 32. With a weight of 1, the VC 1 best-effort node can transmit 1/32 of the available bandwidth when both constituents are competing for bandwidth.
Figure 32 on page 110 illustrates an example of mixed interface shaping and its implications for implicit constituent selection for compound shared shaping.
Figure 32: Implicit Constituent Selection for Compound Shared Shaper: Mixed Interface Types
Related Documentation
Configuring Implicit Constituents for Simple or Compound Shared Shaping on page 110
Simple implicitConstituents are best-effort node or queues, and all nodes and queues in named traffic-class groups. Compound implicitConstituents are selected automatically by the software. If a node exists in a given traffic-class group, the node is active and the queues stacked above it are inactive 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.
110
Chapter 13: Configuring Implicit and Explicit Constituent Selection for Shaping
1.
host1(config-scheduler-profile)#shared-shaping-constituent weight 28
Including this command does not affect how the system selects the compound implicit constituent. If the command is present for a constituent that was implicitly selected, the software configures that constituent using the strict-priority or weight attributes. After you configure implicit constituents:
Configure the scheduler hierarchy with the best-effort nodes and queues. See Configuring a QoS Profile on page 126.
Related Documentation
Constituent Selection for Shared Shaping Overview on page 103 Implicit Constituent Selection Overview on page 105 scheduler-profile shared-shaping-constituent shared-shaping-rate
111
NOTE: If you explicitly specify both a node and the queues stacked above the node as constituents in a scheduler profile, compound shared shaping uses the node as the constituent.
For compound shared shaping, omit the simple keyword. For a compound shared shaper, you can further designate the explicit constituents as priority or weighted.
In this example, the VC shared shaper has two explicit constituents, the VC 1 best effort node and the VC 1 Group EF node. By default, these constituents are considered to be strict constituents with a priority of 8. If implicit selection rules are followed in this example, the association of the shared shaper with the VC 1 best-effort node selects the VC 1 best effort node, the VC 1 Group EF node, and the VC 1 Group AF node.
112
Chapter 13: Configuring Implicit and Explicit Constituent Selection for Shaping
In Case 1, scheduler profile A associates the shared-shaping rate with the VLAN 1 best-effort queue. Table 12 on page 113 lists the explicit constituents of the shared shaper and the bandwidth allocated to each constituent:
Bandwidth Allocation
Strict constituent that can consume up to its legacy shaping-rate. Weighted constituent that shares bandwidth with its weighted shared shaper siblings in a proportion of 4/10. Weighted constituent that shares bandwidth with its weighted shared shaper siblings in a proportion of 3/10. Weighted constituent that shares bandwidth with its weighted shared shaper siblings in a proportion of 2/10. Weighted constituent that shared bandwidth with weighted shared shaper siblings in a proportion of 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.
113
In Case 2, scheduler profile B associates the shared-shaping rate with the best-effort node for VLAN 1. Table 13 on page 114 lists the explicit constituents of the shared shaper and the bandwidth allocated to each constituent:
Bandwidth Allocation
Strict constituent that can consume up to its legacy shaping-rate. Weighted constituent that shares bandwidth with its weighted shared shaper siblings in a proportion of 4/10. Weighted constituent that shares bandwidth with its weighted shared shaper siblings in a proportion of 3/10. Weighted constituent that shared bandwidth with weighted shared shaper siblings in a proportion of 3/10. 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 Documentation
Configuring Explicit Constituents for Simple or Compound Shared Shaping on page 115
114
Chapter 13: Configuring Implicit and Explicit Constituent Selection for Shaping
Simple explicit constituentsThe software selects constituents based on the shared-shaping-constituent command. The weight and priority attributes of the shared-shaping-constituent command are ignored, because the simple shared shaper does not allocate bandwidth among constituents; instead it controls just the best-effort queue or node. Compound explicitThe software selects constituents based on the configured shared priority and shared weight in the shared-shaping-constituent command. If no attributes are specified, the software supplies a shared priority consistent with the legacy scheduler configuration. You can specify a constituent as strict (priority) or weighted. Strict-priority constituents are allocated bandwidth ahead of weighted 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.
2. Configure the shared-shaper and specify that you do not want the router to identify
shared shaper constituents associated with the logical interface. To configure a simple shared shaper:
host1(config-scheduler-profile)#shared-shaping-rate 128000 bps
host1(config-scheduler-profile)#shared-shaping-constituent weight 28
You can specify a constituent as strict (priority) or weighted. Strict-priority constituents are allocated bandwidth ahead of weighted constituents. 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 18 and the default value is 8. A lower value correlates to a higher claim.
115
For weighted constituents, the range is 131 and the default value is 8. The weights of all sibling weighted constituents are added together. Then each weighted constituent is allocated bandwidth according to the proportion of its weight to the total. Related Documentation
Constituent Selection for Shared Shaping Overview on page 103 Explicit Constituent Selection Overview on page 111 scheduler-profile shared-shaping-constituent shared-shaping-rate
116
CHAPTER 14
Monitoring the QoS Scheduler Hierarchy on page 307 Monitoring the Configuration of Scheduler Profiles on page 313 Monitoring Shared Shapers on page 314 Monitoring Shared Shaper Algorithm Variables on page 316
117
118
PART 4
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 143 Monitoring a Scheduler Hierarchy on an Interface with QoS Profiles on page 149
119
120
CHAPTER 15
QoS Profile Overview on page 121 Managing System Resources for Nodes and Queues on page 121 Scaling Subscribers on the TFA ASIC with QoS on page 122
Supported Interface Types for QoS Profiles on page 125 Configuring a QoS Profile on page 126
121
and 128,000 level 2 nodes or queues. The router implicitly creates the level 2 node. Each line module supports a maximum of 64,000 nodes or queues per line module. Line modules with the TFA ASIC hardware provide 96,000 descriptors that are shared between all nodes and queues. Each line module supports a maximum of 64,000 nodes or queues. Related Documentation
Scaling Subscribers on the TFA ASIC with QoS on page 122 For more information about system resource requirements for shadow nodes, see Managing System Resources for Shadow Nodes on page 145 For information about egress memory available on ASIC line modules, see Memory Requirements for Queue and Buffers on page 19 To identify the type of ASIC used by a line module, see the ERX Module Guide and the E120 and E320 Module Guide
If the configuration includes IP and VLANs, you can configure shapers within those queues to control service throughout. For example, in a triple-play environment with voice, video, and data service, you might want to limit the overall rate of traffic using a shared shaper. At the same time, you might want to individually restrict the maximum rate of each of the services. To conserve node usage, attach shapers to the queue for each service, and attach the shared shaper to the best-effort queue. These queues must be at level 3 in the scheduler hierarchy. Typically, aggregation nodes such as an S-VLAN are placed at level 2. The VLAN queues then feed in to the S-VLAN nodes, which then feed to the level 1 nodes below. 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.
122
If the configuration includes S-VLANs, you could configure S-VLAN nodes in the default traffic-class group. Combining S-VLAN and VLAN nodes uses fewer resources than when you combine IP and VLAN nodes. You can also configure additional S-VLAN nodes in other traffic-class groups.
In non-default traffic-class groups, you can configure a group node and VLAN queues. Although this apparently does not consume nodes, it does consume a hidden, phantom node for each queue, to satisfy the level requirement of the TFA ASIC. Alternatively, use group nodes and shadow nodes. We recommend that you configure an Ethernet shadow node in the group with the following QoS profile rule:
host1(config-qos-profile)#ethernet shadow-node group groupname
This rule stacks another node over the group node, so all VLAN queues are stacked above the single shadow node. No nodes are consumed in the traffic-class group. Related Documentation
For more information about system resource requirements for shadow nodes, see Managing System Resources for Shadow Nodes on page 145 For QoS system maximums, see JunosE Release Notes, Appendix A, System Maximums Monitoring the QoS Profiles Attached to an Interface on page 324
123
124
CHAPTER 16
Supported Interface Types for QoS Profiles on page 125 Configuring a QoS Profile on page 126 Attaching a QoS Profile to an Interface on page 128 Munged QoS Profile Overview on page 131 Example: Port-Type QoS Profile Attachment on page 133 Example: QoS Profile Attachment to Port on page 135 Example: Diffserv Configuration with Multiple Traffic-Class Groups on page 137
Queue
Node
Group
Shadow Node
125
Queue
Node
Group
Shadow Node
Related Documentation
Configuring a QoS Profile on page 126 Configuring Shadow Nodes on page 146
Configure the traffic classes. See Configuring Traffic Classes That Define Service Levels on page 14.
Configure the queuing hierarchy. See Configuring Queue Profiles to Manage Buffers and Thresholds on page 22.
Configure the scheduler hierarchy and shaping with scheduler profiles. See Configuring a Scheduler Hierarchy on page 47.
126
When you configure a group node, you can also reference a default or named traffic-class group, a scheduler profile, or a statistics profile. If you do not specify a traffic-class group, the group node defaults to the default group. Each traffic class can belong to only one traffic-class group (either the default group or a named group). The router supports up to four traffic-class groups above a given port.
3. (Optional) Configure a scheduler node for interfaces.
When you configure a scheduler node, you can also reference a default or named traffic-class group and a scheduler profile. The scheduler profile supplies a relative weight and potentially a shaping rate to be applied at the scheduler node.
NOTE: You cannot associate a scheduler profile with a port-type interface unless you also specify the strict-priority group.
host1(config-qos-profile)#atm queue traffic-class strict-priority scheduler-profile scheduler1 queue-profile queue1 drop-profile drop1
When you configure a queue, you can include any of the following profiles:
The scheduler profile supplies a relative weight and potentially a shaping rate to be applied at the queue. The queue profile supplies threshold information for the queue if the router defaults are not appropriate. The drop profile supplies dropping behavior of a set of egress queues. Each queue traffic class can appear in only one traffic-class group.
Related Documentation
Attaching a QoS Profile to an Interface on page 128 Supported Interface Types for QoS Profiles on page 125 Configuring Shadow Nodes on page 146 Monitoring a Scheduler Hierarchy on an Interface with QoS Profiles on page 149 For information about configuring QoS profiles with Service Manager, see JunosE Broadband Access Configuration Guide group node
127
qos-profile queue
Attaching a QoS Profile to a Base Interface on page 128 Attaching a QoS Profile to an ATM VP on page 128 Attaching a QoS Profile to an S-VLAN on page 129 Attaching a QoS Profile to a Port Type on page 130
host1(config-if)#qos-profile qosp-ethernet-queuing
If you attempt to modify the QoS profile attached to an ATM VP that contains nonbroadcast multiaccess (NBMA) or multipoint interfaces from profileA to profileB by using the atm-vp qos-profile command for a specific VP on that interface, the command is configured correctly and no error message is displayed in the CLI interface. However, the shaping rate on the interfaces that are part of the ATM VP is not properly updated
128
with the shaping rate specified in profileB. Instead, the multipoint interfaces remain configured with the shaping rate set in profileA. To modify the QoS profile currently attached to ATM VPs that contain NBMA or multipoint interfaces from another profile, you must first remove the QoS profile attached to the interfaces by using the no atm-vp qos-profile command in Interface Configuration mode, and then attach the new QoS profile to the interfaces by using the atm-vp qos-profile command. This restriction exists because the mungeing of QoS profiles does not occur correctly if any of the attributes of ATM VPs with multipoint interfaces are modified. If you modify the QoS profile attached to a point-to-point ATM interface from profileA to profileB by using the qos-profile command (or the atm-vp qos-profile command for a specific VP on the ATM interface) in Interface Configuration mode, the shaping rate is correctly configured on the interface and is modified with the value specified in profileB. To modify the QoS profile attached to an ATM VP that contains an NBMA or a multipoint interface from profileA to profileB, perform the following steps. These steps assume that profileA and profileB have been previously configured on the router.
1.
2. Remove the QoS profile, profileA, currently attached to the ATM VP that contains the
NMBA interface.
host1(config-if)#no atm-vp 1 qos-profile profileA
3. Attach the new QoS profile, profileB, that you want to be attached to the ATM VP
host1(config-if)#svlan id 0 1
3. Attach the QoS profile to the S-VLAN.
129
The interface type can be: atm, ethernet, lag, serial, or server-port. A profile attached to a port must specify a queue for each forwarding interface type in the best-effort traffic class. To restore the default port-type:
Issue the qos-port-type-profile command and specify the server-default QoS profile from Global Configuration mode:
host1(config)#qos-port-type-profile server-port qos-profile server-default
Related Documentation
Supported Interface Types for QoS Profiles on page 125 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 atm vp-tunnel encapsulation vlan interface qos-port-type-profile qos-profile svlan id svlan qos-profile
130
2. Traverse down the stack of interfaces until another QoS profile attachment is found. 3. Add rules from the lower-attached QoS profile to the munged QoS profile. Conflicting
rules from the lower-attached QoS profile are not added: rules in higher-attached QoS profiles override or eclipse rules in lower-attached QoS profiles.
4. Repeat Steps 2 and 3 until a port interface is reached at the bottom of the interface
stack. a. If there is a QoS profile attached at the port, add the profiles rules to the munged QoS profile, and the munge algorithm is then complete. b. If there is no QoS profile attached at the port, then locate the QoS profile indicated in the qos-port-type-profile command that corresponds to the interface type of the port. For example, if the port is an ATM interface, the default QoS port-type profile for type 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. After the munged QoS profile is complete, the router reprocesses the queues for all forwarding interfaces in the scope of the attachment, adding, deleting, or modifying the scheduler hierarchy as required by the munged QoS profile rules. Conflicting node rules operate differently than this. With conflicting node rules, the mungeing algorithm for QoS nodes start at the base of the interface hierarchy (usually near the physical interface), instead of at the top of the interface column. If a QoS profile is not attached to the port, nodes are added to the interface column according to the QoS port-type profile. Nodes are subsequently added from profiles that are attached higher in the interface column until all node rules from the interface column have been added, or the maximum hierarchy of three nodes has
131
been reached. Higher level nodes can not eclipse lower-attached nodes. For example, if a QoS hierarchy is Ethernet node > Ethernet group node > VLAN node > queue, an IP node from a higher-attached QoS profile cannot eclipse the VLAN node. In Step 3, the router must decide which rules from a QoS profile conflict with rules already contained within the munged QoS profile. Queue rules are identified by their {interface type, traffic class} pair; two queue rules with the same interface type and traffic class are deemed conflicting. Node rules are identified by their {interface type, traffic-class group} pair; two node rules with the same interface type and traffic-class group are deemed conflicting.
NOTE: The munge algorithm is modified when you configure QoS for 802.3ad link aggregation interfaces.
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
All forwarding interfaces stacked above the port are within the scope of the attachment, so all IP interfaces stacked above the port will be provisioned with a queue in the priority-data traffic class, shaped to 64 Kbps. The QoS profile attached at subinterface ATM 11/0.2 contains the following two rules:
host1(config)#qos-profile atmVc host1(config-qos-profile)#ip queue traffic-class priority-data scheduler-profile 1mbps host1(config-qos-profile)#ip queue traffic-class voice-over-ip host1(config-qos-profile)#exit
132
The queue rule for {interface type IP, traffic-class priority-data} in the QoS profile that is attached to ATM 11/0.2 effectively overrides the queue rule for the same interface type and traffic class in the port-attached QoS profile on ATM11.0. The second queue rule, which is for the voice-over-ip traffic-class, is not conflicting. In this configuration, the provider has configured a 64 Kbps priority-data queue for each IP interface stacked above the port. But the IP interface above the ATM 11/0.2 attachment provides 1 Mbps for priority-data, and also has a second queue provisioned for VoIP.
NOTE: When a QoS profile is attached to an interface, the router first searches to determine if a munged QoS profile already exists. If you modify an existing QoS profile, the router automatically updates all munged QoS profiles that are dependent on the modified profile.
Related Documentation
For more information about the munge algorithm and 802.3ad link aggregation interfaces, see Munged QoS Profiles and Load Balancing on page 178
ATM 11/0.1QoS profile qp1 is attached ATM 11/0.2QoS profile qp2 is attached ATM 11/0.3No 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.
133
host1(config-qos-profile)#atm-vc queue traffic-class tc2 scheduler-profile sp2 queue-profile qp2 host1(config-qos-profile)#atm-vc queue traffic-class tc3 scheduler-profile sp3 queue-profile qp3 host1(config-qos-profile)#atm-vc queue traffic-class tc4 scheduler-profile sp4 queue-profile qp4 host1(config-qos-profile)#atm-vc queue traffic-class tc5 scheduler-profile sp5 queue-profile qp5 host1(config-qos-profile)#exit
2. Create and configure QoS profile qp2.
host1(config)#qos-profile qp2 host1(config-qos-profile)#atm-vp node scheduler-profile sp1 host1(config-qos-profile)#atm-vc queue traffic-class tc1 scheduler-profile sp1 queue-profile qp1 host1(config-qos-profile)#atm-vc queue traffic-class tc2 scheduler-profile sp2 queue-profile qp2 host1(config-qos-profile)#atm-vc queue traffic-class tc3 scheduler-profile sp3 queue-profile qp3 host1(config-qos-profile)#exit
3. Attach the QoS profiles to the ATM subinterfaces, as shown in Figure 37 on page 133.
host1(config)#interface atm 11/0.1 host1(config-subif)#qos-profile qp1 host1(config-subif)#exit host1(config)#interface atm 11/0.2 host1(config-subif)#qos-profile qp2 host1(config-subif)#exit
4. 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.
host1# show qos interface-hierarchy interface atm 11/0 attachment@ atm-vc ATM11/0.2: qos interface rule traffic scheduler queue t-class profile type type class profile profile group --------------- ---- --------------- ------- ------qp2@ATM11/0.2 atm-vp node sp1 qp2@ATM11/0.2 atm-vc queue tc1 sp1 qp2@ATM11/0.2 atm-vc queue tc2 sp2 qp2@ATM11/0.2 atm-vc queue tc3 sp3 atm-default @atm ip node default atm-default @atm atm-vc node default atm-default @atm Bridge node default atm-default @atm ipv6 node default atm-default @atm ip queue best-effort default atm-default @atm atm queue best-effort default atm-default @atm atm-vc queue best-effort default atm-default @atm Bridge queue best-effort default atm-default @atm ipv6 queue best-effort default attachment@ atm-vc ATM11/0.1: qos interface rule traffic scheduler profile type type class profile --------------- ---- --------------default qp1 qp2 qp3 default default default default default default default default default queue t-class profile group ------- -------
134
qp1@ATM11/0.1 qp1@ATM11/0.1 qp1@ATM11/0.1 qp1@ATM11/0.1 qp1@ATM11/0.1 qp1@ATM11/0.1 atm-default @atm atm-default @atm atm-default @atm atm-default @atm atm-default @atm atm-default @atm atm-default @atm atm-default @atm atm-default @atm
atm-vp atm-vc atm-vc atm-vc atm-vc atm-vc ip atm-vc Bridge ipv6 ip atm atm-vc Bridge ipv6
node queue queue queue queue queue node node node node queue queue queue queue queue
sp1 sp1 sp2 sp3 sp4 sp5 default default default default default default default default default
default qp1 qp2 qp3 qp4 qp5 default default default default default default default default default
ATM subinterface 11/0.3 was not shown because no QoS profile is attached to it. You can display the QoS interface hierarchy for subinterface 11/0.3 by specifying the subinterface, as shown below. In this case, the QoS port-type profile, atm-default, is attached (by default) to the ATM major interface, ATM 11/0, below ATM subinterface 11/0.3. Because no QoS profile is attached to this ATM subinterface, the QoS port-type profile is applied. The @atm in the qos profile column indicates that the row comes from a default QoS port-type profile that is below the interfaces shown: subinterfaces ATM 11/0.2 and ATM 11/0.1 in this example. You can explicitly show the ATM subinterface that has no explicit QoS profile attachment, as shown below. 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: qos interface rule traffic scheduler profile type type class profile --------------- ---- --------------atm-default@atm ip node default atm-default@atm atm-vc node default atm-default@atm Bridge node default atm-default@atm ipv6 node default atm-default@atm ip queue best-effort default atm-default@atm atm queue best-effort default atm-default@atm atm-vc queue best-effort default atm-default@atm Bridge queue best-effort default atm-default@atm ipv6 queue best-effort default
queue t-class profile group ------- ------default default default default default default default default default
ATM 11/0.1No QoS profile is explicitly attached ATM 11/0.2QoS profile qp2 is attached ATM 11/0.3No QoS profile is explicitly attached
135
The qp1 profile overrides the QoS port-type profile, atm-default, on subinterfaces 1 and 3. It does not override profile qp2, which was explicitly attached to subinterface 2.
host1(config)#qos-profile qp2 host1(config-qos-profile)#atm-vp node scheduler-profile sp1 host1(config-qos-profile)#atm-vc queue traffic-class tc1 scheduler-profile sp1 queue-profile qp1 host1(config-qos-profile)#atm-vc queue traffic-class tc2 scheduler-profile sp2 queue-profile qp2 host1(config-qos-profile)#atm-vc queue traffic-class tc3 scheduler-profile sp3 queue-profile qp3 host1(config-qos-profile)#exit
3. Attach QoS profile qp1 to ATM interface 11/0.
136
5. Display the QoS interface hierarchy for ATM 11/0. host1#show qos interface-hierarchy interface atm 11/0 qos interface rule traffic scheduler profile type type class profile --------------- -----------------@ATM11/0 atm queue qp1@ATM11/0 atm-vp node qp1@ATM11/0 atm-vc queue qp1@ATM11/0 atm-vc queue qp1@ATM11/0 atm-vc queue qp1@ATM11/0 atm-vc queue qp1@ATM11/0 atm-vc queue attachment@ atm-vc ATM11/0.2: qos interface rule profile type type --------------- ---qp2@ATM11/0.2 qp2@ATM11/0.2 qp2@ATM11/0.2 qp2@ATM11/0.2 @ATM11/0 qp1@ATM11/0 qp1@ATM11/0 atm-vp atm-vc atm-vc atm-vc atm atm-vc atm-vc node queue queue queue queue queue queue best-effort tc1 tc2 tc3 tc4 tc5 traffic class ------default sp1 sp1 sp2 sp3 sp4 sp5 scheduler profile --------sp1 sp1 sp2 sp3 default sp4 sp5
queue t-class profile group ------- ------default default qp1 qp2 qp3 qp4 qp5 queue t-class profile group ------- ------default qp1 qp2 qp3 default qp4 qp5
Note that:
ATM best-effort queues are created on ATM interface @ATM11/0 and ATM 11/0.2. ATM 11/0.2 subinterface has three queues (traffic classes tc1, tc2, and tc3) that come from QoS profile qp2. Traffic class tc3 is defined in both QoS profile qp1 and qp2. The 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.
The voice service gets low-latency, strict priority treatment through the fabric and on egress. You configure an assured rate of 20 Mbps, and shape the traffic to 20 Mbps. Each voice user is shaped to 1 Mbps to support up to 20 voice subscribers without
137
oversubscription. Call admission control ensures that there are no more than 20 simultaneous voice service subscribers. Unused bandwidth is divided among the video and best-effort users.
The video service is scheduled by the HRR scheduler and gets the hierarchical assured rate. You shape the video traffic to 50 Mbps. Each video service user is assured 1 Mbps, and is shaped to 1 Mbps to support up to 50 video subscribers without oversubscription. Call admission control ensures that there are no more than 50 simultaneous video service subscribers. Unused bandwidth is divided among the best-effort users. The best-effort data service is scheduled by the HRR scheduler and gets the bandwidth left over from the voice and video services.
Create the video and voice traffic classes. Assign the voice traffic class a strict-priority treatment within the fabric. Manually creating a best-effort traffic class is superfluous because the router creates this class by default.
(config)#traffic-class video (config-traffic-class)#exit (config)#traffic-class voice (config-traffic-class)#fabric-strict-priority (config-traffic-class)#exit (config)#traffic-class best-effort (config-traffic-class)#exit
2. 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
3. Assured traffic is not strict, so it is scheduled by the HRR scheduler. Shape the assured
traffic to 50 Mbps, and specify the hierarchical assured rate to give assured traffic preferential treatment over best-effort traffic.
(config)#scheduler-profile assuredGroup (config-scheduler-profile)#shaping-rate 50000000 (config-scheduler-profile)#assured-rate hierarchical (config-scheduler-profile)#exit
4. Best effort traffic is also scheduled by the HRR scheduler. You do not apply any shaping
voice and video to 1 Mbps. Because you do not specify a shaping rate, the best-effort traffic can borrow unused bandwidth.
(config)#scheduler-profile voice
138
(config-scheduler-profile)#shaping-rate 1000000 (config-scheduler-profile)#exit (config)#scheduler-profile video (config-scheduler-profile)#shaping-rate 1000000 (config-scheduler-profile)#exit (config)#scheduler-profile best-effort (config-scheduler-profile)#exit
6. Put the video traffic class into the assured-forwarding traffic-class group and specify
the group as strict priority. Put the voice traffic class into the expedited-forwarding traffic-class group. Put the best-effort traffic class into the best-effort traffic-class group.
(config)#traffic-class-group assured-forwarding auto-strict-priority (config-traffic-class-group)#traffic-class video (config-traffic-class-group)#exit (config)#traffic-class-group expedited-forwarding extended (config-traffic-class-group)#traffic-class voice (config-traffic-class-group)#exit (config)#traffic-class-group best-effort extended (config-traffic-class-group)#traffic-class best-effort (config-traffic-class)#exit
7. Create a QoS profile that contains the group rules for the assured-forwarding,
IP 1 subscribes to data, video, and voice services. IP 2 subscribes to data and video services. IP 3 subscribes to data and voice services.
139
The following set of commands configures the QoS profile detailed in Step 7 previously. Each line in the profile is known as a profile rule. The numbers associated with each rule correspond to the numbers in Figure 39 on page 140.
(config)#qos-profile qpDiffServExample (1) (config-qos-profile)#ethernet group best-effort scheduler-profile bestEffortGroup (2) (config-qos-profile)#ethernet group assured-fwd scheduler-profile assuredGroup (3) (config-qos-profile)#ethernet group expedited-fwd scheduler-profile expeditedGroup (4) (config-qos-profile)#ip node group best-effort scheduler-profile default (5) (config-qos-profile)#ip node group assured-fwd scheduler-profile default (6) (config-qos-profile)#ip node group expedited-fwd scheduler-profile default (7) (config-qos-profile)#ip queue traffic-class voice scheduler-profile voice (8) (config-qos-profile)#ip queue traffic-class video scheduler-profile video (9) (config-qos-profile)#ip queue traffic class best-effort scheduler-profile best-effort
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. For example, the following set of commands configures the same QoS profile, but with the group removed, as shown in Figure 40 on page 141.
(config)#qos-profile qpDiffServExample (config-qos-profile)#ip node 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
In this case, the configuration creates the groups but does not place any of the traffic classes into the groups. Figure 40 on page 141 shows that IP 1, IP 2, and IP 3 contain the ungrouped traffic classes, data, video, and voice.
140
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.
141
142
CHAPTER 17
Shadow Node Overview on page 143 Shadow Nodes and Scheduler Behavior on page 144 Managing System Resources for Shadow Nodes on page 145 Configuring Shadow Nodes on page 146 Example: Shadow Nodes over VLAN and IP Queues on page 147 Example: Shadow Nodes on the Same Traffic-Class Group on page 148 Example: Shadow Nodes on Different Traffic-Class Groups on page 148
143
The first scheduler hierarchy displayed in Figure 41 on page 144 shows Queue A, Queue B, and Node C at the same scheduler level and with the same weight of 8. They equally share the bandwidth available to the level 1 node. The second scheduler hierarchy in Figure 41 on page 144 shows the phantom nodes the router added for Queue A and Queue B. It also shows the weight associated with Queue A and Queue B. As the result, Phantom A, Phantom B, and Node C share the bandwidth of the level 1 node. The phantom nodes do not change the behavior of Queue A and Queue B.
Figure 42 on page 145 compares a scheduler hierarchy with and without shadow nodes.
144
Unlike phantom nodes, shadow nodes can alter the behavior of the scheduler. The first scheduler hierarchy in Figure 42 on page 145 shows VLAN interfaces A, B and C stacked above the same S-VLAN interface. Interfaces A and B have the same scheduler hierarchy (referencing qos-profile AB) and have a VLAN queue stacked directly above the S-VLAN node. In this case, VLAN interfaces A, B and C share the same 33 percent bandwidth available to the S-VLAN node. Interface C has a VLAN queue stacked above a VLAN node and the S-VLAN node (referencing qos-profile C). Specifying a shadow node forces the VLAN queue to the proper scheduler level. The second scheduler hierarchy in Figure 42 on page 145 shows the shadow node that is applied after QoS profile AB-shadow is assigned to interfaces A and B. As a result, interfaces A and B have 25 percent of the S-VLAN bandwidth and interface C has 50 percent of the S-VLAN bandwidth. The S-VLAN shadow node uses the same scheduler profile as the queue. To provide interfaces A and B with the proper weight, configure the weight of the shadow node to the sum of its queue weight. You can use hierarchical parameter instances and weight expressions to configure an appropriate weight. Related Documentation
For a list of interface types supported for shadow nodes, see Supported Interface Types for QoS Profiles on page 125 For more information about hierarchical parameters, see Hierarchical QoS Parameters Overview on page 249
145
Shadow node queues stack above a port node, a level 1 node, and a shadow node. Therefore, the shadow node queue is at level 3. The router does not implicitly create any nodes for the queues. You can configure 64,000 level 1 queues using shadow nodes by specifying the group and shadow node rules in the QoS profile. Each level 1 queue is stacked above the port, the group node, and the shadow node; therefore, it requires 64,002 descriptors. Table 15 on page 146 lists the number of nodes required to create a queue.
Related Documentation
Managing System Resources for Nodes and Queues on page 121 Scaling Subscribers on the TFA ASIC with QoS on page 122
Configure the traffic classes. See Configuring Traffic Classes That Define Service Levels on page 14.
Configure the queuing hierarchy. See Configuring Queue Profiles to Manage Buffers and Thresholds on page 22.
Configure the scheduler hierarchy and shaping with scheduler profiles. See Configuring a Scheduler Hierarchy on page 47.
146
QoS profile.
host1(config-qos-profile)#atm group default scheduler-profile default
The router creates the shadow node when the following conditions are met:
After all the nodes and group nodes are created. If the queues are not at the required scheduler level. When a node of the same interface type has existed in the same group of the scheduler hierarchy. Shadow Node Overview on page 143 Shadow Nodes and Scheduler Behavior on page 144 Managing System Resources for Shadow Nodes on page 145 Monitoring a Scheduler Hierarchy on an Interface with QoS Profiles on page 149 group node qos-profile queue shadow-node
Related Documentation
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
147
148
CHAPTER 18
Monitoring the QoS Profiles Attached to an Interface on page 324 Monitoring the Configuration of QoS Port-Type Profiles on page 325 Monitoring the Configuration of QoS Profiles on page 325 Monitoring the Configuration of Scheduler Profiles on page 313 Monitoring QoS Parameter Instances on page 336
149
150
PART 5
Configuring an Integrated Scheduler to Provide QoS for ATM on page 153 Configuring QoS for Gigabit Ethernet Interfaces and VLAN Subinterfaces on page 171 Configuring QoS for 802.3ad Link Aggregation Groups on page 177 Configuring QoS for L2TP Sessions on page 189 Configuring Interface Sets for QoS on page 199
151
152
CHAPTER 19
ATM Integrated Scheduler Overview on page 153 Integrating the HRR Scheduler and SAR Scheduler on page 156 Per-Packet Queuing on the SAR Scheduler Overview on page 157 Guidelines for Configuring QoS over ATM on page 161 Configuring Default Integrated Mode for ATM Interface on page 162 Configuring Low-Latency Mode for Per-Port Queuing on ATM Interfaces on page 164 Configuring Low-CDV Mode for Per-Port Queuing on ATM Interfaces on page 166 Configuring the QoS Shaping Mode for ATM Interfaces on page 169 Disabling Per-Port Queuing on ATM Interfaces on page 169 Monitoring QoS Configurations for ATM on page 170
153
NOTE: The term HRR scheduler is used in this chapter to describe the scheduling performed by the ASIC on the ATM line module. Although the ASIC might differ depending on the ATM line module, the configuration and performance of the HRR scheduler are the same. For example, the ERX7xx models, ERX14xx models, and ERX310 Broadband Services router use the egress forwarding ASIC (EFA); and the E120 and E320 Broadband Services Routers use the frame forwarding ASIC (FFA) on the ES2 4G LM.
The HRR scheduler and the SAR scheduler work together as an integrated scheduler for ATM traffic. The HRR scheduler is configured by default with per-VC and per-IP interface scheduler nodes, and one best-effort class queue for each IP interface. The SAR scheduler implements weighted round-robin scheduling with one queue per VC. The VC queues are grouped into round robins based on the ATM service classes and the VP tunnels you have configured. In the default integrated mode, controlled by the ATM application, the SAR scheduler controls the scheduling via the VC backpressure messages it sends to the HRR scheduler. When the HRR scheduler receives a backpressure message from the SAR scheduler, the HRR scheduler disables the node regardless of the node weight or shaping rate. When the HRR scheduler receives a backpressure release, the scheduler node is reenabled.
NOTE: The default QoS profile for ATM (atm-default) contains the atm-vc node command, which creates the scheduler node that is required by the 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.
154
Figure 43 on page 155 shows the HRR and SAR schedulers working together to form the integrated scheduler. When the SAR VC queues start to back up, the SAR exerts VC backpressure to the corresponding VC node in the HRR scheduler. VC backpressure affects only VC nodes that are in the default traffic-class group. As a consequence, VC nodes that are in named traffic-class groups within the scheduler hierarchy are not affected by VC backpressure.
In a WAN field programmable gate array (FPGA), the backpressure to the IOA is generated from the system packet interface (SPI4) first-in, first-out (FIFO) queue buffers that are partially full. An intermediate FIFO exists between the SIO from the IOA and the SPI4 to the storage router accelerator (SRA) or Internet eXchange processor (IXP). The SRA on an ES2 10G line module is almost identical to the ES2 10G Uplink line module, with the exception that the ES2 10G LM contains an SRA, its associated memory, and a utility FPGA. When the intermediate FIFO becomes full to half its total capacity, it sets an overflow that stops transmission of packets to the SPI4 and waits for the next End of Packet (EOP) bit before sending the next packet. This mechanism sends an out-of-sequence bit to the SPI4. Therefore, the intermediate FIFO becomes full to half its total size always on systems that display SRA1 when the WAN status registers are read.
155
The FIFO buffer has been enlarged by 4 times its previous size. When the FIFO buffer is 5/8 full, backpressure is sent to the IOA. When the FIFO buffer is 3/4 full, an overflow is set, an error is sent and an EOP is generated before the stoppage of transmission of packets to the SPI4. This method of processing causes the interface to receive a valid protocol. The error registers in the WAN FPGA of ES2 10G ADV LMs are correctly adjusted with the error data widths of the V5 serial input/output (SIO) status registers.
VP Shaping
VP shaping can be performed either in the SAR or by using the QoS shaping application using QoS profiles. Configuring VP shaping in the SAR enables traffic to be sent out of the port at a rate that closely matches strict ATM contract rates. SAR VP shaping is configured for the physical port using the atm vp-tunnel command. Related Documentation
Integrating the HRR Scheduler and SAR Scheduler on page 156 Per-Packet Queuing on the SAR Scheduler Overview on page 157
Default integrated QoS port modeATM application controls the scheduling facilities of the SAR scheduler. Low-latency QoS port modeHRR scheduler controls the traffic rate. Low-CDV QoS port modeHRR scheduler and the SAR scheduler work together to schedule traffic.
Improper configuration of the two schedulers might create an inefficient scenario in which extra latency is introduced, or might cause the scheduler to underuse the link. To configure integration of the schedulers, use the qos-mode-port commands listed in Table 16 on page 156.
Backpressure
VC and port port port port
SAR Buffering
significant normal minimal minimal
Scheduling
SAR SAR and HRR HRR HRR
156
NOTE: For ERX7xx models, ERX14xx models, and the ERX310 router, the qos-mode-port commands are valid only for the major interface on port 0.
To properly integrate the schedulers, make sure that the HRR and the SAR schedulers shape packets at the same rate. If the HRR scheduler sends packets at a higher rate than the SAR scheduler shapes them, the SAR scheduler can become congested and block the entire port. To manage the integration of the HRR and the SAR schedulers:
1.
Specify the cell-based shaping mode. See Configuring the QoS Shaping Mode for ATM Interfaces on page 169.
2. 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 166.
3. Configure the QoS application to control the SAR schedulers operation. In this mode
you configure both schedulers using scheduler profiles and QoS profiles. The E Series router then ensures that VPs and VCs are shaped to the same rates in both schedulers.
NOTE: You can also use the QoS cell mode application with QoS parameters to manage the integration of HRR and SAR schedulers. Specifying the QoS cell mode application with the qos-parameter-define command enables you to configure a port with either frame or cell shaping mode and then configure the port for low-CDV port mode.
Related Documentation
For more information about scheduler profiles, see Scheduler Hierarchy Overview on page 45 For more information about configuring QoS profiles, see QoS Profile Overview on page 121 For more information about configuring QoS parameters, see QoS Parameter Overview on page 215
157
Default integrated modeThe ATM SAR scheduler does the scheduling. Both VC and port backpressure are enabled, and the HRR scheduler does minimal scheduling. The SAR scheduler performs significant buffering. Low-latency modeThe HRR scheduler does the scheduling. All QoS configurations are supported. VC backpressure is disabled, port backpressure is set as aggressive, and the SAR scheduler does minimal buffering. This mode enables the lowest latency for packets scheduled in the HRR scheduler with strict priority. Because the SAR scheduler is running with minimal buffering, there is no head-of-line blocking. Low-CDV modeThe HRR and SAR schedulers both perform scheduling; QoS synchronizes the rates of the two schedulers. All QoS configurations are supported. VC backpressure is disabled, and port backpressure is set to the default thresholds of 6 MB per OC3 port and 24 MB per OC12 port. In this mode, you can configure shaping in both the 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.
The QoS shaping mode you set with the qos-shaping-mode command on port 0 and on the specific port The port queuing mode you set with the qos-mode-port command on port 0
158
The router uses the following rules to determine the operational shaping mode used for a port:
1.
If the specific port has a QoS shaping mode configured, the operational shaping mode for that port is the same as the QoS shaping mode.
2. If the specific port has no QoS shaping mode configured, the operational shaping
mode is the same as the QoS shaping mode for port 0, if one is configured.
3. If both the specific port and port 0 have no QoS shaping mode configured, the
operational shaping mode is based on the port 0 queuing mode. If the port 0 queuing mode (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 159 lists the possible combinations of the two commands and the resultant operational shaping mode.
Table 17: Operational Shaping Modes for ERX7xx Models, ERX14xx Models, and the ERX310 Router
Operational Shaping Mode for the Specific Port
Cell Frame Cell Frame Cell Frame
Rule
Rule 1
Rule 2
Rule 3
The QoS shaping mode you set with the qos-shaping-mode command on port 0 and on the specific port The port queuing mode you set with the qos-mode-port command on port 0 and on the specific port
The E120 and E320 routers use the following rules to determine the operational shaping mode used for a port:
159
1.
If the specific port has a QoS shaping mode configured, the operational shaping mode for that port is the same as the QoS shaping mode.
2. If the specific port has no QoS shaping mode and a port queuing mode of low-cdv
operational shaping mode for that port is the same as the port 0 QoS shaping mode.
4. If both the specific port and port 0 have no QoS shaping mode configured, the
operational shaping mode is based on the port 0 queuing mode. If the port 0 queuing mode (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 160 lists the possible combinations of the two commands and the resultant operational shaping mode.
Table 18: Operational Shaping Modes for the E120 Router and E320 Router
Operational Shaping Mode for Specific Port
Cell Frame
Rule
Rule 1
Rule 2 Rule 3
No shaping mode
Any
Any
Cell
No shaping mode
Frame
Any
Frame
No shaping mode
Cell
Any
Cell
Rule 4
No shaping mode
No shaping mode
low-cdv
Cell
No shaping mode
No shaping mode
low-latency or none
Frame
Related Documentation
Guidelines for Configuring QoS over ATM on page 161 Configuring Default Integrated Mode for ATM Interface on page 162 Configuring Low-Latency Mode for Per-Port Queuing on ATM Interfaces on page 164 Configuring Low-CDV Mode for Per-Port Queuing on ATM Interfaces on page 166 Configuring the QoS Shaping Mode for ATM Interfaces on page 169
160
NOTE: These rules apply only to the default integrated mode. VC backpressure is disabled in low-latency or low-cdv modes. You must account for cell tax; to do this, use the qos-shaping-mode cell command for the line module.
Use external admission control to guarantee that the sum of non-backpressured traffic into the VC is less than the SAR shaping rate for the VC. Shape the non-backpressured queues or nodes in the HRR, making the aggregate of the non-backpressured traffic for a VC less than the VC rate. In JunosE Release 6.0 and later, you can configure a shared shaper on the ATM VC node in the default traffic class group. Configure the shared-shaping rate to be less than or equal to the VC shaping rate in the SAR. Special rules apply for VP tunnels shaped in the SAR. When shaping in the SAR, configure ATM VP nodes in the HRR, and arrange that the aggregate traffic dequeued from the HRR for that vp-tunnel is less than or equal to the VP tunnel shaping rate in the SAR. Use one of the following two techniques for VP tunnels shaped in the SAR:
Partition the SAR VP tunnel bandwidth across the ATM VP nodes in the different traffic class groups in the HRR. For example, using a 4 Mbps VP tunnel, allocate 1 Mbps for the ATM VP node in the default traffic class group, 2 Mbps for the ATM VP
161
node in the video traffic class group, and 1 Mbps for the ATM VP node in the voice traffic class group. When using this technique, keep in mind that the different traffic classes cannot share bandwidth.
In JunosE Release 6.1 and later, using the EFA2 ASIC, you can configure shared shaping on the ATM VP nodes in the HRR to perform bandwidth sharing.
Related Documentation
Integrating the HRR Scheduler and SAR Scheduler on page 156 Shared Shaping and Low-CDV Mode on page 71 Configuring Default Integrated Mode for ATM Interface on page 162 Configuring Low-Latency Mode for Per-Port Queuing on ATM Interfaces on page 164 Configuring Low-CDV Mode for Per-Port Queuing on ATM Interfaces on page 166 Configuring the QoS Shaping Mode for ATM Interfaces on page 169
162
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.
TIP: Configuring an ATM VP tunnel sets a shaping rate in the SAR scheduler. Before configuring an ATM VP tunnel, there must be no PVCs with the same VPI that you are about to configure. Before using the atm vp-tunnel command, remove any PVCs from the configuration. You can reconfigure the PVCs after configuring the shapeless VP tunnel.
163
Related Documentation
Per-Packet Queuing on the SAR Scheduler Overview on page 157 Guidelines for Configuring QoS over ATM on page 161 atm vp-tunnel interface atm qos-mode-port
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 164.
164
host1(config)#qos-profile low-latency-q-p host1(config-qos-profile)#atm-vc node host1(config-qos-profile)#atm-vc queue traffic-class best-effort host1(config-qos-profile)#atm group strict scheduler-profile strict host1(config-qos-profile)#atm-vc queue traffic-class strict host1(config-qos-profile)#exit
5. From the desired port, set the QoS port mode to low latency.
TIP: For ATM interfaces on ERX7xx models, ERX14xx models, and the ERX310 router, you must specify port 0.
Excludes non-UBR ATM QoS services on any VC on the ATM module; for example, PCR, nrtVBR, and CBR Cannot be used if shaping is currently configured on the SAR scheduler Cannot be used with ATM VP tunnels with nonzero rates; however, can be used with tunnels with rates of zero (shapeless tunnels).
Related Documentation
Per-Packet Queuing on the SAR Scheduler Overview on page 157 Guidelines for Configuring QoS over ATM on page 161 interface atm qos-mode-port qos-profile
165
QoS synchronizes the shaping rates for VPs and VCs in the HRR and SAR schedulers. VC backpressure is disabled. Port backpressure is set to default thresholds of 6 MB per OC3 port and 24 MB per OC12 port. 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 166. Figure 47 on page 167 shows low-CDV mode with per-VC CDVT.
166
host1(config)#scheduler-profile strict host1(config-scheduler-profile)#strict-priority host1(config-scheduler-profile)#exit host1(config)#scheduler-profile 500k host1(config-scheduler-profile)#shaping-rate 500000 host1(config-scheduler-profile)#exit host1(config)#scheduler-profile 1m host1(config-scheduler-profile)#shaping-rate 1000000 host1(config-scheduler-profile)#exit host1(config)#scheduler-profile 2m host1(config-scheduler-profile)#shaping-rate 2000000
167
host1(config-scheduler-profile)#exit
4. Configure per-VC CDVT by configuring QoS profile with ATM VC queues.
host1(config)#qos-profile low-cdv-q-p host1(config-qos-profile)#atm-vc node scheduler-profile 1m host1(config-qos-profile)#atm-vp node scheduler-profile 2m host1(config-qos-profile)#atm-vc queue traffic-class best-effort host1(config-qos-profile)#atm group strict scheduler-profile strict host1(config-qos-profile)#atm-vc queue traffic-class strict scheduler-profile 500k host1(config-qos-profile)#exit
5. Configure per-VP CDVT using shapeless VP tunnels that are used when the QoS
application controls SAR scheduler shaping and set the QoS port mode to low CDV.
host1(config)#interface atm 2/0 host1(config-if)#atm vp-tunnel 0 0 host1(config-if)#atm vp-tunnel 1 0 host1(config-if)#qos-mode-port low-cdv host1(config-if)#qos-profile low-cdv-q-p host1(config-subif)#interface atm 2/0.5 host1(config-subif)#atm pvc 5 0 5 aal5snap host1(config-subif)#interface atm 2/0.6 host1(config-subif)#atm pvc 6 0 6 aal5snap host1(config-subif)#interface atm 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. Configuring an ATM VP tunnel sets a shaping rate in the SAR scheduler. Before configuring an ATM VP tunnel, there must be no PVCs with the same VPI that you are about to configure. Before using the atm vp-tunnel command, remove any PVCs from the configuration. You can reconfigure the PVCs after configuring the shapeless VP tunnel.
Excludes non-UBR ATM QoS services on any VC on the ATM module; for example, PCR, nrtVBR, and CBR Cannot be used if shaping is currently configured on the SAR scheduler Cannot be used with ATM VP tunnels with nonzero rates; however, can be used with tunnels with rates of zero (shapeless tunnels)
Related Documentation
Per-Packet Queuing on the SAR Scheduler Overview on page 157 Guidelines for Configuring QoS over ATM on page 161 atm vp-tunnel interface atm
168
qos-mode-port
NOTE: For ATM interfaces on ERX7xx models, ERX14xx models, and the ERX310 router, you must use port 0.
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.
Related Documentation
Per-Packet Queuing on the SAR Scheduler Overview on page 157 interface atm qos-mode-port qos-shaping-mode
169
1.
Specify the ATM interface for which you want to disable per-port queuing.
host1(config)#interface atm 2/0
host1(config-if)#no qos-mode-port
Related Documentation
Configuring Default Integrated Mode for ATM Interface on page 162 interface atm qos-mode-port
Monitoring the QoS Configuration of ATM Interfaces on page 328 Monitoring the QoS Configuration of IP Interfaces on page 330 Monitoring the QoS Profiles Attached to an Interface on page 324 Monitoring the Configuration of QoS Port-Type Profiles on page 325 Monitoring the Configuration of QoS Profiles on page 325 Monitoring the QoS Scheduler Hierarchy on page 307 Monitoring Shared Shapers on page 314
170
CHAPTER 20
Providing QoS for Ethernet Overview on page 171 QoS Shaping Mode for Ethernet Interfaces Overview on page 172 Configuring the QoS Shaping Mode for Ethernet Interfaces on page 173 Creating a QoS Interface Hierarchy for Bulk-Configured VLAN Subinterfaces with RADIUS on page 174 Monitoring QoS Configurations for Ethernet on page 176
QoS Shaping Mode for Ethernet Interfaces Overview on page 172 Creating a QoS Interface Hierarchy for Bulk-Configured VLAN Subinterfaces with RADIUS on page 174 To configure subscriber-based QoS for 802.3ad link aggregation interfaces, see QoS for 802.3ad Link Aggregation Interfaces Overview on page 177
171
Gigabit Ethernet interfaces on the GE-2 line module and the GE-HDE line module on ERX routers Gigabit Ethernet and 10-Gigabit Ethernet interfaces on the ES2 4G LM on E120 and E320 Broadband Services routers 10-Gigabit Ethernet interfaces on the ES2 10G LM on E120 and E320 routers
When you use cell shaping mode to configure the shaping or policing rate, the resulting traffic stream conforms exactly to the policing rates configured in downstream ATM switches. Using cell shaping also reduces the number of packet drops in the Ethernet network. The setting for port 0 provides the default shaping mode for all ports on the same I/O module or IOA. Individual ports can have a specific shaping mode setting that overrides the setting for port 0. If you do not configure the QoS shaping mode for a port, the shaping mode is calculated using the value for port 0 on the same I/O module or IOA. If the port's shaping mode is configured, the system uses the port's shaping mode. Table 19 on page 172 lists the possible combinations of the qos-shaping-mode command and the resultant operational shaping mode.
172
Chapter 20: Configuring QoS for Gigabit Ethernet Interfaces and VLAN Subinterfaces
To account for different layer 2 encapsulations, you can configure the byte adjustment application using QoS parameters. The byte adjustment is calculated differently for frame shaping mode than cell shaping mode.
NOTE: You can also use the QoS cell mode application with QoS parameters to configure the shaping mode for a port.
Related Documentation
Configuring the QoS Shaping Mode for Ethernet Interfaces on page 173 Byte Adjustment for ADSL and VDSL Traffic Overview on page 279 Cell Shaping Mode Using QoS Parameters Overview on page 269
host1(config)#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.
Related Documentation
QoS Shaping Mode for Ethernet Interfaces Overview on page 172 interface gigabitEthernet qos-shaping-mode
173
Creating a QoS Interface Hierarchy for Bulk-Configured VLAN Subinterfaces with RADIUS
Bulk-configured VLAN subinterfaces are created dynamically, so you cannot apply a QoS profile directly to a VLAN subinterface. Instead, you can use subscriber service profiles and RADIUS to apply QoS profiles. To create an interface hierarchy for bulk-configured VLAN subinterfaces:
1.
2. Configure the profiles and service profile for the bulk-configured VLAN subinterfaces
TIP: Configure the service profile in the default virtual router or the virtual router in which RADIUS is configured.
4. Access the RADIUS server and assign values for the RADIUS attributes necessary for
creating a QoS interface hierarchy, including the QoS profile name. For example:
Juniper VSA Qos-Profile-Name [26-26]QoS profile name (Optional) Juniper VSA Virtual-Router [26-1]Virtual router name (Optional) IETF VSA [22]Framed-Route
The highlighted output from this debug log message shows the QoS profile, virtual router, and framed route attributes configured through RADIUS.
174
Chapter 20: Configuring QoS for Gigabit Ethernet Interfaces and VLAN Subinterfaces
DEBUG 06/17/2007 14:50:19 radiusSendAttributes: ACCESS-REQUEST attributes (default) DEBUG 06/17/2007 14:50:19 radiusSendAttributes: username attr added: vlan@test DEBUG 06/17/2007 14:50:19 radiusSendAttributes: acct-session-id attr added: erx GigabitEthernet 2/1.100:100:0004194348 DE BUG 06/17/2007 14:50:19 radiusSendAttributes: user-password attr added: <value withheld> DEBUG 06/17/2007 14:50:19 radiusSendAttributes: calling-station-id attr added: #ananke#E21#100 DEBUG 06/17/2007 14:50:19 radiusSendAttributes: nas-port-type attr added:15 DEBUG 06/17/2007 14:50:19 radiusSendAttributes: nas-port attr added: 553648228 DEBUG 06/17/2007 14:50:19 radiusSendAttributes: nas-port-id attr added: GigabitEthernet 2/1.100:100 DEBUG 06/17/2007 14:50:19 radiusSendAttributes: nas-ip-address attr added: 172.26.27.50 DEBUG 06/17/2007 14:50:19 radiusSendAttributes: nas-identifier attr added: ananke DEBUG 06/17/2007 14:50:19 radiusAttributes: USER ATTRIBUTES: (vlan@test) DEBUG 06/17/2007 14:50:19 radiusAttributes: class attr: (binary data) DEBUG 06/17/2007 14:50:19 radiusAttributes: total eap message attr length = 0 DEBUG 06/17/2007 14:50:19 radiusAttributes: framed route attr: 40.40.41.0/30 0.0.0.0 DEBUG 06/17/2007 14:50:19 radiusAttributes: ingress policy name (vsa) attr: test DEBUG 06/17/2007 14:50:19 radiusAttributes: ingress policy stats (vsa) attr: 1 DEBUG 06/17/2007 14:50:19 radiusAttributes: egress policy name (vsa) attr: test DEBUG 06/17/2007 14:50:19 radiusAttributes: egress policy stats (vsa) attr: 1 DEBUG 06/17/2007 14:50:19 radiusAttributes: qos profile name (vsa) attr: test DEBUG 06/17/2007 14:50:19 radiusAttributes: virtual router name (vsa) attr: server 6. Verify that the interface was created in the default virtual router. host1:server# show ip interface brief Interface IP-Address Status Protocol -------------------- ---------------------------- ---------null0 255.255.255.255/32 up up loopback0 10.1.0.1/24 up up GigabitEthernet6/0.100 Unnumbered up up 7. Verify that the framed route is installed. host1:server# show ip route Prefix/Length Type Next Hop Dst/Met Interface ------------------ --------- --------------- ---------- ----------------------10.1.0.0/24 Connect 10.1.0.1 0/0 loopback0 40.40.41.0/30 Access 0.0.0.0 3/2 GigabitEthernet6/0/0.100
Description -------------
TIP: When you initially create the user record for dynamic IP interfaces using VSA [22], you might not know the next hop. In this case, specify the value 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.
8. Verify that the correct QoS profile is attached to the VLAN subinterface. host1:server#show qos interface-hierarchy interface gigabitEthernet 6/0/0.100 attachment@ ip GigabitEthernet6/0/0.100: t-class interface rule traffic scheduler
queue
qos profile group type type class profile profile ------------------------ ------- --------- ----- ------- --------- -------test@GigabitEthernet6/0/0.100 vlan node default default
175
Related Documentation
For information about bulk-configured VLAN subinterfaces, see JunosE Link Layer Configuration Guide For information about service profiles, see JunosE Broadband Access Configuration Guide For information about RADIUS VSAs, see JunosE Broadband Access Configuration Guide auto-configure vlan encapsulation vlan interface gigabitEthernet ip service-profile profile profile vlan bulk-config vlan auto-configure vlan bulk-config vlan profile vlan service-profile show ip interface show ip route show qos interface-hierarchy
Monitoring the QoS Configuration of Fast Ethernet, Gigabit Ethernet, and 10-Gigabit Ethernet Interfaces on page 332 Monitoring the QoS Configuration of IP Interfaces on page 330 Monitoring the QoS Profiles Attached to an Interface on page 324 Monitoring the Configuration of QoS Port-Type Profiles on page 325 Monitoring the Configuration of QoS Profiles on page 325 Monitoring the QoS Scheduler Hierarchy on page 307 Monitoring Shared Shapers on page 314
176
CHAPTER 21
QoS for 802.3ad Link Aggregation Interfaces Overview on page 177 Hashed Load Balancing for 802.3ad Link Aggregation Groups Overview on page 179 Subscriber Load Balancing for 802.3ad Link Aggregation Groups Overview on page 180 Guidelines for Configuring QoS over 802.3ad Link Aggregation Groups on page 183 Configuring the Scheduler Hierarchy for Hashed Load Balancing in 802.3ad Link Aggregation Groups on page 184 Enabling Default Subscriber Load Balancing for 802.3ad Link Aggregation Groups on page 185 Configuring the Scheduler Hierarchy for Subscriber Load Balancing in 802.3ad Link Aggregation Groups on page 185 Configuring Load Rebalancing for 802.3ad Link Aggregation Groups on page 186 Monitoring QoS Configurations for 802.3ad Link Aggregation Groups on page 188
177
demultiplexes each packet to an active link based on the subinterface underlying the egress interface. For example, when an IP packet is routed to an IP interface over a LAG, the system binds the underlying VLAN, PPPoE, or MPLS subinterface to one of the active links in the LAG. The packet is transmitted over the interface. Most network operators configure QoS over 802.3ad LAGs using subscriber load balancing to take advantage of subscriber class-based queueing (SCBQ) features. However, configuring hashed load balancing is useful for achieving fine-grained distribution of multicast VLAN traffic or for any high bandwidth VLAN that does not require shared shaping. To ensure that QoS is symmetrically applied to all the links, the router periodically rebalances the traffic on the LAG. You can control the loadbalancing parameters.
Attachment 1QoS profile attached to the VLAN Attachment 2QoS profile attached to the S-VLAN Attachment 3QoS profile attached to the LAG
If there is no QoS profile attached to the LAG, the system locates the lag-default QoS profile indicated in the qos-port-type-profile command. If the resulting QoS profile specifies only Ethernet queues, the system uses the hash algorithm to balance the links. If the resulting QoS profile specifies any VLAN, IP, or L2TP-Session queues, then the system uses subscriber load balancing.
178
Hashed Load Balancing for 802.3ad Link Aggregation Groups Overview on page 179 Subscriber Load Balancing for 802.3ad Link Aggregation Groups Overview on page 180 For more information about configuring the lag-default QoS profile for default subscriber load balancing, see Enabling Default Subscriber Load Balancing for 802.3ad Link Aggregation Groups on page 185 For more information about Ethernet link redundancy, see JunosE Link Layer Configuration Guide For more information about configuring QoS parameters, see Parameter Definition Attributes for QoS Administrators Overview on page 219 For more information about the munge algorithm, see Munged QoS Profile Overview on page 131 For a list of modules that support 802.3ad link aggregation, see the ERX Module Guide and the E120 and E320 Module Guide
179
shares the traffic equally across the links based on the distribution characteristics defined in the hash algorithm. Because all traffic is carried in Ethernet queues, per-subscriber QoS features such as shared shaping for VLANs are not available.
180
within the LAG. S-VLAN nodes and queues are the only resources that are cloned; the system always allocates nodes and queues for other interface types to a single selected link. Cloning S-VLAN nodes enables fine-grained load balancing within the LAG because VLANs within the S-VLAN can be allocated to the link with the least traffic. However, cloned S-VLANs can introduce anomalous scheduling behavior. A shaped S-VLAN node within the LAG shapes traffic on a per-link basis. Shaping a LAG S-VLAN node to 2 Mbps on a LAG with 2 links can enable up to 4 Mbps of traffic (2 Mbps per link). Shared shaping on an S-VLAN within a LAG has the same behavior; the LAG S-VLAN that is shared shaped to 10 Mbps on a LAG with 2 ports allows up to 20Mbps of traffic; 10 Mbps for each link.
181
182
In an ideal QoS configuration, queues and nodes are stacked over a single port that corresponds to a LAG, with the port bandwidth equal to the sum of the overall port bandwidth. However, the actual LAG behavior is different. No level 1 node or queue can exceed the bandwidth of a link. The relative weighting of queues and nodes results in proportional bandwidth allocation only within a link, but not across the entire LAG. Actual traffic might not be evenly balanced across links in the LAG, resulting in latency and loss on one link, while another link may be lightly loaded. Even though relative weighting is different on a LAG, shaping and shared shaping in the partitioned scheduler hierarchy operate in the same way as a typical Ethernet configuration. Related Documentation
For more information about load rebalancing, see Configuring Load Rebalancing for 802.3ad Link Aggregation Groups on page 186
QoS profiles cannot be attached to Ethernet ports if the port is a member of a LAG. In typical QoS configurations, the Ethernet interface is considered the root of the interface hierarchy. When you configure QoS for 802.3ad link aggregation, the LAG interface is considered the root of the interface hierarchy. You cannot configure hierarchical QoS for IP configured directly over a LAG interface. You cannot obtain QoS information or statistics for IP interfaces stacked over a LAG interface using any of the show commands for QoS. Instead, the show qos scheduler-hierarchy command is designed to find the interface hierarchy rooted at the specified interface and report all scheduler nodes and queues managed by those interfaces. The typical defaults in QoS profiles such as ethernet-default and atm-default
183
specify the "ip queue traffic-class best-effort" rule, so those queues are reported in the interface hierarchy. The lag-default QoS profile does not specify this rule by default.
Do not attach QoS profiles to IP or VLAN subinterfaces in a LAG that contain downreferences (that is, rules for S-VLAN or Ethernet nodes or queues). QoS profiles attached at subinterfaces above a LAG that also include downreference create an asymmetric scheduler hierarchy. For example, one Ethernet port might be shaped and not another. Also, if the QoS profile specifies only Ethernet, then the traffic sent to the subinterface might be only partially affected by the QoS profile, or not at all. The traffic can be allocated to another port entirely.
Related Documentation
Subscriber Load Balancing for 802.3ad Link Aggregation Groups Overview on page 180 Configuring the Scheduler Hierarchy for Subscriber Load Balancing in 802.3ad Link Aggregation Groups on page 185 Configuring Load Rebalancing for 802.3ad Link Aggregation Groups on page 186
Configuring the Scheduler Hierarchy for Hashed Load Balancing in 802.3ad Link Aggregation Groups
The type of load balancing that the system performs depends on the configuration of the scheduler hierarchy in the QoS profile. To configure the scheduler hierarchy for hashed load balancing:
1.
host1(config-qos-profile)#ethernet queue traffic-class best-effort host1(config-qos-profile)#ethernet queue traffic-class tc1 host1(config-qos-profile)#ethernet queue traffic-class tc2
3. Create the LAG interface and attach the QoS profile.
Related Documentation
QoS for 802.3ad Link Aggregation Interfaces Overview on page 177 Hashed Load Balancing for 802.3ad Link Aggregation Groups Overview on page 179 interface lag node qos-profile queue
184
Enabling Default Subscriber Load Balancing for 802.3ad Link Aggregation Groups
The factory default contents of the lag-default QoS profile include an Ethernet queue and the best-effort traffic class. When you use the lag-default QoS profile, the system automatically sends traffic to the Ethernet queue and uses hash load balancing for the Ethernet queues. To enable subscriber load balancing as the default behavior for all LAGs, issue the following command:
host1(config)#qos-port-type-profile lag qos-profile ethernet-default
Related Documentation
QoS for 802.3ad Link Aggregation Interfaces Overview on page 177 qos-port-type-profile
Configuring the Scheduler Hierarchy for Subscriber Load Balancing in 802.3ad Link Aggregation Groups
The type of load balancing that the system performs depends on the configuration of the scheduler hierarchy in the QoS profile. To configure the scheduler hierarchy for subscriber load balancing:
1.
host1(config-qos-profile)#vlan queue traffic-class best-effort host1(config-qos-profile)#vlan queue traffic-class tc1 host1(config-qos-profile)#vlan node scheduler-profile subscriber host1(config-qos-profile)#svlan node scheduler-profile svlan host1(config-qos-profile)#svlan node group g1 scheduler-profile svlan
3. Create the LAG interface and assign member interfaces.
host1(config-if)#qos-profile subscriber-lag
Related Documentation
QoS for 802.3ad Link Aggregation Interfaces Overview on page 177 Subscriber Load Balancing for 802.3ad Link Aggregation Groups Overview on page 180 Enabling Default Subscriber Load Balancing for 802.3ad Link Aggregation Groups on page 185 interface lag
185
Configuring LoadRebalancing Parameters on page 186 Configuring the System to Dynamically Rebalance the LAG on page 187
host1(config-if)#load-rebalance period 120 start-threshold 20 percent stop-threshold 100 percent maximum-improvement 300
This example specifies that the system rebalance within 120 seconds, can accept imbalance in the LAG in the range 20100 percent, and can move 300 subscribers to other ports during that time. Table 20 on page 186 describes the load balancing algorithm parameters that you can configure.
Description
Specifies the time period for rebalancing. For example, a period of 120 specifies that rebalancing occurs once every 2 minutes.
186
Description
Specifies the amount of imbalance in the LAG that triggers the algorithm to start rebalancing. The default is 0 percent. Optionally, you can specify one of the following units of measure:
percentSpecifies that the amount of imbalance is measured as a percentage of the average load per link. The range is 0100 percent. For example, the average load per link in a LAG is 500. Specifying start-threshold 5 percent indicates that the algorithm rebalances any link that deviates from the average load per link by 25 (5 percent of 500).
subscribersSpecifies that the amount of imbalance is measured by the number of subscribers from the average subscriber count in the LAG. The range is 010000. For example, specifying start-threshold 20 subscribers indicates that the algorithm rebalances any link with a subscriber count that differs from the average subscriber count by more than 20.
stop-threshold
Specifies the amount of imbalance in the LAG that triggers the algorithm to stop rebalancing. The algorithm continues rebalancing until this value is reached. The default is 0 percent. Optionally, you can specify one of the following units of measure:
percentSpecifies that the amount of imbalance is measured as a percentage of the average load per link. The range is 0100 percent. For example, the average load per link in a LAG is 500. Specifying the stop-threshold 2 percent command indicates that the algorithm stops within 10 of 500 (2 percent of 500). In this case, the algorithm stops when the links are at 510 and 490.
subscribersSpecifies that the amount of imbalance is measured by the number of subscribers. The range is 010000. For example, specifying stop-threshold 100 subscribers indicates that the algorithm continues until each link in the LAG is within 100 subscribers of the average subscriber count.
maximumimprovement
Specifies the maximum number of links to rebalance in the LAG per period. The default is 100 percent. Optionally, you can specify one of the following units of measure:
percentSpecifies that the maximum number of links is measured as a percentage of the total links. The range is 0100 percent. For example, specifying maximum-improvement 1 percent indicates that the algorithm rebalances 10 links per period (1 percent of 1000).
subscribersSpecifies that the maximum number of links is measured by the number of subscribers. The range is 010000 subscribers. For example, specifying maximum-improvement 40 subscribers indicates that the algorithm rebalances 40 subscribers per period.
187
host1(config-if)#load-rebalance
Related Documentation
Configuring Load Rebalancing for 802.3ad Link Aggregation Groups on page 186 QoS for 802.3ad Link Aggregation Interfaces Overview on page 177 Enabling Default Subscriber Load Balancing for 802.3ad Link Aggregation Groups on page 185 Configuring the Scheduler Hierarchy for Subscriber Load Balancing in 802.3ad Link Aggregation Groups on page 185 interface lag load-rebalance
Monitoring the QoS Configuration of Fast Ethernet, Gigabit Ethernet, and 10-Gigabit Ethernet Interfaces on page 332 Monitoring the QoS Configuration of IEEE 802.3ad Link Aggregation Group Bundles on page 333 Monitoring the QoS Configuration of IP Interfaces on page 330 Monitoring the QoS Profiles Attached to an Interface on page 324 Monitoring the Configuration of QoS Port-Type Profiles on page 325 Monitoring the Configuration of QoS Profiles on page 325 Monitoring the QoS Scheduler Hierarchy on page 307 Monitoring Shared Shapers on page 314
188
CHAPTER 22
Providing QoS for L2TP Overview on page 189 Sample Scheduler Hierarchies for L2TP on page 189 Configuring QoS for an L2TP Session on page 191 Configuring QoS for Tunnel-Server Ports for L2TP LNS Sessions on page 194 QoS and L2TP TX Speed AVP 24 Overview on page 195 Monitoring QoS Configurations for L2TP on page 196
189
190
Related Documentation
191
-------- ------------ ----- ----------- --------- ------- ------- ---------l2tp-session queue best-effort default default default default
Configuring QoS for an L2TP LNS Session on page 192 Configuring QoS for an L2TP LAC Session on page 193
Configure the traffic classes. See Configuring Traffic Classes That Define Service Levels on page 14.
Configure the queuing hierarchy. See Configuring Queue Profiles to Manage Buffers and Thresholds on page 22.
Configure the scheduler hierarchy and shaping with scheduler profiles. See Configuring a Scheduler Hierarchy on page 47.
Remove the best-effort traffic class rule from the IP interface type of the server-default QoS profile.
host1(config)#qos-profile server-default host1(config-qos-profile)#no ip queue traffic-class best-effort host1(config-qos-profile)#exit
2. Create a traffic-class group, and enter Traffic Class Group Configuration mode. Add
Create the QoS profile, and enter QoS Profile Configuration mode.
host1(config)#qos-profile l2tpQpro25 host1(config-qos-profile)#
4. Attach the QoS profile to the interface on which you have configured L2TP.
192
traffic
scheduler queue
drop
statistics
class profile profile profile profile -------- --------- ------- ------- ---------default default default default default default
Configure traffic classes. See Configuring Traffic Classes That Define Service Levels on page 14.
Configure the queuing hierarchy. See Configuring Queue Profiles to Manage Buffers and Thresholds on page 22.
Configure the scheduler hierarchy and shaping with scheduler profiles. See Configuring a Scheduler Hierarchy on page 47.
Create the QoS profile, and enter QoS Profile Configuration mode.
host1(config)#qos-profile l2tpQpro25 host1(config-qos-profile)#
2. Attach the QoS profile to the interface on which you have configured L2TP.
193
host1(config)#show qos-profile l2tpQpro25 qos-profile l2tpQpro25: t-class interface rule group type -------- ---------
traffic
scheduler queue
drop
statistics
type class profile profile profile profile ----- --------- --------- ------- ------- ---------default default default default default default
Related Documentation
Supported Interface Types for QoS Profiles on page 125 Sample Scheduler Hierarchies for L2TP on page 189 group interface qos-profile queue scheduler-profile show qos-profile traffic-class
Configure the dedicated or shared tunnel-server port. See JunosE Physical Layer Configuration Guide.
NOTE: Dedicated and shared tunnel servers do not support QoS profiles on interfaces stacked on the server-port.
Configure the traffic classes. See Configuring Traffic Classes That Define Service Levels on page 14.
Configure the queuing hierarchy. See Configuring Queue Profiles to Manage Buffers and Thresholds on page 22.
Configure the scheduler hierarchy and shaping with scheduler profiles. See Configuring a Scheduler Hierarchy on page 47.
194
1.
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 host1(config-qos-profile)#ip queue traffic-class voice scheduler-profile voice queue-profile voice host1(config-qos-profile)#server-port group video host1(config-qos-profile)#server-port group data host1(config-qos-profile)#server-port group voice scheduler-profile strict-priority
3. Create and attach the QoS port-type profile for server ports.
Related Documentation
For more information about tunnel-server ports, see JunosE Physical Layer Configuration Guide group interface node qos-port-type-profile qos-profile queue scheduler-profile traffic-class tunnel-server
ATM 1483 subinterface over ATM VP over ATM interface PPPoE subinterface over Ethernet interface
195
For those logical interfaces with a rate controlled by QoS, QoS reports this configured rate as the transmit connect speed for that interface. For the logical interfaces that do not have a QoS-configured rate, QoS reports the speed of the underlying physical port as the transmit connect speed. 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 shaping rate or shared-shaping rate is determined as the result of a provider-specified arithmetic expression in a scheduler profile. This expression can either be a constant value, such as 1,000,000, or an expression using QoS parameters, with values supplied by RADIUS or statically in non-volatile storage (NVS). If the QoS profile or the QoS parameters are configured in RADIUS, these values are used in computing the rate at the time of login. The system can subsequently modify the value of parameters through change of authorization (CoA), Service Manager, or L2C. Modifications are not reflected in the rate QoS reports because they might take place after the LAC has sent the message that contains AVP 24.
Shaping Mode
When the QoS shaping mode is set to cell for an interface, QoS reports the ATM rate. In cell mode, user-specified rates account for cell headers and trailers, which are ATM native rates; therefore, QoS does not convert the rates for AVP 24. Related Documentation
For information about shared-shaping rates, see Simple Shared Shaping Overview on page 75 and Compound Shared Shaping Overview on page 95 For information about QoS parameters that are configured in RADIUS, see QoS Parameter Overview on page 215 For information about how to configure the transmit connect speed, see the JunosE Broadband Access Configuration Guide
Monitoring the QoS Configuration of Fast Ethernet, Gigabit Ethernet, and 10-Gigabit Ethernet Interfaces on page 332 Monitoring the QoS Configuration of IEEE 802.3ad Link Aggregation Group Bundles on page 333 Monitoring the QoS Configuration of IP Interfaces on page 330 Monitoring the QoS Profiles Attached to an Interface on page 324 Monitoring the Configuration of QoS Port-Type Profiles on page 325 Monitoring the Configuration of QoS Profiles on page 325
196
Monitoring the QoS Scheduler Hierarchy on page 307 Monitoring Shared Shapers on page 314
197
198
CHAPTER 23
Interface Sets for QoS Overview on page 199 Architecture of Interface Sets for QoS on page 200 Configuring Interface Sets for Scheduling and Queuing on page 203 Configuring Interface Supersets for QoS on page 204 Configuring Interface Sets for QoS on page 205 Adding Member Interfaces to an Interface Set on page 206 Creating a QoS Parameter on an Interface Superset or Interface Set on page 208 Attaching a QoS Profile to an Interface Superset or an Interface Set on page 209 Deleting an Interface Superset or an Interface Set on page 211 Example: Configuring Interface Sets for 802.3ad Link Aggregation Groups on page 212
199
Description
Set of logical interfaces of the same type: VLAN, ATM VC, and IP. An interface set shares a common parent interface. Set of QoS interface sets and logical interfaces of the same type. A superset shares a common parent interface. Logical interface associated with a set. All members of an interface set must be configured under this parent interface, or they cannot join an interface set. Interface set of VLAN subinterfaces. Interface superset that contains VLAN interface sets and VLAN subinterfaces, stacked over a common Ethernet major interface. Interface set of ATM 1483 subinterfaces. Interface set that is restricted to VLAN subinterfaces sharing a common VLAN ID. The parent of the interface set is an S-VLAN. The VLAN subinterfaces that are members of the interface set must have the same S-VLAN ID as the parent.
Interface superset
Parent interface
Interface set of VLAN subinterfaces that span S-VLANs. The parent of the interface set is an Ethernet major interface. The member VLAN subinterfaces can have different S-VLAN IDs.
Interface set that is restricted to ATM VC subinterfaces sharing a common VPI. The parent of the interface set is a VPI. The ATM VC subinterfaces that are members of the interface set must have the same VPI as the parent.
Interface set of ATM VC subinterfaces that span VPIs. The parent of the interface set is an ATM major interface. The member ATM VC subinterfaces can have different VPIs.
Related Documentation
Architecture of Interface Sets for QoS on page 200 Configuring Interface Sets for Scheduling and Queuing on page 203
200
When an interface is grouped in an interface set, the logical interface column is modified, and interface set appears below the interface in the column. The interface superset appears below the interface set. Although interface sets enable you to configure more types of scheduler nodes, the number of node and queue resources supported in the current scheduler hierarchy are the same.
201
Figure 58 on page 202 shows a scheduler hierarchy with VLAN nodes at the interface set.
Figure 58: Scheduler Hierarchy with Nodes at Interface Set and Superset
202
You can use QoS profiles and QoS parameters to manage the scheduling and shaping in the interface set. When you attach a QoS profile to an interface set or an interface superset, the QoS profile applies to all of the interfaces in the set and the superset. You can create parameter instances for an interface set or a superset by specifying the set or superset as a controlled-interface type and instance-interface type. Related Documentation
Interface Sets for QoS Overview on page 199 Configuring Interface Sets for Scheduling and Queuing on page 203 For more information about scheduler resources, see Managing System Resources for Nodes and Queues on page 121
Configure an interface superset. See Configuring Interface Supersets for QoS on page 204.
You can configure the scheduler hierarchy using one of the following methods:
Attach a QoS profile to an interface superset or an interface set. QoS profiles reference queue, drop, statistics, and scheduler profiles. See Attaching a QoS Profile to an Interface Superset or an Interface Set on page 209.
Create a QoS parameter instance on an interface superset or an interface set. QoS parameter instances enable you to configure shaping rates independent of the QoS profile and scheduler profile. See Creating a QoS Parameter on an Interface Superset or Interface Set on page 208.
See Monitoring the Configuration of QoS Interface Sets on page 334 and Monitoring the Configuration of QoS Interface Supersets on page 335. Related Documentation
203
Configuring an Interface Superset on page 204 Restricting an Interface Superset to an S-VLAN ID or an ATM VP on page 204
You can configure an Ethernet major interface, an ATM major interface, or a LAG for the parent interface. You must define the parent before you add interface sets or subinterfaces to the interface superset.
Related Documentation
To add members to the interface superset, see Configuring Interface Sets for QoS on page 205 Monitoring the Configuration of QoS Interface Supersets on page 335 qos-interface-superset qos-interface-parent
204
restricted
Configuring an Interface Set on page 205 Deleting an Interface Set from an Interface Superset on page 205
host1(config-interface-set)#qos-interface-parent vlan-superset
You can specify vlan, atm-vc, or ip for the member-interface type. If the parent interface superset is attached to an Ethernet major interface, the valid interface types are vlan and ip. If the parent interface superset is attached to an ATM major interface, the valid interface types are atm-vc or ip.
Related Documentation
For more information about configuring interface supersets, see Configuring Interface Supersets for QoS on page 204 Monitoring the Configuration of QoS Interface Sets on page 334 member-interface-type
205
Adding Interfaces to an Interface Set with the CLI on page 206 Adding Interfaces to an Interface Set with RADIUS on page 206 Changing and Deleting Interface Members in an Interface Set on page 207 Changing Interface Members with Upper-Layer Protocols in an Interface Set on page 207
Specify the VLAN or ATM-VC subinterface you want to add to the interface set. For VLAN subinterfaces:
host1(config)#interface gigabitEthernet 4/0/0.1
host1(config-sub-if)#qos-interface-parent residential-customers
The interface type must match the member-interface type specified in the interface set.
206
Leaving an interface set is not supported from RADIUS. The interface leaves an interface set when it is deleted or manually removed from the interface set through the CLI.
2. Delete the member interface from the subinterface using the no version of the
command.
host1(sub-if)#no qos-interface-parent vlan-business
3. Configure the new interface set for the member interface.
host1(sub-if)#qos-interface-parent vlan-residential
Instead of moving the member interface, we recommend that you add an interface member to an interface set at the subinterface rather than at the upper-layer binding. 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 Documentation
For more information about RADIUS VSAs, see the JunosE Broadband Access Configuration Guide qos-interface-parent
207
Configuring a QoS Parameter Definition for an Interface Superset or an Interface Set on page 208 Creating a QoS Parameter Instance for an Interface Superset on page 208 Creating a QoS Parameter Instance for an Interface Set on page 209
2. Configure the controlled-interface type and specify the interface set or the interface
superset.
host1(config-qos-parameter-define)#controlled-interface-type set host1(config-qos-parameter-define)#controlled-interface-type superset
You can specify up to four controlled-interface types for each parameter definition.
3. Configure the instance-interface type and specify the interface set or the interface
superset.
host1(config-qos-parameter-define)#instance-interface-type set host1(config-qos-parameter-define)#instance-interface-type superset
You can specify up to eight instance-interface types for each parameter definition.
host1(config-qos-interface-superset)#qos-parameter business-data
3. Attach the QoS profile.
host1(config-qos-interface-superset)#qos-profile vlan
208
host1(config-qos-interface-set)#qos-parameter business-data
3. Attach the QoS profile.
host1(config-qos-interface-set)#qos-profile vlan
Related Documentation
Monitoring the QoS Profiles Attached to an Interface on page 324 Monitoring the QoS Scheduler Hierarchy on page 307 Monitoring Shared Shapers on page 314 controlled-interface-type instance-interface-type qos-interface-set qos-interface-superset qos-parameter qos-profile
Configuring a QoS Profile for an Interface Superset or an Interface Set on page 209 Attaching a QoS Profile to an Interface Superset on page 210 Attaching a QoS Profile to an Interface Set on page 210
209
host1(config-qos-interface-superset)#qos-profile business-data
host1(config-qos-interface-set)#qos-profile business-data
Related Documentation
Monitoring the QoS Profiles Attached to an Interface on page 324 Monitoring the QoS Scheduler Hierarchy on page 307 Monitoring Shared Shapers on page 314 node qos-interface-set qos-interface-superset qos-profile queue
210
Deleting an Interface Superset on page 211 Deleting an Interface Set on page 211
Related Documentation
For more information about deleting an interface set from an interface superset, see Configuring Interface Supersets for QoS on page 204 For more information about deleting interface members of an interface set, see Configuring Interface Sets for QoS on page 205 qos-interface-parent qos-interface-set qos-interface-superset
211
Related Documentation
212
PART 6
QoS Parameter Overview on page 215 Configuring a QoS Parameter on page 219 Configuring Hierarchical QoS Parameters on page 249 Configuring IP Multicast Bandwidth Adjustment with QoS Parameters on page 257 Configuring the Shaping Mode for Ethernet with QoS Parameters on page 269 Configuring Byte Adjustment for Shaping Rates with QoS Parameters on page 279 Configuring the Downstream Rate Using QoS Parameters on page 287
213
214
CHAPTER 24
QoS Parameter Overview on page 215 QoS Parameter Audience on page 215 QoS Parameter Terms on page 216 Relationship Among QoS Parameters, Scheduler Profiles, and QoS Profiles on page 217
Shaping rate Shared-shaping rate Assured rate Scheduler weight QoS Parameter Audience on page 215 QoS Parameter Terms on page 216
Related Documentation
215
also configure parameter definitions that control the parameters, interfaces, and ranges of values that QoS clients, using QoS parameters, can assign. QoS clients are responsible for configuring services for individual subscribers by creating parameter instances. The parameter instances that QoS clients create depend on the settings that the QoS administrator defined in parameter definitions. QoS clients can use the CLI, Session and Resource Control (SRC), IP multicast bandwidth adjustment, RADIUS, or Service Manager to manage these services. Related Documentation
QoS Parameter Overview on page 215 Relationship Among QoS Parameters, Scheduler Profiles, and QoS Profiles on page 217
Description
QoS feature that controls a node or queue lower in the scheduler hierarchy. For example, a QoS profile that is attached to an ATM virtual circuit (ATM VC) modifies QoS settings on ATM virtual path (VP) nodes. You cannot configure downreferences for QoS parameters. We also recommend that you do not configure downreferences for QoS profiles. Hierarchical parameter instance whose value is explicitly specified by a client. This term is meaningful only when referring to hierarchical parameter instances; non-hierarchical parameter instances are always explicit. Parameter with both explicit instances that are configured by a QoS client, and with implicit instances that are automatically generated for all controlled interfaces. The value for the implicit instance is the sum of the explicit instances for interfaces stacked above the controlled interface. Hierarchical parameter instance where the value is the sum of explicit parameter instances on scheduler nodes and queues stacked above them in the scheduler hierarchy. Definition of a parameter name and attributes that a QoS administrator creates. Parameters used in conjunction with operators. Scheduler profiles reference a parameter definition name within a parameter expression. Parameter name and value that a QoS client associates with a logical interface. 32-byte unsigned integer value associated with a parameter instance.
Hierarchical parameter
Parameter definition
Parameter expression
Parameter instance
Parameter value
216
Description
Person responsible for implementing a QoS queuing architecture by configuring QoS profiles, scheduler profiles, and parameter definitions. Person responsible for configuring services for individual subscribers and setting rates for those services by using the parameter definitions and QoS profiles that the QoS administrator configures. QoS clients can use the CLI, SRC, Service Manager, IP multicast bandwidth adjustment, or RADIUS.
QoS client
Related Documentation
For definitions of other common QoS terms, see QoS Terms on page 5
Figure 59: Relationship of Parameter Definitions, Scheduler Profiles, and QoS Profiles
The following sections describe the steps displayed in Figure 59 on page 217, based on the tasks that the QoS administrator performs and those the QoS client performs.
The QoS administrator defines the attributes that the QoS client can modify by configuring a parameter definition.
2. The QoS administrator specifies the parameter definition name in a scheduler profile. 3. The QoS administrator references the scheduler profile in a QoS profile rule.
217
The QoS client creates a parameter instance and associates it with a logical interface.
Related Documentation
218
CHAPTER 25
Parameter Definition Attributes for QoS Administrators Overview on page 219 Scheduler Profiles and Parameter Expressions for QoS Administrators on page 225 Configuring a Basic Parameter Definition for QoS Administrators on page 227 Parameter Instances for QoS Clients Overview on page 229 Creating Parameter Instances on page 231 Example: QoS Parameter Configuration for Controlling Subscriber Bandwidth on page 232
Description
Name for the parameter. Interface types to which the QoS client can apply a parameter instance. The QoS administrator can specify up to eight instance-interface types for each parameter definition. 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.
Controlled-interface type
219
Description
Subscriber interfaces to which QoS clients can apply parameters obtained through RADIUS or profiles. The QoS administrator can specify up to four subscriber-interface types for each parameter definition. Valid range of values that a QoS client can specify. Boolean that indicates whether the parameter uses implicit parameter instances, which are the sum of explicit instances of the parameter on all scheduler nodes or queues above them in the scheduler hierarchy. Application that binds parameter instance to a specific application, such as IP multicast bandwidth adjustment.
Range Expression
Application
Description
Total bandwidth for a subscriber (average of all services) Shaping rate for a subscriber voice queue Assured rate for a priority-data service queue 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 221 lists examples of valid and invalid parameter names that use operators.
220
Invalid Names
1 1n + +foo min max
Parameter names are case-sensitive. For example, max-subscriber-bw and max-Subscriber-bw are different parameter names. Because the shaping rate and shared-shaping rates determine the maximum scheduler rates, and the assured rate determines minimum scheduler rates, we recommend that you use min or max operands in the parameter name.
Controlled-Interface Types
Controlled-interface types specify interface types for queues and scheduler nodes that a parameter instance can control. You can define up to four controlled-interface types for each parameter definition by issuing the controlled-interface-type command in QoS Parameter Definition Configuration mode. Examples of controlled interface types include atm-vp (ATM virtual paths), atm-vc (ATM virtual circuits), and VLAN (virtual LANs). For example, if you specify controlled-interface types of atm-vc and vlan, then you can use the parameter instance to shape or weight an ATM VC or VLAN node. However, because you did not specify ip, the system does not allow this parameter in a scheduler profile that was referenced in a QoS profile with an ip node (for example, ip node scheduler-profile test1). Controlled-Interface Type Example 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.
221
This scheduler profile can be referenced only by QoS profile VLAN rules. When a user attempts to reference the scheduler profile using rules other than VLAN, an error message is displayed. For example, a QoS profile rule cannot associate the scheduler profile with an atm-vc rule, as shown in the following example:
host1(config-qos-profile)#atm-vc queue traffic-class best-effort scheduler-profile subscriber % scheduler-profile parameter's controlled-interface-types(s) do not control this atm-vc qos-profile rule type
After you reference the parameter in a scheduler profile, you can reference the scheduler profile from a QoS profile. In this example, you configure a vlan node for each subscriber with a shared-shaping rate specified by the parameter max-subscriber-bandwidth.
host1(config)#qos-profile subscriber-triple-play host1(config-qos-profile)#vlan queue traffic-class best-effort scheduler-profile subscriber
Instance-Interface Types
After you configure at least one controlled-interface type, you configure one or more instance-interface types that specify the types of logical interfaces to which the QoS client can apply the parameter. You can define up to eight instance-interface types for each parameter definition by issuing the instance-interface-type command in QoS Parameter Definition Configuration mode. QoS clients cannot create a downreference for a parameter instance for instance-interface types that is above the lowest controlled-interface type of the same family in the interface stack.
NOTE: The guidelines are different for using instance-interface types with hierarchical parameters. For more information, see Scheduler Profiles and Parameter Expressions for QoS Administrators on page 225.
Instance-Interface Type Example In the following example, you configure a parameter definition with a controlled-interface type of 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
222
host1(config-qos-parameter-define)#instance-interface-type ethernet
In the scheduler hierarchy, IP is above VLANs. If you attempt to configure an instance-interface type for ip, an error message indicates that you cannot downreference IP from VLANs.
host1(config-qos-parameter-define)#instance-interface-type ip % instance-interface-type ip cannot stack above the lowest controlled-interface-type
Subscriber-Interface Types
Subscriber-interface types represent subscriber interfaces to which you can apply QoS parameters obtained through RADIUS or SRC. You can define up to four subscriber-interface types for each parameter definition by issuing the subscriber-interface-type command in QoS Parameter Definition Configuration mode. The following interface types are supported:
QoS clients cannot create a parameter instance for subscriber-interface types that is above the lowest controlled-interface type of the same family in the interface stack. If an interface profile contains a QoS parameter instance rule of max-subscriber-bandwidth 1000000, the system searches the logical interface column, starting at the top, and associates the parameter instance with the first interface with the subscriber-interface type that it locates. 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. Subscriber-Interface Type Example In the following example, you configure a parameter definition with a controlled-interface type and a subscriber-interface type of IP. These settings enable you to create QoS parameter VSAs on an IP interface.
host1(config)#qos-parameter-define max-subscriber-bandwidth host1(config-qos-parameter-define)#controlled-interface-type ip host1(config-qos-parameter-define)#instance-interface-type ip host1(config-qos-parameter-define)#subscriber-interface-type ip
223
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)#range 512000 8192000 host1(config-qos-parameter-define)#exit
If the QoS client attempts to configure values outside of this range, a message is displayed.
host1(config)#interface fastEthernet 9/0.1 host1(config-subif)#qos-parameter max-subscriber-bandwidth 1000000 host1(config-subif)#exit host1(config)#interface fastEthernet 9/0.1 host1(config-subif)#qos-parameter max-subscriber-bandwidth 200000 % parameter instance is out of range
You cannot create or modify an existing range if the change causes any explicit parameter instance values to be outside the valid range. For example:
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)#range 512000 8192000 host1(config-qos-parameter-define)#exit host1(config)#interface fastEthernet 9/0.1 host1(config-subif)# ! This parameter instance is within the range of 512Kbps to 8Mbps. host1(config-subif)#qos-parameter max-subscriber-bandwidth 1000000 host1(config-subif)#exit host1(config)#qos-parameter-define max-subscriber-bandwidth host1(config-qos-parameter-define)#range 2048000 8192000 % cannot modify a range when parameter instances exist with values outside the new range
NOTE: You can also define a range in parameter expressions when referencing a parameter within a scheduler profile. For more information, see Specifying a Range in Expressions on page 227.
IP Multicast Bandwidth Adjustment QoS Cell Mode Byte Adjustment (Cell and Frame) QoS Downstream Rate Configuring a Basic Parameter Definition for QoS Administrators on page 227 IP Multicast Bandwidth Adjustment for QoS Overview on page 257
Related Documentation
224
Cell Shaping Mode Using QoS Parameters Overview on page 269 Byte Adjustment for ADSL and VDSL Traffic Overview on page 279 QoS Downstream Rate Application Overview on page 287
When a scheduler profile references a parameter, the system implicitly assigns controlled-interface types to the scheduler profile that are the same as the controlled-interface types of all referenced parameters. The system validates scheduler profile types using the QoS profile rules that refer to those scheduler profiles. For example, if the parameter definition max-sub-bw has the controlled-interface types atm-vc and ip, the scheduler profile cannot be referenced in QoS profile rules that have a type other than atm-vc or ip.
225
Simple parameter expressions are displayed in the following example. Simple parameter expressions usually contain a constant rate or a single parameter name.
host1(config-scheduler-profile)#shaping-rate 10000000 host1(config-scheduler-profile)#shared-shaping-rate max-sub-bw auto host1(config-scheduler-profile)#shaping-rate max-sub-be-bw host1(config-scheduler-profile)#assured-rate assured-bw
More complicated parameter expressions are displayed in the following example. Complicated parameter expressions contain combinations of constant rates, parameter names, and operators.
host1(config-scheduler-profile)#shaping-rate max-sub-bw % 90 host1(config-scheduler-profile)#shared-shaping-rate max-data-bw + max-voice-bw + max-video-bw auto host1(config-scheduler-profile)#assured-rate min-data-bw % oversubscription-rate + min-video-bw % oversubscription-rate host1(config-scheduler-profile)#shared-shaping-rate 400000 - multicast-adjustment burst 100 milliseconds auto
Description
Percent in the range 1100
Precedence
1
Examples
max-subscriber-bw % 100 max-subscriber-bw % 10
* / +
1 1 2
Subtraction
min
Minimum
max
Maximum
226
Take the max of the subscriber-rate scheduler profile, or 1 Mbps, and name it x.
Example 1
The value of the subscriber-rate scheduler profile is less than 1 Mbps, specifically 500,000.
The max of 500K and1 Mbps is 1 Mbps The min of 1Mbps and 5 Mbps is 1 Mbps
ResultMade the subscriber-rate a minimum of 1 Mbps. Example 2 The value of the subscriber-rate scheduler profile is greater than 5 Mbps, specifically 6 Mbps.
The max of 6 Mbps and 1 Mbps is 6 Mbps The min of 6 Mbps and 5 Mbps is 5 Mbps
ResultMade the subscriber-rate a maximum of 5 Mbps. Example 3 The value of the subscriber-rate scheduler profile is within the range of 15 Mbps, specifically 3 Mbps.
The max of 3 Mbps and 1 Mbps is 3 Mbps The min of 3 Mbps and 5 Mbps is 3 Mbps
Related Documentation
Using Expressions for Bandwidth and Burst Values in a Scheduler Profile on page 48 Configuring a Basic Parameter Definition for QoS Administrators on page 227
227
Several of the following tasks are optional. Perform the required tasks and also any optional tasks that you need for your QoS parameter configuration. To configure a parameter definition:
1.
b. Specify the logical interface types for the nodes and queues controlled by this parameter.
host1(config-qos-parameter-define)#controlled-interface-type atm-vc host1(config-qos-parameter-define)#controlled-interface-type vlan
You can specify up to four of the following controlled-interface types per parameter definition: atm, atm-vc, atm-vp, bridge, ethernet, fr-vc, ip, ip-tunnel, ipv6, l2tp-session, l2tp-tunnel, lsp, pppoe, serial, server-port, vlan. c. Specify the set of logical interfaces types upon which a QoS client can create instances of the parameter.
host1(config-qos-parameter-define)#instance-interface-type atm-vc host1(config-qos-parameter-define)#instance-interface-type ip
You can specify up to four of the following controlled-interface types per parameter definition: atm, atm-vc, atm-vp, bridge, ethernet, fr-vc, ip, ip-tunnel, ipv6, lag, l2tp-session, l2tp-tunnel, lsp, pppoe, serial, server-port, svlan, vlan. d. (Optional) Specify the set of interface types that a QoS client can assign to a parameter instance to represent subscribers.
host1(config-qos-parameter-define)#subscriber-interface-type ip
You can specify up to four of the following subscriber-interface types: atm-vc, ip, ipv6, l2tp-session, vlan. e. (Optional) Define the range of values that a QoS client can assign to a parameter instance.
host1(config-qos-parameter-define)#range 64000 8000000
3. Reference the parameter within a scheduler profile parameter expression and configure
228
host1(config)#qos-profile subscriber host1(config-qos-profile)#atm-vc queue traffic-class business-data scheduler-profile business-data host1(config-qos-profile)#atm-vc queue traffic-class video scheduler-profile voice host1(config-qos-profile)#atm-vc queue traffic-class voice scheduler-profile video
Related Documentation
Parameter Definition Attributes for QoS Administrators Overview on page 219 Example: QoS Parameter Configuration for Controlling Subscriber Bandwidth on page 232 For more information about configuring a scheduler hierarchy with rates and weights, see Configuring a Scheduler Hierarchy on page 47 For more information about configuring a QoS profile, see Configuring a QoS Profile on page 126 assured-rate controlled-interface-type instance-interface-type node qos-parameter-define qos-profile queue range scheduler-profile shaping-rate shared-shaping-rate subscriber-interface-type traffic-class weight
229
When you create a parameter instance in Global Configuration mode, the value that you set for a rate becomes the default value for the router. We recommend that you create a global default value for a parameter instance to provide a minimal level of service by default for the router.
Parameter instances have hierarchical scope. The scope of a parameter instance is the set of logical interfaces stacked above the interface upon which you create it. Any interface stacked above the instance that is one of the controlled-interface types that are configured in the parameter definition can have its nodes or queues controlled by that instance. For example, a parameter named max-sub-bw might have logical interface types of IP and l2tp-session; therefore, it controls rates only for nodes and queues associated with those interface types. For example, the scope of a parameter instance at a S-VLAN can be all VLANs stacked above that particular S-VLAN. Scopes can overlap, for example, if a parameter instance is created for both an S-VLAN and a VLAN. The most specific instance overrides the other instances. However, you cannot configure QoS parameter instances to downreference through the interface stack. For example, you cannot create a parameter instance with an interface type of ATM VP on an ATM1483 subinterface. When you attach the parameter instance to an interface, it provides a default subscriber bandwidth for terminated and tunneled subscribers that terminate over that interface. To set parameter instances for a subscriber, a parameter instance is attached to a subscriber interface such as a vlan or atm-vc. The QoS administrator defines the available subscriber-interface types in the parameter definition. The parameter instance overrides the 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
230
behaves as if there is no shaping rate, shared-shaping rate, or assured rate for that node or queue. Related Documentation
Creating Parameter Instances on page 231 For more information about using global parameter instances for IP multicast bandwidth adjustment, see IP Multicast Bandwidth Adjustment for QoS Overview on page 257
Creating a Global Parameter Instance on page 231 Creating a Parameter Instance for an Interface on page 231 Creating a Parameter Instance for an ATM VP on page 231 Creating a Parameter Instance for an S-VLAN on page 232
Specify an interface.
host1(config)#interface atm 11/0.1 host1(config)#interface gigabitEthernet 2/0
231
Attach the parameter instance and associate with the QoS profile.
host1(config-if)#atm-vp 4 qos-profile video qos-parameter max-subscriber-bandwidth 375000
host1(config-if)#svlan id 1 202
3. Attach the parameter instance to an S-VLAN ID on the interface.
Related Documentation
Parameter Instances for QoS Clients Overview on page 229 For information about creating QoS parameter instances for Service Manager, see JunosE Broadband Access Configuration Guide atm-vp qos-parameter atm vp-tunnel encapsulation vlan interface qos-parameter svlan id svlan qos-parameter
232
The S-VLAN scheduler nodes correspond to the DSLAM in the physical network topology; the VLAN scheduler nodes correspond to the subscribers. Figure 61 on page 233 shows the QoS scheduler hierarchy that the QoS client creates when configuring a different service for each subscriber.
For Subscriber 1, the QoS client configures a basic best-effort data service, with a maximum rate of 2 Mbps, and assigns a scheduler weight value of 1. For Subscriber 2, the QoS client configures a basic triple-play service consisting of voice, video, and best-effort data services. This service enables the subscriber to transmit up to 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
233
subscriber to claim up to three times the bandwidth than the basic data service configured for Subscriber 1. For Subscriber 3, the QoS client configures an enhanced triple-play service consisting of voice, video and best-effort data services. This enhanced triple-play service enables the subscriber to transmit up to 8 Mbps of combined voice, video, and best-effort data traffic. This service limits video traffic to 3 Mbps and enables low-latency bandwidth for up to three 100 Kbps voice calls. The QoS client then assigns this subscriber a scheduler weight value of 6, enabling this subscriber to claim up to six times the bandwidth of the basic data service subscriber configured for Subscriber 1, and up to twice the bandwidth of the basic triple-play subscriber configured for Subscriber 2.
Configure the traffic classes. a. Configure the traffic class named best-effort. b. Configure the traffic class named video. c. Configure the traffic class named voice. d. Enable the voice traffic class to provide a strict priority treatment throughout the fabric.
host1(config)#traffic-class best-effort host1(config-traffic-class)#exit host1(config)#traffic-class video host1(config-traffic-class)#exit host1(config)#traffic-class voice host1(config-traffic-class)#fabric-strict-priority host1(config-traffic-class)#exit
2. Configure a traffic-class group for low-latency expedited forwarding (EF) and add
the voice traffic class into the traffic-class group EF. a. Configure the EF traffic-class group with strict-priority scheduling. b. Add the voice traffic class to the traffic-class group.
host1(config)#traffic-class-group EF auto-strict-priority host1(config-traffic-class-group)#traffic-class voice host1(config-traffic-class-group)#exit
The remaining traffic classes, best-effort and video, remain in the default traffic-class group.
234
After configuring the traffic classes and traffic-class groups, the QoS administrator configures the parameter definitions for Subscribers 1, 2, and 3.
1.
Configure a parameter definition for the maximum subscriber bandwidth. a. Configure the parameter definition named max-subscriber-bandwidth. b. Enable the parameter to control VLANs. c. Enable the parameter to have instances created on VLAN subinterfaces. d. Specify the valid range of this parameter as 512 Kbps8 Mbps.
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)#range 512000 8192000 host1(config-qos-parameter-define)#exit
round-robin (HRR) scheduler. This parameter is used to provide different scheduler weights for each of the three service offerings. a. Configure the parameter definition named subscriber-weight. b. Enable the parameter to control VLANs. c. Enable the parameter to have instances created on VLAN subinterfaces. d. Specify the valid range of this parameter as 16.
host1(config)#qos-parameter-define subscriber-weight host1(config-qos-parameter-define)#controlled-interface-type vlan host1(config-qos-parameter-define)#instance-interface-type vlan host1(config-qos-parameter-define)#range 1 6 host1(config-qos-parameter-define)#exit
3. Configure a parameter definition for the subscriber's maximum video bandwidth. By
creating a parameter instance on S-VLANs, the QoS administrator can specify a subscriber's maximum video bandwidth for each DSLAM in the hierarchy. a. Configure the parameter definition named max-subscriber-video-bandwidth. b. Enable the parameter to control VLANs. c. Enable the parameter to have instances created on both SVLAN and VLAN subinterfaces. d. Specify the valid range of this parameter as 1 Mbps5 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
235
host1(config-qos-parameter-define)#exit
4. Configure a parameter definition for the maximum number of 100 Kbps voice calls
supported for the subscriber. a. Configure the parameter definition named max-100Kbps-voice-calls. b. Enable the parameter to control VLANs. c. Enable the parameter to have instances created on VLAN subinterfaces. d. Specify the valid range of this parameter as 13.
host1(config)#qos-parameter-define max-100Kbps-voice-calls host1(config-qos-parameter-define)#controlled-interface-type vlan host1(config-qos-parameter-define)#instance-interface-type vlan host1(config-qos-parameter-define)#range 1 3 host1(config-qos-parameter-define)#exit
The QoS administrator can then reference the parameter definitions within a scheduler profile, which defines the shaping rates for the parameter.
1.
Configure a scheduler profile to specify the maximum bandwidth of the subscriber's best-effort data. a. Configure the scheduler profile named subscriber-best-effort. b. Configure the shared-shaping rate by referencing the max-subscriber-bandwidth parameter and choosing automatic shared shaping.
host1(config)#scheduler-profile subscriber-best-effort host1(config-scheduler-profile)#shared-shaping-rate max-subscriber-bandwidth auto host1(config-scheduler-profile)#exit
video service. a. Configure the scheduler profile named subscriber-video. b. Configure the shaping rate by referencing the max-subscriber-video-bandwidth parameter.
host1(config)#scheduler-profile subscriber-video host1(config-scheduler-profile)#shaping-rate max-subscriber-video-bandwidth host1(config-scheduler-profile)#exit
3. Configure a scheduler profile for the subscriber's weight within the HRR scheduler.
a. Configure the scheduler profile named subscriber-weight. b. Configure the weight using the default for the subscriber-weight parameter.
host1(config)#scheduler-profile subscriber-weight host1(config-scheduler-profile)#weight subscriber-weight host1(config-scheduler-profile)#exit
4. Configure a scheduler profile for the subscriber's voice service.
236
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.
host1(config)#scheduler-profile subscriber-voice host1(config-scheduler-profile)#shaping-rate max-100Kbps-voice-calls * 100000 host1(config-scheduler-profile)#exit
By referencing the scheduler profiles within QoS profiles, the QoS administrator creates the scheduler hierarchy. In this portion of the example, the QoS administrator configures QoS profiles for the best-effort data and triple-play service offerings.
1.
Define a QoS profile for the best-effort data service. a. Create the QoS profile named subscriber-data-service. b. Create a node for S-VLAN subinterfaces. c. Specify a node for VLAN subinterfaces and reference the subscriber-weight scheduler profile. d. Specify a queue for VLAN subinterfaces, referencing the best-effort traffic class and the subscriber-best-effort scheduler-profile.
host1(config)#qos-profile subscriber-data-service host1(config-qos-profile)#svlan node host1(config-qos-profile)#vlan node scheduler-profile subscriber-weight host1(config-qos-profile)#vlan queue traffic-class best-effort scheduler-profile subscriber-best-effort host1(config-qos-profile)#exit
The best-effort queue rule for VLAN subinterfaces refers to the subscriber-best-effort scheduler profile. The scheduler profile refers to the max-subscriber-bandwidth parameter that controls the maximum rate of this subscriber's best-effort queue.
2. Define a QoS profile for the triple-play service and specify S-VLAN nodes and VLAN
nodes. a. Create a QoS profile named subscriber-triple-play. b. Specify a node for S-VLAN subinterfaces. c. Specify a node for VLAN subinterfaces and reference the subscriber-weight scheduler profile. d. Specify a node for S-VLAN subinterfaces and reference the EF traffic-class group. e. Specify a queue for VLAN subinterfaces, referencing the best-effort traffic class and the subscriber-best-effort scheduler profile. f. Specify a queue for VLAN subinterfaces, referencing the video traffic class and the subscriber-video scheduler profile.
237
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 host1(config-qos-profile)#svlan node group EF host1(config-qos-profile)#vlan queue traffic-class best-effort scheduler-profile subscriber-best-effort host1(config-qos-profile)#vlan queue traffic-class video scheduler-profile subscriber-video host1(config-qos-profile)#vlan queue traffic-class voice scheduler-profile subscriber-voice host1(config-qos-profile)#exit
VLAN queues are used for each service. The VLAN queue rules reference scheduler profiles that define the scheduler rates for the service.
3. Configure a QoS profile and attach to all Fast Ethernet, Gigabit Ethernet, and 10-Gigabit
Ethernet interfaces in the chassis. a. Create a QoS profile named ethernet-default. b. Remove the QoS profile rule for creating IP nodes. c. Remove the IP queue for the best-effort traffic-class.
host1(config)#qos-profile ethernet-default host1(config-qos-profile)#no ip node host1(config-qos-profile)#no ip queue traffic-class best-effort host1(config-qos-profile)#exit
4. Configure the Fast Ethernet interface and VLAN subinterfaces.
a. Configure the Fast Ethernet interface in slot 9, port 0. b. Configure the VLAN major interface. c. Configure the VLAN subinterface at slot 9, port 0, subinterface 1. d. Assign an S-VLAN ID of 2 and a VLAN ID of 1 to the VLAN subinterface. e. Assign an IP address to the VLAN subinterface. f. Repeat Steps ae to configure VLAN subinterfaces in slot 9, port 0, subinterface 2 and in slot 9, port 0, subinterface 3.
host1(config)# interface fastEthernet 9/0 host1(config-if)#encapsulation vlan host1(config-if)#exit host1(config)#interface fastEthernet 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
238
2. Create a global parameter instance for subscriber-weight with a value of 1. 3. Create a global parameter instance for subscriber-video-bandwidth with a value of
2000000.
4. Create a global parameter instance for max-100Kbps-voice-calls with a value of 1.
host1(config)#qos-parameter max-subscriber-bandwidth 2000000 host1(config)#qos-parameter subscriber-weight 1 host1(config)#qos-parameter max-subscriber-video-bandwidth 2000000 host1(config)#qos-parameter max-100Kbps-voice-calls 1
Instead of creating global parameter instances, the QoS client can create different parameter instances for the DSLAMs that correspond to the S-VLAN nodes shown in Figure 61 on page 233. In this portion of the example, the QoS client creates 1 Mbps video streams by default on DSLAM 1, rather than the 2Mbps global parameter instance.
1.
Configure the basic-data service for Subscriber 1. a. Specify the Fast Ethernet interface in slot 9, port 0. b. Attach the QoS profile subscriber-data-service to the subscribers Fast Ethernet interface.
host1(config)#interface fastEthernet 9/0.1 host1(config-subif)#qos-profile subscriber-data-service
239
host1(config-subif)#exit
This QoS profile references the scheduler profiles, which then reference the parameter instances max-subscriber-bandwidth and subscriber-weight. These global parameter instances are created with values 2 Mbps and 1.
2. Configure a basic triple-play service consisting of voice, video, and data services for
Subscriber 2. a. Specify the Fast Ethernet interface in slot 9, port 0. b. Create a parameter instance for max-subscriber-bandwidth, enabling the subscriber to transmit up to 6 Mbps of combined voice, video, and data traffic. c. Create a parameter instance for subscriber-weight with a value of 3. This value enables the subscriber to claim up to three times the bandwidth of Subscriber 1, with basic data service. d. Create a parameter instance for max-subscriber-video-bandwidth, limiting video traffic to 2 Mbps. e. Create a parameter instance for max-100Kbps-voice-calls, enabling bandwidth for one 100 Kbps voice call. f. Attach the QoS profile subscriber-triple-play to the subscriber's interface.
host1(config)#interface fastEthernet 9/0.2 host1(config-if)#qos-parameter max-subscriber-bandwidth 6000000 host1(config-if)#qos-parameter subscriber-weight 3 host1(config-if)#qos-parameter max-subscriber-video-bandwidth 2000000 host1(config-if)#qos-parameter max-100Kbps-voice-calls 1 host1(config-if)#qos-profile subscriber-triple-play host1(config-if)#exit
3. Configure a enhanced triple-play service consisting of voice, video, and data services
for Subscriber 3. Enable the subscriber to have twice as much bandwidth as Subscriber 2, with basic triple-play service. a. Create a parameter instance for max-subscriber-bandwidth, enabling the subscriber to transmit up to 8 Mbps of combined voice, video, and data traffic. b. Create a parameter instance for subscriber-weight with a value of 6, enabling the subscriber to claim up to six times the bandwidth of Subscriber 1, with basic data service. c. Create a parameter instance for max-subscriber-video-bandwidth, limiting video traffic to 3 Mbps. d. 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
240
To display the traffic classes for best-effort, video, and voice, issue the show traffic-class command.
host1#show traffic-class fabric strict priority -------no no yes
2. To display the traffic-class group EF, issue the show traffic-class-group command. host1#show traffic-class-group traffic-class-group EF auto-strict-priority traffic-class voice 3. To display the settings for all four QoS parameter definitions
(max-subscriber-bandwidth, subscriber-weight, max-subscriber-video-bandwidth, and max-100Kbps-voice-calls), issue the show qos-parameter-define command.
host1#show qos-parameter-define controlled instance subscriber interface interface interface types types types ---------- ----------- ---------vlan vlan <none> vlan vlan <none> vlan vlan, svlan <none> vlan vlan <none> value range properties ----------------- ---------512000 - 8192000 <none> 1 - 10 <none> 1000000 - 5000000 <none> 1 - 3 <none>
parameter name -----------------------------max-subscriber-bandwidth subscriber-weight max-subscriber-video-bandwidth max-100Kbps-voice-calls parameter name -----------------------------max-subscriber-bandwidth subscriber-weight max-subscriber-video-bandwidth max-100Kbps-voice-calls
4. 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 burst
scheduler
shaping rate
241
---------------------default subscriber-best-effort subscriber-video subscriber-weight subscriber-voice scheduler ---------------------default subscriber-best-effort subscriber-video subscriber-weight subscriber-voice
-------------------------------------<none> <none> <none> <none> max-subscriber-video-bandwidth default <none> <none> max-100Kbps-voice-calls * 100000 default strict assured weight priority rate -----------------------------8 no <none> 8 no <none> 8 no <none> subscriber-weight no <none> 8 no <none> shared shared shaping shaping shared shaping rate burst constituent ---------------------------------------<none> <none> <none> max-subscriber-bandwidth default <none> <none> <none> <none> <none> <none> <none> <none> <none> <none> shared shaping mode ------------<none> auto implicit <none> <none> <none>
5. To display the settings for the QoS profile subscriber-triple-play, issue the show
qos-profile command.
host1#show qos-profile subscriber-triple-play qos-profile subscriber-triple-play: t-class interface rule traffic group type type class scheduler profile ------- ------- ----- ----------- ---------------------vlan node subscriber-weight svlan node default vlan queue best-effort subscriber-best-effort vlan queue video subscriber-video EF svlan node default EF vlan queue voice subscriber-voice
6. To display the attachments on all QoS profiles, issue the show qos-profile references
command.
host1#show qos-profile references qos profile attachment --------------------------------------------------------------------------atm-default (qos-port-type-profile) serial-default (qos-port-type-profile) ethernet-default (qos-port-type-profile) server-default (qos-port-type-profile) subscriber-data-service vlan FastEthernet9/0.1
242
7. To display global and interface attachments on all of the QoS parameter instances,
Global parameter instances: 4 Parameter instances reported: 13 8. To display the queue forwarding rates for the VLANs on the Fast Ethernet interface
class rate drop rate rate rate ----------- --------- --------- ------- --------best-effort * * 0 100000000 best-effort * * 0 2000000 best-effort * * 0 6000000 video voice best-effort video voice * * * * * 0 0 8 0 8 * 0 2000000 100000 8000000 3000000 300000
vlan FastEthernet9/0.3
* 100000 * 0 * * 0 300000
Queues reported: Queues filtered (under threshold): * Queues disabled (no rate period): **Queues disabled (no resources): Total queues:
9. To display the shared-shaper settings for the VLANs on the Fast Ethernet interface
243
host1#show qos shared-shaper interface fastEthernet 9/0 shared shaping shaping resource rate rate other ------------------------- ------- ------- -----------vlan node A vlan queue best-effort 2000000 rate 2000000 vlan node A vlan queue best-effort 6000000 rate 6000000 A vlan queue video 2000000 A vlan queue EF voice 100000 vlan node A vlan queue best-effort 8000000 rate 8000000 A vlan queue video 3000000 A vlan queue EF voice 300000
vlan Eth9/0.3
Total shared shapers: 3 Total constituents: 10 Total shared shaper failovers: 0 Compound shared shapers are not supported. 10. To display the scheduler hierarchy for the Fast Ethernet interface in slot 9, port 0,
244
To use the example for immediate use, copy it to the local console or Telnet session from which you access the router. You can also save the example as a script (.scr) file that executes the commands as though they were entered at the terminal. For information about executing .scr files, see JunosE System Basics Configuration Guide.
245
scheduler-profile subscriber-weight weight subscriber-weight exit ! Configure the subscriber-voice scheduler profile. scheduler-profile subscriber-voice shaping-rate max-100Kbps-voice-calls * 100000 exit ! Configure the subscriber-data-service QoS profile. qos-profile subscriber-data-service svlan node vlan node scheduler-profile subscriber-weight vlan queue traffic-class best-effort scheduler-profile subscriber-best-effort exit ! Configure the subscriber-triple-play QoS profile. qos-profile subscriber-triple-play svlan node vlan node scheduler-profile subscriber-weight svlan node group EF vlan queue traffic-class best-effort scheduler-profile subscriber-best-effort vlan queue traffic-class video scheduler-profile subscriber-video vlan queue traffic-class voice scheduler-profile subscriber-voice exit ! Configure the ethernet-default QoS profile. qos-profile ethernet-default no ip node no ip queue traffic-class best-effort exit ! 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 exit interface fastEthernet 9/0.3 svlan id 2 3 ip address 192.3.1.1 255.255.255.0 exit
246
svlan 1 qos-parameter max-subscriber-video-bandwidth 1000000 exit ! Configure the basic-data service for Subscriber 1. interface fastEthernet 9/0.1 qos-profile subscriber-data-service exit ! Configure the basic triple-play service for Subscriber 2. interface fastEthernet 9/0.2 qos-parameter max-subscriber-bandwidth 6000000 qos-parameter subscriber-weight 3 qos-parameter max-subscriber-video-bandwidth 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
247
248
CHAPTER 26
Hierarchical QoS Parameters Overview on page 249 Guidelines for Configuring Hierarchical Parameters on page 249 Configuring a Parameter Definition to Calculate Hierarchical Instances on page 250 Example: QoS Parameter Configuration for Hierarchical Parameters on page 251
Configuring a Parameter Definition to Calculate Hierarchical Instances on page 250 For information about the IP multicast bandwidth adjustment application, see IP Multicast Bandwidth Adjustment for QoS Overview on page 257
249
You can specify only a subset of the instance-interface types that are supported for non-hierarchical parameters. The following output lists the instance-interface types that are supported:
host1(config)#qos-parameter-define hierarchical-parameter hierarchical host1(config-qos-parameter-define)#instance-interface-type ? atm-vc ATM Virtual Circuit (VC) ip IP interface ipv6 IP version 6 interface l2tp-session L2tp session interface vlan VLAN subinterface
You can specify only one instance-interface type per hierarchical parameter. For example:
host1(config)#qos-parameter-define hierarchical-parameter hierarchical host1(config-qos-parameter-define)#instance-interface-type ip host1(config-qos-parameter-define)#instance-interface-type vlan % only one instance-interface-type can be specified for a hierarchical parameter
Hierarchical instance-interface types cannot stack above the highest controlled-interface type. For example:
host1(config)#qos-parameter-define hierarchical-parameter hierarchical host1(config-qos-parameter-define)#controlled-interface-type ip host1(config-qos-parameter-define)#instance-interface-type vlan % hierarchical instance-interface-type vlan cannot stack above controlled-interface-type ip
In contrast, a non-hierarchical instance-interface type cannot stack above the lowest controlled-interface type (vlan). For example:
host1(config)#qos-parameter-define non-hierarchical-parameter host1(config-qos-parameter-define)#controlled-interface-type vlan host1(config-qos-parameter-define)#instance-interface-type ip % instance-interface-type ip cannot stack above the lowest controlled-interface-type
You must specify a subscriber-interface type that is identical to the instanceinterface type that you specified. Configuring a Parameter Definition to Calculate Hierarchical Instances on page 250
Related Documentation
250
Related Documentation
Hierarchical QoS Parameters Overview on page 249 Configuring a Basic Parameter Definition for QoS Administrators on page 227 Configuring a Parameter Definition for IP Multicast Bandwidth Adjustment on page 259 Example: QoS Parameter Configuration for Hierarchical Parameters on page 251 qos-parameter-define
251
The QoS administrator configures the parameter definition for the maximum subscriber bandwidth. To configure a parameter definition for the maximum subscriber bandwidth:
1.
2. Enable the parameter to control S-VLANs. 3. Enable the parameter to control VLANs. 4. Enable the parameter to have instances created on VLAN subinterfaces. 5. Specify that the QoS client can create the parameter instance for VLANs, which
represent subscribers.
host1(config)#qos-parameter-define max-sub-bw hierarchical host1(config-qos-parameter-define)#controlled-interface-type svlan host1(config-qos-parameter-define)#controlled-interface-type vlan host1(config-qos-parameter-define)#instance-interface-type vlan host1(config-qos-parameter-define)#subscriber-interface-type vlan host1(config-qos-parameter-define)#exit
The QoS administrator can then reference the parameter definition within a scheduler profile, which defines the shaping rates for the parameter.
1.
Configure a scheduler profile to shape the throughput the explicit QoS parameters for VLANs. a. Configure the scheduler profile named sp-shape-cvlan. b. Configure the shaping rate by referencing the parameter max-sub-bw.
host1(config)#scheduler-profile sp-shape-cvlan host1(config-scheduler-profile)#shaping-rate max-sub-bw host1(config-scheduler-profile)#exit
a. Configure the scheduler profile named sp-shape-svlan. b. Configure the shaping rate by referencing the parameter max-sub-bw.
host1(config)#scheduler-profile sp-shape-svlan host1(config-scheduler-profile)#shaping-rate max-sub-bw host1(config-scheduler-profile)#exit
By referencing the scheduler profiles within QoS profiles, the QoS administrator creates the scheduler hierarchy. In this portion of the example, the QoS administrator configures QoS profiles for the VLAN and the S-VLAN.
1.
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.
252
host1(config)#qos-profile qp-shape-cvlan host1(config-qos-profile)#vlan queue traffic-class best-effort host1(config-qos-profile)#vlan node scheduler-profile sp-shape-cvlan host1(config-qos-profile)#exit
2. Configure the QoS profile for the S-VLAN interface.
a. Configure the QoS profile named qp-shape-svlan. b. Configure the S-VLAN node and reference the scheduler profile sp-shape-svlan.
host1(config)#qos-profile qp-shape-svlan host1(config-qos-profile)#svlan node scheduler-profile sp-shape-svlan host1(config-qos-profile)#exit
Create an explicit parameter instance at VLAN subinterface 100. a. Specify the Gigabit Ethernet interface in slot 2, port 0. b. Configure the VLAN major interface. c. Configure the VLAN subinterface at slot 2, port 0, subinterface 100. d. Assign an S-VLAN ID of 10 and a VLAN ID of 100 to the VLAN subinterface. e. Attach the max-sub-bw QoS parameter to the subinterface with a value of 1024000. f. Attach the qp-shape-cvlan QoS profile to the subinterface.
host1(config)#interface gigabitEthernet 2/0 host1(config-if)#encapsulation vlan host1(config)#interface gigabitEthernet 2/0.100 host1(config-if)#svlan id 10 100 host1(config-if)#qos-parameter max-sub-bw 1024000 host1(config-if)#qos-profile qp-shape-cvlan host1(config-if)#exit
a. Specify the VLAN subinterface 101 in slot 2, port 0. b. Assign an S-VLAN ID of 10 and a VLAN ID of 101 to the VLAN subinterface. c. 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
253
host1(config-if)#exit
3. Create an implicit parameter instance at S-VLAN subinterface 10.
a. Specify the Gigabit Ethernet interface at slot 2, port 0. b. Attach the qp-shape-svlan QoS profile to the node at S-VLAN subinterface 10.
host1(config)#interface gigabitEthernet 2/0 host1(config-if)#svlan 10 qos-profile qp-shape-svlan
Explicit parameter instances: Hierarchical parameter instances: IP multicast parameter instances: Parameter instances reported:
254
shaping-rate max-sub-bw exit scheduler-profile sp-shape-svlan shaping-rate max-sub-bw exit ! Configure the qp-shape-cvlan and qp-shape-svlan QoS profiles. qos-profile qp-shape-cvlan vlan queue traffic-class best-effort vlan node scheduler-profile sp-shape-cvlan exit qos-profile qp-shape-svlan svlan node scheduler-profile sp-shape-svlan exit
Related Documentation
255
256
CHAPTER 27
IP Multicast Bandwidth Adjustment for QoS Overview on page 257 Guidelines for Configuring IP Multicast Adjustment for QoS on page 259 Configuring a Parameter Definition for IP Multicast Bandwidth Adjustment on page 259 Example: QoS Parameter Configuration for IP Multicast Bandwidth Adjustment on page 261
257
logical interface minus the ip-multicast bandwidth. To enable the IP multicast QoS adjustment, you must:
Define a qos-parameter using the qos-parameter-define command with the application ip-multicast and the hierarchical keyword.
host1(config)# qos-parameter-define ipm application ip-multicast hierarchical host1(config-qos-parameter-define)#
This scheduler profile contains an expression for the shared-shaping rate that limits the shared-shaping rate to 10 Mbps less the rate of any IP multicast traffic.
Reference the scheduler profile within a QoS profile rule. For example:
host1(config)#qos-profile subscriber host1(config-qos-profile)#vlan node scheduler-profile totalSubscriberBw
This QoS profile rule limits a subscriber with vlan to the rate specified in the totalSubscriberBw scheduler profile. QoS clients do not need to create a parameter instance to activate the IP multicast bandwidth adjustment application. The system automatically creates explicit instances based on IGMP joins and leaves. When a subscriber logs in, the QoS scheduler hierarchy is created with the vlan configured for shared shaping, based on the expression 1000000 - ipm. If no multicast traffic is being transmitted, there is no ipm parameter instance with the vlan. To calculate the subscriber bandwidth from the total subscriber bandwidth, you must create a global parameter instance using the ip-multicast keyword and set the value to 0. To ensure the system can locate an instance of the ipm parameter for subscribers that are not receiving multicast traffic, you must create a global parameter with a value of 0:
host1(config)# qos-parameter ipm 0
If you do not create the global parameter instance, the expression result is undefined for these subscribers and the shared shaping rate is not set. By configuring a global parameter instance of 0, the value is applied to all the interfaces that reference the parameter. QoS overrides the global ipm parameter instance with the value specified in the bandwidth map for a specific IP interface on which IGMP joins. Related Documentation
Guidelines for Configuring IP Multicast Adjustment for QoS on page 259 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 225
258
You must specify a controlled-interface type. You cannot specify any instance-interface types or subscriber-interface types. By default, the system assigns a default instance-interface type of ip. When you specify the IP multicast bandwidth adjustment application, the parameter definition is hierarchical. You must specify the hierarchical keyword with the application keyword. The system prevents you from defining more than one parameter definition with the ip-multicast application specified. For example:
host1(config)#qos-parameter-define vpShaper application ip-multicast hierarchical host1(config-qos-parameter-define)#controlled-interface-type ip host1(config-qos-parameter-define)#exit host1(config)#qos-parameter-define bar application ip-multicast hierarchical % there cannot be more than one parameter defined with this property
Parameter instances associated with the IP multicast bandwidth adjustment application are not stored in non-volatile storage (NVS). (Parameter definitions are stored in NVS.) Because the application is activated based on IGMP joins and leaves received on an interface, the system removes the instances when you turn off or reset the router, then re-creates it based on new messages received on an interface. Configuring a Parameter Definition for IP Multicast Bandwidth Adjustment on page 259
Related Documentation
Define a multicast bandwidth map and the QoS adjustment for a virtual router. See JunosE Multicast Routing Configuration Guide.
259
adjustment as 0.
host1(config)#qos-parameter ipm 0
4. Reference the parameter within a scheduler profile parameter expression.
host1(config)#qos-profile vlan-subscriber host1(config-qos-profile)#vlan queue traffic-class best-effort host1(config-qos-profile)#vlan queue traffic-class voice scheduler-profile 192k host1(config-qos-profile)#vlan node scheduler-profile vlan-subscriber host1(config-qos-profile)#exit
6. Attach the parameter definition to a logical interface.
host1(config)#interface gigabitEthernet 7/0 host1(config-if)#encapsulation vlan host1(config-if)#exit host1(config)#interface gigabitEthernet 7/0.1 host1(config-if)#vlan id 200 host1(config-if)#qos-profile vlan-subscriber host1(config-if)#ip address 1.1.1.1 255.255.255.0
After the QoS profile is attached to the interface, the IP multicast bandwidth adjustment application begins to adjust rates based on IGMP joins and leaves received on that interface. Related Documentation
IP Multicast Bandwidth Adjustment for QoS Overview on page 257 Example: QoS Parameter Configuration for IP Multicast Bandwidth Adjustment on page 261 controlled-interface-type encapsulation vlan interface gigabitEthernet node qos-parameter-define qos-profile queue scheduler-profile shared-shaping-rate
260
traffic-class vlan id
The QoS administrator configures the traffic classes and traffic-class groups for best-effort data and voice services. The QoS administrator does not need to configure a traffic class for the video service because it is transmitted through the IP multicast connection.
261
1.
Configure the traffic classes. a. Configure the traffic class named best-effort. b. Configure the traffic class named voice.
host1(config)#traffic-class voice host1(config-traffic-class)#exit host1(config)#traffic-class best-effort host1(config-traffic-class)#exit
2. Configure a traffic-class group for low-latency expedited forwarding (EF) and add
the traffic class for voice service into the traffic-class group EF. a. Configure the EF traffic-class group with strict-priority scheduling. b. Add the traffic class voice to the traffic-class group.
host1(config)#traffic-class-group EF auto-strict-priority host1(config-traffic-class-group)#traffic-class voice host1(config-traffic-class-group)#exit
The remaining traffic class, best-effort, remains in the default traffic-class group.
The QoS administrator configures the QoS parameter definition and specifies the IP multicast bandwidth adjustment application. The QoS administrator must configure the parameter as hierarchical. The QoS scheduler hierarchy is constructed when the subscriber logs on. However, because the parameter instance has not yet been created, the shared-shaping rate is undefined (that is, there is no shaping rate). Therefore, the QoS administrator creates a global parameter instance to shape the subscriber to the desired bandwidth. The initial value is determined based on the application; in this example, the QoS administrator specifies 0 as the default.
1.
Configure the QoS parameter definition ipm, associate it with the ip-multicast application, and assign it as a hierarchical parameter.
host1(config)#qos-parameter-define ipm application ip-multicast hierarchical host1(config-qos-parameter-define)#controlled-interface-type atm-vc host1(config-qos-parameter-define)#exit host1(config)#qos-parameter ipm 0
Therefore, the initial shared-shaping rate is 10 Mbps (10 Mbps - ipm value of 0). Reference the Parameter Definition Within a Scheduler Profile The QoS administrator configures the scheduler profile for the ATM VC subscriber and configures the shared-shaping rate. When a scheduler profile references the parameter instance, it enables the IP multicast bandwidth adjustment application to adjust the subscriber bandwidth to account for the video traffic.
262
The QoS administrator then configures the scheduler profile to shape voice traffic.
1.
Configure the scheduler profile for the ATM VC subscriber. a. Configure the scheduler profile named vc-subscriber. b. Configure the shared-shaping rate by referencing an expression to limit the subscriber bandwidth to 10 Mbps.
host1(config)#scheduler-profile vc-subscriber host1(config-scheduler-profile)#shared-shaping-rate 10000000 - ipm burst 50 milliseconds auto host1(config-scheduler-profile)#exit
a. Configure the scheduler profile named 192K. b. Configure the shaping rate at 1920000.
host1(config)#scheduler-profile 192K host1(config-scheduler-profile)#shaping rate 192000 host1(config-scheduler-profile)#exit
The IP multicast adjustment application is initialized when IGMP joins or leaves. The QoS administrator specifies the scheduler hierarchy by using a QoS profile rule that refers to a scheduler profile with a parameter expression.
1.
2. Configure a queue for ATM VC subinterfaces with the best-effort traffic class. 3. Configure a queue for ATM VC subinterfaces with the voice traffic class and reference
vc-subscriber.
host1(config)#qos-profile ipm-adjusted host1(config-qos-profile)#atm-vc queue traffic-class best-effort host1(config-qos-profile)#atm-vc queue traffic-class voice scheduler-profile 192k host1(config-qos-profile)#atm-vc node scheduler-profile vc-subscriber host1(config-qos-profile)#exit
The QoS administrator creates a logical interface and attaches the parameter definition. The scheduler hierarchy is created when the QoS administrator creates the interface.
1.
2. Configure the ATM PVC with aal5snap encapsulation. 3. Attach the QoS profile vc-subscriber to the subinterface. 4. 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
263
When an IGMP join occurs, the IP multicast bandwidth adjustment application creates the parameter instance ipm for the IP interface and the ATM VC subinterface. Because the shared-shaping rate of the ATM VC references the ipm parameter, the rate is recalculated. If the imp parameter has a value of 2 Mbps, the resulting shared-shaping rate is 8 Mbps (10 Mbps - 2 = 8 Mbps). When another IGMP join occurs, the IP multicast bandwidth adjustment application recalculates the value for parameter ipm and configures it to another value (for example, 7 Mbps). The system readjusts the ipm at the ATM VC and readjusts the shared-shaping rate. If the voice traffic is 100 Kbps, then the best-effort traffic is 2.9 Mbps. When an IGMP leave occurs, the IP multicast bandwidth adjustment application configures the ipm parameter instance with a new value and readjusts the shared-shaping rate.
To display the traffic classes for best-effort and voice, issue the show traffic-class command.
host1#show traffic-class traffic class ----------best-effort voice fabric weight -----8 8 fabric strict priority -------no no
2. To display the traffic-class group, issue the show traffic-class-group command. host1#show traffic-class-group traffic-class-group EF auto-strict-priority traffic-class voice 3. To display the scheduler profile settings for vc-subscriber and 192K, issue the show
scheduler-profile command.
host1#show scheduler-profile shaping shaping scheduler rate burst ------------------------default <none> <none> vc-subscriber <none> <none> 192k 192000 default shared shaping rate -------------<none> 10000000 - ipm <none> strict assured weight priority rate ------------------8 no <none> 8 no <none> 8 no <none> shared shared shaping shaping shared burst constituent shaping mode -------------------------------<none> <none> <none> 50 bytes <none> simple implicit <none> <none> <none>
264
4. To display the attachments on all QoS profiles, including ipm-adjust, issue the show
5. To display the settings for the ipm-adjust QoS profile, issue the show qos-profile
command.
host1#show qos-profile ipm-adjust qos-profile ipm-adjust: t-class interface rule traffic scheduler queue drop statistics group type type class profile profile profile profile ------- --------- ----- ----------- ------------- ------- ------atm-vc node vc-subscriber atm-vc queue best-effort default default default default EF atm-vc queue voice 192k default default default 6. To display the settings for the ipm QoS parameter definition, issue the show
qos-parameter-define command.
host1#show qos-parameter-define controlled instance parameter interface interface name types types --------- -------------- --------ipm atm-vc <none> subscriber interface types ---------<none>
parameter name properties --------- ------------------------------------ipm ip-multicast-adjustment, hierarchical 7. To display global and interface attachments on the ipm QoS parameter instance,
265
Explicit parameter instances: Heirarchical parameter instances: IP multicast parameter instances: Parameter instances reported:
8. To display the queue forwarding rates for the ATM VC and IP interfaces on the ATM
9. To display the shared shaper settings for the ATM VC on the ATM interface in slot 2,
266
traffic-class best-effort exit traffic-class-group EF auto-strict-priority traffic-class best-effort exit ! 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. scheduler-profile vc-subscriber shared-shaping-rate 10000000 - ipm burst 50 milliseconds auto exit scheduler-profile 192K shaping-rate 192000 exit ! Add the scheduler profiles to the ipm-adjusted QoS profile. qos-profile ipm-adjusted atm-vc queue traffic-class best-effort atm-vc queue traffic-class voice scheduler-profile 192k atm-vc node scheduler-profile vc-subscriber exit ! 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 Documentation
267
268
CHAPTER 28
Cell Shaping Mode Using QoS Parameters Overview on page 269 Guidelines for Configuring the Cell Shaping Mode with QoS Parameters on page 271 Configuring a Parameter Definition to Shape Ethernet Traffic Using Cell Mode on page 272 Example: QoS Parameter Configuration for QoS Cell Mode and Byte Adjustment for Cell Shaping on page 273
269
The QoS administrator then applies frame shaping mode to the Gigabit Ethernet interface configured on slot 6, adapter 0, port 2, subinterface 1 using the QoS cell mode application. This parameter instance overrides the shaping mode configured at the port.
host1(config-if)#interface gigabitEthernet 6/0/2.1 host1(config-if)#qos-parameter cell-mode 0
qos-cell-mode Application
Adjustment Performed By
Internal cell-taxing mechanism
Parameter expression associated with qos-cell-mode application (See Cell Tax Adjustment Using QoS Cell Mode on page 270.) Internal cell-taxing mechanism
ATM interfaces on all E Series routers All other interface types on all E Series routers
270
Chapter 28: Configuring the Shaping Mode for Ethernet with QoS Parameters
NOTE: Do not use the parameter expression on Ethernet interfaces configured on the ES2 4G LM, GE-2 line module, or the GE-HDE line module.
For example, the subscriber-rate parameter represents the bandwidth of a subscriber. The shaping rate for the parameter is calculated by referencing an expression that represents the cell mode adjustment in a scheduler profile:
(config-scheduler-profile)# shaping-rate subscriber-rate - subscriber-rate * cell-mode % 25
The subscriber-rate - subscriber-rate * cell-mode % 25 expression provides for an explicit cell-tax factor of 25 percent when the subscriber local loop is transmitting cells. In cases where the local loop is very-high-bit-rate digital subscriber line (VDSL), the second term in the expression drops to 0.
Configuring a Parameter Definition to Shape Ethernet Traffic Using Cell Mode on page 272 Example: QoS Parameter Configuration for QoS Cell Mode and Byte Adjustment for Cell Shaping on page 273 For more information about configuring the QoS shaping mode, see QoS Shaping Mode for Ethernet Interfaces Overview on page 172 For more information about configuring scheduler rates for QoS parameters, see Scheduler Profiles and Parameter Expressions for QoS Administrators on page 225 For more information about shaping the downstream rate using QoS parameter instances that were created dynamically by ANCP, see QoS Downstream Rate Application Overview on page 287
Guidelines for Configuring the Cell Shaping Mode with QoS Parameters
When you specify the QoS cell mode application, the following considerations apply:
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.
271
You can specify only the subscriber-interface type of vlan when you configure Qos cell mode application on its own or with the byte adjustment application. When you configure the QoS cell mode application with the QoS downstream rate application, you must specify a subscriber-interface type. ANCP uses the subscriber-interface type to determine the instance-interface type on which to dynamically create the parameter. You can specify only 0 or 1 as the values for a parameter instance with the QoS cell mode application configured. 0 indicates frame mode, and 1 indicates cell mode. You cannot configure another range for the parameter definition using the range command. Cell Shaping Mode Using QoS Parameters Overview on page 269 Configuring a Parameter Definition to Shape Ethernet Traffic Using Cell Mode on page 272 Example: QoS Parameter Configuration for QoS Cell Mode and Byte Adjustment for Cell Shaping on page 273 For more information about configuring scheduler rates for QoS parameters, see Scheduler Profiles and Parameter Expressions for QoS Administrators on page 225 For more information about the QoS downstream rate application, see QoS Downstream Rate Application Overview on page 287
Related Documentation
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
272
Chapter 28: Configuring the Shaping Mode for Ethernet with QoS Parameters
host1(config-if)#interface gigabitEthernet 6/0/2.1 host1(config-if)#vlan id 1 host1(config-if)#qos-parameter cell-mode 1 host1(config-if)#ip address 6.10.10.10 255.255.255.255 host1(config-if)#exit host1(config)#interface gigabitEthernet 6/0/2 host1(config-if)#svlan 1 qos-parameter cell-mode 1 host1(config-if)#exit host1(config)#interface gigabitEthernet 6/0/2 host1(config-if)#qos-parameter cell-mode 1
Related Documentation
Example: QoS Parameter Configuration for QoS Cell Mode and Byte Adjustment for Cell Shaping on page 273 For more information about configuring scheduler rates for QoS parameters, see Scheduler Profiles and Parameter Expressions for QoS Administrators on page 225 For more information about the QoS downstream rate application, see QoS Downstream Rate Application Overview on page 287 controlled-interface-type instance-interface-type interface gigabitEthernet ip address qos-parameter qos-parameter-define scheduler-profile svlan qos-parameter traffic-class vlan id
Example: QoS Parameter Configuration for QoS Cell Mode and Byte Adjustment for Cell Shaping
The example in this section illustrates how to configure the byte adjustment application to adjust the shaping rate for downstream ATM traffic from the customer premise equipment (CPE) to Ethernet interfaces configured on an E320 router. In this example, the QoS administrator manages the shaping rate using a combination of the byte adjustment application and cell shaping mode to account for different layer 2 encapsulations and the ATM cell pad, header, and trailer. Figure 64 on page 274 displays the Ethernet network to which the QoS administrator applies the byte adjustment.
273
In Figure 64 on page 274, VLAN 1 and VLAN 2 map to the subscribers at VC1 and VC2. The QoS administrator allocates a total of 10 Mbps of bandwidth for voice, video, and data services to VC1, and 2 Mbps of bandwidth of data traffic for VC2. Table 28 on page 274 lists the shaping rate and byte adjustment for both subscribers.
VC2
A1 encapsulation -2 1000000 bps 1000000 bps
The QoS administrator configures the traffic classes and traffic-class groups for video and voice services.
1.
The QoS administrator configures a parameter definition and the byte adjustment application. 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.
1.
274
Chapter 28: Configuring the Shaping Mode for Ethernet with QoS Parameters
VLAN and IP queues. a. Configure the controlled-interface type for VLAN. b. Configure the controlled-interface type for IP.
host1(config-qos-parameter-define)#controlled-interface-type vlan host1(config-qos-parameter-define)#controlled-interface-type ip host1(config-qos-parameter-define)#exit
The QoS administrator then configures the QoS shaping mode using the QoS cell mode application. When you configure the QoS shaping mode to cell mode on port 0 of the IOA, all ports on the IOA use the same value.
1.
2. Define the controlled-interface types for vlan and ip for the shaping mode.
The QoS administrator configures the shaping rate and the shared-shaping rate within scheduler profiles for the subscribers at VC1 and VC2.
1.
Configure the scheduler profile for the subscriber VC1. a. Configure the scheduler profile named vc1. b. Configure the shared-shaping rate of 10000000 with a burst of 10 milliseconds.
host1(config)#scheduler-profile vc1 host1(config-scheduler-profile)#shared-shaping-rate 10000000 burst 10 milliseconds host1(config-scheduler-profile)#exit
a. Configure the scheduler profile named voice. b. Configure the shared-shaping rate of 100000 with a burst of 10 milliseconds.
host1(config)#scheduler-profile voice host1(config-scheduler-profile)#shaping-rate 100000 burst 10 milliseconds host1(config-scheduler-profile)#exit
3. 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
275
host1(config-scheduler-profile)#exit
4. Configure the scheduler profile for the subscriber VC2.
a. Configure the scheduler profile named vc2. b. Configure the shared-shaping rate of 1000000 with a burst of 10 milliseconds.
host1(config)#scheduler-profile vc2 host1(config-scheduler-profile)#shaping-rate 1000000 burst 10 m host1(config-scheduler-profile)#exit
After configuring the scheduler profiles, the QoS administrator then configures QoS profiles for subscribers VC1 and VC2.
1.
Configure the vc1 QoS profile with a shared-shaping rate of 10 Mbps. a. Configure the QoS profile vc1. b. Configure the vlan node and reference the scheduler profile vc1. c. Configure the vlan queue and reference the voice traffic class and the voice scheduler profile. d. Configure the vlan queue and reference the video traffic class and the video scheduler profile.
host1(config)#qos-profile vc1 host1(config-qos-profile)#vlan node scheduler-profile vc1 host1(config-qos-profile)#vlan queue traffic-class voice schedule-profile voice host1(config-qos-profile)#vlan queue traffic-class video schedule-profile video host1(config-qos-profile)#exit
a. Configure the QoS profile vc2. b. Configure the vlan node and reference the scheduler profile vc2.
host1(config)#qos-profile vc2 host1(config-qos-profile)#vlan node scheduler-profile vc2 host1(config-qos-profile)#exit
The QoS administrator creates logical interfaces for VLAN1 and VLAN2 and attaches the parameter definitions to them.
1.
Attach the parameter definition to VLAN1. a. Configure the Gigabit Ethernet interface in slot 6, adapter 0, port 0. b. Configure the VLAN major interface. c. Configure the Gigabit Ethernet interface in slot 6, adapter 0, port 0, subinterface 1. d. Assign VLAN ID of 1. e. Create a parameter instance for byte-adjustment with a value of -28.
276
Chapter 28: Configuring the Shaping Mode for Ethernet with QoS Parameters
f. Create a parameter instance for cell-mode with a value of 1 (cell shaping mode). g. Attach the QoS profile vc1 to the Gigabit Ethernet interface.
host1(config)#interface gigabitEthernet 6/0/0 host1(config-if)#encapsulation vlan host1(config-if)#interface gigabitEthernet 6/0/0.1 host1(config-if)#vlan id 1 host1(config-if)#qos-parameter byte-adjustment -28 host1config-if)#qos-parameter cell-mode 1 host1(config-if)#qos-profile vc1 host1(config-if)#exit
2. Attach the parameter definition to VLAN2.
a. Specify the Gigabit Ethernet interface in slot 6, adapter 0, port 1. b. Assign a VLAN ID of 2. c. Create a parameter instance for byte-adjustment with a value of -2. d. Create a parameter instance for cell-mode with a value of 1 (cell shaping mode). e. Attach the QoS profile vc2 to the Gigabit Ethernet interface.
host1(config-if)#interface gigabitEthernet 6/0/1.1 host1(config-if)#vlan id 2 host1(config-if)#qos-parameter byte-adjustment -2 host1(config-if)#qos-parameter cell-mode 1 host1(config-if)#qos-profile vc2 host1(config-if)#exit
277
exit ! Create the cell-mode QoS parameter definition. qos-parameter-define cell-mode application qos-cell-mode controlled-interface-type vlan controlled-interface-type ip exit ! Configure the vc1 and vc2 scheduler profiles. scheduler-profile vc1 shared-shaping-rate 10000000 burst 10 milliseconds exit scheduler-profile voice shaping-rate 100000 burst 10 milliseconds exit scheduler-profile video shaping-rate 8000000 burst 10 milliseconds exit scheduler-profile vc2 shaping-rate 1000000 burst 10 m exit ! Add the scheduler profiles to the vc1 QoS profile. qos-profile vc1 vlan node scheduler-profile vc1 vlan queue traffic-class voice schedule-profile voice vlan queue traffic-class video schedule-profile video exit qos-profile vc2 vlan node scheduler-profile vc2 ! Configure the byte adjustment for VLAN1 and VLAN2. interface gigabitEthernet 6/0/0 encapsulation vlan interface gigabitEthernet 6/0/0.1 vlan id 1 qos-parameter byte-adjustment -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 Documentation
278
CHAPTER 29
Byte Adjustment for ADSL and VDSL Traffic Overview on page 279 Guidelines for Configuring Byte Adjustment of Cell and Frame Shaping Rates Using QoS Parameters on page 282 Configuring a Parameter Definition to Adjust Cell Shaping Rates for ADSL Traffic on page 283 Configuring a Parameter Definition to Adjust Frame Shaping Rates for VDSL Traffic on page 285
279
To adjust the shaping rates to account for different layer 2 encapsulations as well as the ATM cell pad, header, and trailer on interfaces, apply a parameter with the cell byte-adjustment application (qos-byte-adjustment). When you apply a parameter with the qos-byte-adjustment application to an interface with frame shaping mode, you adjust shaping rates to account for different layer 2 encapsulations only.
Figure 65: Byte Adjustment Calculation for Ethernet and ATM Encapsulations
Table 29 on page 280 lists the header lengths for the Ethernet encapsulation, which represents the CPE protocol overhead. The hierarchy is PPPoE over S-VLAN over Ethernet.
Number of Bytes
14 bytes (6-SA, 6-DA, 2-ethertype) 8 bytes (2-vmanTci, 2-ethertype, 2-vlanTci, 2-ethertype) 6 bytes (1-version/type, 1-code, 2-session id, 2-length) 2 bytes (2-protocol id) 4 bytes 34 bytes
PppoeHeader
Ppp FCS
Total
280
Chapter 29: Configuring Byte Adjustment for Shaping Rates with QoS Parameters
Table 30 on page 281 lists the header lengths for the ATM encapsulation, which represents the B-RAS protocol overhead. The interface stack is PPPoA over ATM 1483 with LLC Mux. The ATM AAL5 trailer is considered cell tax and is not part of the byte adjustment calculation.
Number of Bytes
4 bytes 2 bytes (2-protocol id) 6 bytes
Total
Table 31: Byte Adjustment Values for Frame and Cell Shaping Modes
Shaping Mode on Port 0
Cell Cell
281
Table 31: Byte Adjustment Values for Frame and Cell Shaping Modes (continued)
Shaping Mode on Port 0
Frame Frame Frame
Related Documentation
Configuring a Parameter Definition to Adjust Cell Shaping Rates for ADSL Traffic on page 283 Configuring a Parameter Definition to Adjust Frame Shaping Rates for VDSL Traffic on page 285 Example: QoS Parameter Configuration for QoS Cell Mode and Byte Adjustment for Cell Shaping on page 273 For more information about configuring shaping modes for Ethernet, see QoS Shaping Mode for Ethernet Interfaces Overview on page 172 and Cell Shaping Mode Using QoS Parameters Overview on page 269 For more information about shaping the downstream rate using QoS parameter instances that were created dynamically by ANCP, see QoS Downstream Rate Application Overview on page 287
Guidelines for Configuring Byte Adjustment of Cell and Frame Shaping Rates Using QoS Parameters
When you specify the cell or frame byte-adjustment application, the following considerations apply:
You can have only one QoS parameter definition with the cell byte-adjustment application (qos-byte-adjustment) configured. You can only have one QoS parameter definition with the frame byte-adjustment application (qos-frame-byte-adjustment) configured. You can specify only instance-interface types of lag, ethernet, svlan, and vlan. You can specify only an subscriber-interface type of vlan. The available range for parameters with the byte adjustment application is -3263. You cannot configure another range using the range command. We recommend that you apply the byte adjustment parameter at the lowest interface column so that upper interfaces automatically have the parameter. 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
282
Chapter 29: Configuring Byte Adjustment for Shaping Rates with QoS Parameters
of 4 bytes. The maximum byte adjustment value that you can configure is 59. When you configure a byte adjustment value greater than 59 in a QoS parameter, the system automatically resets the value to 59. Related Documentation
Byte Adjustment for ADSL and VDSL Traffic Overview on page 279 Configuring a Parameter Definition to Adjust Cell Shaping Rates for ADSL Traffic on page 283 Configuring a Parameter Definition to Adjust Frame Shaping Rates for VDSL Traffic on page 285 Example: QoS Parameter Configuration for QoS Cell Mode and Byte Adjustment for Cell Shaping on page 273 For more information about configuring shaping modes for Ethernet, see QoS Shaping Mode for Ethernet Interfaces Overview on page 172 and Cell Shaping Mode Using QoS Parameters Overview on page 269
Configuring a Parameter Definition to Adjust Cell Shaping Rates for ADSL Traffic
You can adjust shaping rates to account for different layer 2 encapsulations as well as the ATM cell pad, header, and trailer on interfaces with cell shaping mode using the qos-byte-adjustment application.
NOTE: When you apply a parameter with the qos-byte-adjustment application to an interface with frame shaping mode, you adjust shaping rates to account for different layer 2 encapsulations only.
283
Configure the shaping mode by issuing the qos-shaping-mode command. Frame shaping mode is the default for Ethernet interfaces on all E Series routers. You can only set the cell shaping mode for Gigabit Ethernet and 10-Gigabit Ethernet interfaces configured on the GE-2 line module, the GE-HDE line module, and the ES2 4G LM.
Configure the shaping mode by specifying the QoS cell mode application with a parameter definition.
host1(config)#qos-parameter-define cell-mode application qos-cell-mode
In this example, parameter instances are created for both the byte adjustment and QoS cell mode applications.
host1(config)#interface gigabitEthernet 7/0 host1(config-if)#encapsulation vlan host1(config-if)#exit host1(config)#interface gigabitEthernet 7/0.1 host1(config-if)#vlan id 1 host1(config-if)#qos-parameter byteadjustment -16 host1(config-if)#qos-parameter cell-mode 1 host1(config-if)#ip address 1.1.1.1 255.255.255.0
Related Documentation
Byte Adjustment for ADSL and VDSL Traffic Overview on page 279 Guidelines for Configuring Byte Adjustment of Cell and Frame Shaping Rates Using QoS Parameters on page 282 Example: QoS Parameter Configuration for QoS Cell Mode and Byte Adjustment for Cell Shaping on page 273 For information about managing packet fragmentation for traffic with frame shaping mode, see Configuring a Parameter Definition to Adjust Frame Shaping Rates for VDSL Traffic on page 285 For more information about configuring shaping modes for Ethernet, see QoS Shaping Mode for Ethernet Interfaces Overview on page 172 and Cell Shaping Mode Using QoS Parameters Overview on page 269 controlled-interface-type encapsulation vlan instance-interface-type ip address node qos-parameter qos-parameter-define qos-profile queue
284
Chapter 29: Configuring Byte Adjustment for Shaping Rates with QoS Parameters
traffic-class vlan id
Configuring a Parameter Definition to Adjust Frame Shaping Rates for VDSL Traffic
Packet fragmentation can occur at a DSLAM because of the associated segment header that is added for VDSL2 in frame shaping mode. Because the segment header is not included in the ANCP rate report, the forwarding rate on an E Series router can be higher than the DSLAM rate, which can result in packet loss. You can use a QoS parameter expression with the frame byte-adjustment application to reduce the forwarding rate so that it matches the VDSL downstream rate at the DSLAM. You can also configure the cell mode application to account for ADSL downstream traffic that is also being received. To configure a QoS parameter definition to adjust frame shaping rates and manage packet fragmentation:
1.
Configure the QoS parameter definition to accept downstream shaping rate instantiation from ANCP.
host1(config)#qos-parameter-define ancp-downstream application qos-downstream-rate
2. Configure the QoS parameter definition for the frame byte-adjustment application
The ADSL type corresponds to cell mode and VDSL corresponds to frame mode.
4. Configure the parameter expression to reduce the shaping rate to account for packet
fragmentation. In the following expression, the adjustment is applied to traffic with frame shaping mode only. The byte adjustment value is 8 and the shaping rate is reduced by 2 percent.
host1(config)#scheduler-profile service-provider-business host1(config-scheduler-profile)# shaping-rate ancp-downstream - (ancp-downstream % 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.
285
If the user packet size changes, you must change the expression value and the byte adjustment value.
5. To ensure that the router handles the byte adjustment value consistently for VDSL
and ADSL networks, apply the QoS parameter for frame shaping mode globally.
host1(config)#qos-parameter frame-byte 8
NOTE: The ancp-downstream rate and sp-qos-cell-mode QoS parameters are dynamically applied to QoS by ANCP.
Related Documentation
Byte Adjustment for ADSL and VDSL Traffic Overview on page 279 qos-parameter qos-parameter-define qos-profile scheduler-profile shaping-rate
286
CHAPTER 30
QoS Downstream Rate Application Overview on page 287 Guidelines for Configuring QoS Downstream Rate on page 289 Configuring a Parameter Definition for QoS Downstream Rate on page 289 Example: QoS Parameter Configuration for QoS Downstream Rate on page 291
287
Shaping Mode
Cell Cell Cell Cell Frame Cell
Configuring a Parameter Definition for QoS Downstream Rate on page 289 Example: QoS Parameter Configuration for QoS Downstream Rate on page 291 For more information about configuring the shaping mode for Ethernet interfaces, see QoS Shaping Mode for Ethernet Interfaces Overview on page 172 and Cell Shaping Mode Using QoS Parameters Overview on page 269 For more information about configuring byte adjustment for downstream rates, see Byte Adjustment for ADSL and VDSL Traffic Overview on page 279 For information about configuring the shaping mode for ATM interfaces, see Configuring the QoS Shaping Mode for ATM Interfaces on page 169
288
For more information about DSL Forum VSAs, see JunosE Broadband Access Configuration Guide
You can have only one parameter definition with the QoS downstream rate configured. You must specify a controlled-interface type. You must configure a subscriber-interface-type. ANCP uses the subscriber-interface type to determine the instance-interface type on which to dynamically create the parameter. Access loops can synchronize after the user has logged in. The business logic depends on the rate that is reported in the Access-Request message. We recommend that service providers use RADIUS Connect-Info attribute [77] as the default value for their business logic. When the ANCP rate information is not present, the system uses the default QoS parameter instance (which can be defined globally or per VLAN). The advisory transmit speed configurable per VLAN is reported to the RADIUS Connect-Info attribute [77]. Ensure that the value of the default QoS parameter is aligned with the value in RADIUS Connect-Info attribute 77. QoS Downstream Rate Application Overview on page 287 Configuring a Parameter Definition for QoS Downstream Rate on page 289 Example: QoS Parameter Configuration for QoS Downstream Rate on page 291 For more information about the RADIUS Connect-Info attribute, see JunosE Broadband Access Configuration Guide
Related Documentation
289
For VLANs, configure the shaping mode by creating a parameter definition with the QoS cell mode application. Ensure that you specify a subscriber-interface type. See Configuring a Parameter Definition to Shape Ethernet Traffic Using Cell Mode on page 272.
For ATM VCs, configure the shaping mode by issuing the qos-shaping-mode command. See Configuring the QoS Shaping Mode for ATM Interfaces on page 169.
4. Enable QoS adaptive mode for the system by issuing the qos-adaptive-mode
ANCP or AAA dynamically creates the parameter instances for the QoS downstream rate application, and if applicable, the QoS cell mode application; therefore, you do not need to specify them.
host1(config)#interface gigabitEthernet 6/0/2 host1(config-if)#encapsulation vlan host1(config-if)#interface gigabitEthernet 6/0/2.1 host1(config-if)#vlan id 1 host1(config-if)#qos-profile vlan1 host1(config-if)#ip address 6.10.10.10 255.255.255.255
Related Documentation
Example: QoS Parameter Configuration for QoS Downstream Rate on page 291 For information about downstream rate and RADIUS, see JunosE Broadband Access Configuration Guide
290
For more information about configuring ANCP (L2C) parameters, see JunosE IP Services Configuration Guide aaa qos downstream-rate controlled-interface-type encapsulation vlan instance-interface-type ip address node qos-parameter qos-adaptive-mode qos-parameter-define qos-profile queue shared-shaping-rate subscriber-interface-type traffic-class vlan id
VLAN2
Cell 100000 bps
The QoS administrator configures the traffic classes for voice and video services.
1.
291
The QoS administrator configures a parameter definition for the QoS downstream rate application. Using subscriber-interface types, the QoS administrator then enables ANCP to create parameter instances of the QoS downstream rate application.
1.
2. Define the controlled-interface types for vlan and ip to adjust the shaping rate for the
VLAN and IP queues. a. Configure the controlled-interface type for VLAN. b. Configure the controlled-interface type for IP.
host1(config-qos-parameter-define)#controlled-interface-type vlan host1(config-qos-parameter-define)#controlled-interface-type ip
3. Define the subscriber-interface types for vlan and ethernet.
The QoS administrator then configures the QoS shaping mode using the QoS cell mode application. Using subscriber-interface types, the QoS administrator then enables ANCP to create parameter instances using the QoS cell mode application.
1.
2. Define the controlled-interface types for vlan and ip for the shaping mode.
292
host1(config-l2c)#qos-adaptive-mode
The QoS administrator configures the shaping rate and the shared-shaping rate within scheduler profiles for the VLAN1 and VLAN2 subscribers.
1.
Configure the scheduler profile for the subscriber vlan1. a. Configure the scheduler profile named vlan1. b. Configure the shared-shaping rate by referencing the ancpVlan parameter with a burst of 10 milliseconds.
host1(config)#scheduler-profile vlan1 host1(config-scheduler-profile)#shared-shaping-rate ancpVlan burst 10 milliseconds auto host1(config-scheduler-profile)#exit
a. Configure the scheduler profile named voice. b. Configure the shaping rate of 100000 with a burst of 10 milliseconds.
host1(config)#scheduler-profile voice host1(config-scheduler-profile)#shaping-rate 100000 burst 10 milliseconds host1(config-scheduler-profile)#exit
3. Configure the scheduler profile for the video service.
a. Configure the scheduler profile named video. b. Configure the 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 host1(config-scheduler-profile)#exit
4. Configure the scheduler profile for the subscriber vlan2.
a. Configure the scheduler profile named vlan2. b. Configure the shaping rate by referencing the ancpVlan parameter with a burst of 10 milliseconds.
host1(config)#scheduler-profile vlan2 host1(config-scheduler-profile)#shaping-rate ancpVlan burst 10 milliseconds host1(config-scheduler-profile)#exit
After configuring the scheduler profiles, the QoS administrator then configures QoS profiles for the VLAN1 and VLAN2 subscribers.
1.
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.
293
c. Configure the vlan queue and reference the voice traffic class and the voice scheduler profile. d. Configure the vlan queue and reference the video traffic class and the video scheduler profile.
host1(config)#qos-profile vlan1 host1(config-qos-profile)#vlan node scheduler-profile vlan1 host1(config-qos-profile)#vlan queue traffic-class voice scheduler-profile voice host1(config-qos-profile)#vlan queue traffic-class video scheduler-profile video host1(config-qos-profile)#exit
2. Configure the vlan2 QoS profile with a shaping rate of 1 Mbps.
a. Configure the QoS profile named vlan2. b. Configure the vlan node and reference the scheduler profile vlan2.
host1(config)#qos-profile vlan2 host1(config-qos-profile)#vlan node scheduler-profile vlan2 host1(config-qos-profile)#exit
The QoS administrator creates logical interfaces for VLAN1 and VLAN2 and attaches the QoS profiles to them. As the subscribers log in, ANCP creates the parameter instances for cellmodeVlan and ancpVlan using RADIUS VSAs.
1.
Attach the vlan1 QoS profile to VLAN1. a. Configure the Gigabit Ethernet interface in slot 6, adapter 0, port 0. b. Configure the VLAN major interface. c. Configure the Gigabit Ethernet interface in slot 6, adapter 0, port 0, subinterface 1. d. Assign VLAN ID of 1. e. Attach the QoS profile vc1 to the interface.
host1(config)#interface gigabitEthernet 6/0/0 host1(config-if)#encapsulation vlan host1(config-if)#interface gigabitEthernet 6/0/0.1 host1(config-if)#vlan id 1 host1(config-if)#qos-profile vlan1 host1(config-if)#exit
a. 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
294
295
vlan queue traffic-class video scheduler-profile video exit qos-profile vlan2 vlan node scheduler-profile vlan2 exit ! 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 Documentation
296
PART 7
Monitoring QoS on E Series Routers on page 299 Troubleshooting QoS on page 341
297
298
CHAPTER 31
NOTE: The E120 and E320 Broadband Services Routers output for monitor and show commands is identical to output from other E Series routers, except that the E120 and E320 router output also includes information about the adapter identifier in the interface specifier (slot/adapter/port).
Monitoring Service Levels with Traffic Classes on page 300 Monitoring Service Levels with Traffic-Class Groups on page 301 Monitoring Queue Thresholds on page 302 Monitoring Queue Profiles on page 305 Monitoring Drop Profiles for RED and WRED on page 306 Monitoring the QoS Scheduler Hierarchy on page 307 Monitoring the Configuration of Scheduler Profiles on page 313 Monitoring Shared Shapers on page 314 Monitoring Shared Shaper Algorithm Variables on page 316 Monitoring Forwarding and Drop Events on the Egress Queue on page 317 Monitoring Forwarding and Drop Rates on the Egress Queue on page 318 Monitoring Queue Statistics for the Fabric on page 322 Monitoring the Configuration of Statistics Profiles on page 323 Monitoring the QoS Profiles Attached to an Interface on page 324 Monitoring the Configuration of QoS Port-Type Profiles on page 325 Monitoring the Configuration of QoS Profiles on page 325 Monitoring the QoS Configuration of ATM Interfaces on page 328 Monitoring the QoS Configuration of IP Interfaces on page 330 Monitoring the QoS Configuration of Fast Ethernet, Gigabit Ethernet, and 10-Gigabit Ethernet Interfaces on page 332
299
Monitoring the QoS Configuration of IEEE 802.3ad Link Aggregation Group Bundles on page 333 Monitoring the Configuration of QoS Interface Sets on page 334 Monitoring the Configuration of QoS Interface Supersets on page 335 Monitoring the AAA Downstream Rate for QoS on page 336 Monitoring QoS Parameter Instances on page 336 Monitoring QoS Parameter Definitions on page 339
To display the number of times that a QoS profile references the traffic class:
host1#show traffic-class brief traffic-class best-effort referenced 17 times in qos-profiles
To display a list of QoS profiles and traffic-class groups that reference the traffic class:
host1#show traffic-class references traffic-class best-effort Referenced by QoS profiles: atm-default serial-default ethernet-default server-default Referenced by traffic class groups: None
Meaning
Table 34 on page 300 lists the show traffic-class command output fields.
Field Description
Name of the traffic class Weight of the queue in the fabric Setting strict-priority queues in the fabric
300
Field Description
QoS profiles that reference this traffic class Traffic-class groups that reference this traffic class
Related Documentation
Configuring Traffic Classes That Define Service Levels on page 14 show traffic-class
To display a list of profiles and QoS profiles that reference the traffic-class group:
host1#show traffic-class-group references traffic-class-group g2 Referenced by QoS profiles: profile1 traffic-class-group g3 Referenced by QoS profiles: None
Meaning
Table 35 on page 301 lists the show traffic-class-group command output fields.
Field Description
Name of the traffic-class group Name of the traffic class Number of times group is referenced by QoS profiles
301
Field Description
QoS profiles that reference this traffic class
Related Documentation
Configuring Traffic-Class Groups That Define Service Levels on page 15 show traffic-class-group
region -----0 1 2 3 4 5 6 7
As shown, when all of the egress memory in use is between 0 MB and 4 MB, each video queue can queue 139,648 bytes of committed traffic. Because the default conformed fraction is 50 percent and the default exceeded fraction is 25 percent, half of the committed length, or 69,888 bytes, can be queued before conformed traffic is dropped, and one quarter of the committed length, or 34,944 bytes, can be queued before exceeded traffic is dropped. While memory fills, the video queues are given progressively smaller amounts of memory. For example, when 28 to 32 MB of buffer memory is in use, each video queue is limited to 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 routers memory management:
302
host1#show qos queue-thresholds egress-slot 9 region 0 region 0 (0MB - 4MB) oversubscription 3330% exceeded length -------34944 34944 34944 34944 conformed length --------69888 69888 69888 69888 committed length --------139648 139648 139648 139648 queue count ----2000 2000 2000 2000 total committed memory --------279296000 279296000 279296000 279296000
Static and dynamic oversubscription determines that when 8000 queues are configured and 04 MB of egress buffer memory is in use, memory is oversubscribed by 3330 percent. If significantly fewer queues are configured, there is less oversubscription. This example illustrates static oversubscription. Because all of the queues in Example 2 use default queue profiles, all queues have the same lengths. Each queue is allocated 139,648 bytes of committed buffer memory when operating within this region. This allocation allows active queues to burst traffic by using memory that is unused by quiescent queues. This example illustrates dynamic oversubscription, which is based on the assumption that when a large number of queues is configured, only a fraction of the queues is active at a given time. While more queues become active, memory fills and spills into another region. When this occurs, queues are given progressively smaller queue limits. In memory regions 1 through 5, queue limits are progressively reduced. In region 6, memory is strictly partitioned among queues. To display oversubscription in region 6:
host1#show qos queue-thresholds egress-slot 9 region 6 region 6 (24MB - 28MB) oversubscription 100% exceeded length -------1152 1152 1152 1152 conformed length --------2176 2176 2176 2176 committed length --------4224 4224 4224 4224 queue count ----2000 2000 2000 2000 total committed memory --------8448000 8448000 8448000 8448000
Oversubscription is 100 percent. When 2428 MB of the memory is in use, there is no oversubscription of egress buffer memory; 32 MB of the 32-MB memory is allocated. In Example 3, each of the 8000 egress queues is given a queue of 4224 bytes, for a total of 16 MB. If memory continues to fill into region 7, egress buffer memory is undersubscribed, allowing control traffic to flow within the router. As shown in Example 4, when operating in region 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% exceeded length conformed length committed length queue count total committed memory
queue-profile
303
Region 7 has 2000 IP users, each with four queues. Each of the four queues use default queue profiles.
The multicast queue profile is configured with a committed length of 10,000 minimum and 20,000 maximum. When in regions 04, these queues would normally get more memory than the 20,000 byte maximum requested. In this case, the queue is limited to the maximum, and any excess memory is redistributed to other queues. Region 5 does not have enough memory to honor the 20,000-byte maximum requested. Although a 20,000 byte maximum was requested, the router provisions memory in 128 byte blocks, rounded up or down per each request; 20,096 bytes is 157 blocks of 128 bytes. In region 6, memory is strictly partitioned, and neither the minimum nor maximum request is honored. Instead, each multicast queue is given a fair share of the queue length so that aggressive bandwidth consumers cannot starve out moderate traffic consumers. In region 7, memory is underprovisioned to allow queues to drain and to avoid starvation that occurs when egress buffer memory fills completely. To display the queue thresholds for video queues:
host1#show qos queue-thresholds egress-slot 9 region 0 region 0 (0MB - 4MB) oversubscription 3330% exceeded length -------33664 67328 5120 33664 conformed length --------67328 134656 10112 67328 committed length --------134656 269184 20096 134656 queue count ----2000 2000 2000 2000 total committed memory --------269312000 538368000 40192000 269312000
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.
304
Meaning
Table 36 on page 305 lists the show qos queue-thresholds command output fields.
Field Description
Name of the queue profile Egress buffer memory region Amount of memory in each region Amount of exceeded traffic that can be queued at this egress memory usage Amount of conformed traffic that can be queued at this egress memory usage Amount of committed traffic that can be queued at this egress memory usage Amount of committed memory allocated to the queue
conformed length
committed length
Related Documentation
Configuring Queue Profiles to Manage Buffers and Thresholds on page 22 show qos queue-thresholds
To display the number of times that a QoS profile references a queue profile:
host1#show queue-profile brief queue-profile default referenced 31 times in qos-profiles
305
Meaning
Table 37 on page 306 lists the show queue-profile command output fields.
Field Description
Name of the queue profile Greater queue length than the length of the conformed or exceeded length A queue length that is less than the committed length but greater than the exceeded length A queue length less than the conformed length which is less than the committed length Percentage of the total queue that can be occupied before conformed packets are dropped Percentage of the total queue that can be occupied before exceeded packets are dropped Weight of the queue
conformed length
exceeded length
conformed fraction
exceeded fraction
buffer weight
Related Documentation
Configuring Queue Profiles to Manage Buffers and Thresholds on page 22 show queue-profile
drop profile ------default drop1 drop2 drop3 drop4 drop5 drop6 drop7 drop8 drop9 drop10 drop11
306
10 10 10 10
0, 0, 0, 0,
0, 0, 0, 0,
0, 0, 0, 0,
Meaning
Table 38 on page 307 lists the show drop-profile command output fields.
Field Description
Name of the drop profile Exponent used to weight the average queue length over time, controlling WRED responsiveness Minimum and maximum committed queue thresholds and maximum drop probability Minimum and maximum conformed queue thresholds and maximum drop probability Minimum and maximum exceeded queue thresholds and maximum drop probability
committed threshold
conformed threshold
exceeded threshold
Related Documentation
307
interface resource rate rate weight -------------------- ---------------------------- ------- ------- ------ethernet Eth9/0 ethernet port wgt 8 ethernet Eth9/0 ethernet queue wgt 8 svlan Eth9/0 svlan 2 svlan node wgt 8 vlan Eth9/0.1 vlan node wgt 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 vlan Eth9/0.3 vlan node wgt 6 vlan Eth9/0.3 vlan queue video 3000000 wgt 8 vlan Eth9/0.3 vlan queue best-effort 8000000 wgt 8 Scheduler hierarchy for traffic-class group EF assured shared rate shaping shaping or interface resource rate rate weight -------------------- ------------------------- ------- ------- ------ethernet Eth9/0 ethernet group node EF wgt 8 svlan Eth9/0 svlan 2 svlan node EF wgt 8 vlan Eth9/0.2 vlan queue EF voice 100000 wgt 8 vlan Eth9/0.3 vlan queue EF voice 300000 wgt 8
To display the scheduler hierarchy from the specified interface down to the port, then up from the specified interface:
host1#show qos scheduler-hierarchy interface fastEthernet 9/0.2 level 0 Scheduler hierarchy for the default traffic-class group assured shared rate shaping shaping or interface resource rate rate weight -------------------- ---------------------------- ------- ------- ------ethernet Eth9/0 ethernet port wgt 8 svlan Eth9/0 svlan 2 svlan node 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 Scheduler hierarchy for the default traffic-class group assured shared rate shaping shaping or interface resource rate rate weight -------------------- ------------------------- ------- ------- ------ethernet Eth9/0 ethernet port wgt 8 ethernet Eth9/0 ethernet group node EF wgt 8 svlan Eth9/0 svlan 2 svlan node EF wgt 8 vlan Eth9/0.2 vlan queue EF voice 100000 wgt 8
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 or interface resource rate rate weight ------------- ---------------------------- ------- ------- -------
308
vlan node vlan queue video 2000000 vlan queue best-effort 6000000
Scheduler hierarchy for traffic-class group EF assured shared rate shaping shaping or interface resource rate rate weight ------------- ------------------------- ------- ------- ------vlan Eth9/0.2 vlan queue EF voice 100000 wgt 8
To display the scheduler hierarchy of a specific traffic-class group or the default traffic-class group:
host1#show qos scheduler-hierarchy interface fastEthernet 9/0 traffic-class-group EF Scheduler hierarchy for traffic-class group EF assured shared rate shaping shaping or interface resource rate rate weight -------------------- ------------------------- ------- ------- ------ethernet Eth9/0 ethernet group node EF wgt 8 svlan Eth9/0 svlan 2 svlan node EF wgt 8 vlan Eth9/0.2 vlan queue EF voice 100000 wgt 8 vlan Eth9/0.3 vlan queue EF voice 300000 wgt 8
To display a summary of the scheduler profiles stacked above the specified interface:
host1#show qos scheduler-hierarchy interface fastEthernet 9/0 summary Total number of nodes: Level 0 nodes: Level 1 nodes: Level 2 nodes: Level 3 nodes: Total number of queues: Level 0 queues: Level 1 queues: Level 2 queues: Level 3 queues: 7 1 2 4 0 8 0 1 0 7
309
Scheduler hierarchy for traffic-class group EF interface resource -------------------- ------------------------ethernet Eth9/0 ethernet group node EF svlan Eth9/0 svlan 2 svlan node EF vlan Eth9/0.2 vlan queue EF voice vlan Eth9/0.3 vlan queue EF voice
To display the scheduler level, scheduler profile that controls QoS behavior of the scheduler nodes and queues, and the burst associated with shaping rates:
host1#show qos scheduler-hierarchy interface fastEthernet 9/0 full | include subscriber-best-effort vlan Eth9/0.1 vlan Eth9/0.2 vlan Eth9/0.3 subscriber-best-effort subscriber-best-effort subscriber-best-effort 2000000 default 6000000 default 8000000 default
To display the QoS scheduler hierarchy using a filter as an alternative to using the level keyword:
host1#show qos scheduler-hierarchy interface fastEthernet 9/0 full | include level 2 vlan Eth9/0.1 vlan node level 2 vlan Eth9/0.2 vlan node level 2 vlan Eth9/0.3 vlan node level 2 svlan Eth9/0 svlan 2 svlan node EF level 2
----------------- ---------------------------- ------- --------- ------ethernet Eth1/0/0 ethernet port superset cluster set vlanset1 vlan Eth1/0/0.1 vlan Eth1/0/0.2 superset node set node vlan queue best-effort vlan queue best-effort 800000000 300000000 wgt 8 wgt 8 wgt 8 wgt 8 wgt 8
Scheduler hierarchy for traffic-class group EF assured shared shaping shaping rate or
310
interface
resource
rate
rate
weight
----------------- ------------------------- --------- ------- ------ethernet Eth1/0/0 ethernet port ethernet Eth1/0/0 superset cluster set vlanset1 ethernet group node EF superset node EF set queue EF EF 100000000 wgt 8 wgt 8 wgt 8 wgt 8
Scheduler hierarchy for traffic-class group AF assured shared shaping interface resource rate shaping rate rate or weight
----------------- ---------------------- --------- ------- ------ethernet Eth1/0/0 ethernet port superset cluster set vlanset1 vlan Eth1/0/0.1 vlan Eth1/0/0.2 superset node AF set node AF vlan queue AF AF vlan queue AF AF 100000000 wgt 8 wgt 8 wgt 8 wgt 8 wgt 8
----------------- ---------------------------- ------- --------- ------ethernet Eth1/0/0 ethernet port superset cluster set vlanset1 vlan Eth1/0/0.1 vlan Eth1/0/0.2 superset node set node vlan queue best-effort vlan queue best-effort 800000000 300000000 wgt 8 wgt 8 wgt 8 wgt 8 wgt 8
311
wgt 8 wgt 8
Scheduler hierarchy for traffic-class group EF assured shared shaping interface resource rate shaping rate rate or weight
----------------- ------------------------- --------- ------- ------ethernet Eth1/0/0 ethernet port ethernet Eth1/0/0 superset cluster set vlanset1 set vlanset2 ethernet group node EF superset node EF set queue EF EF set queue EF EF 100000000 wgt 8 wgt 8 wgt 8 wgt 8 wgt 8
Scheduler hierarchy for traffic-class group AF assured shared shaping interface resource rate shaping rate rate or weight
----------------- ---------------------- --------- ------- ------ethernet Eth1/0/0 ethernet port superset cluster set vlanset1 vlan Eth1/0/0.1 vlan Eth1/0/0.2 set vlanset2 vlan Eth1/0/0.3 superset node AF set node AF vlan queue AF AF vlan queue AF AF set node AF vlan queue AF AF 100000000 wgt 8 wgt 8 wgt 8 wgt 8 wgt 8 wgt 8 wgt 8
Meaning
Table 39 on page 313 lists the show qos scheduler-hierarchy command output fields.
312
Field Description
Type of interface Traffic resource associated with the logical interface Individual shaping rate of a traffic resource in bits per second Configured shared-shaping rate in bits per second Configured assured rate in bits per second or configured weight
Related Documentation
Configuring a Scheduler Hierarchy on page 47 Configuring Simple Shared Shaping on page 77 Configuring Compound Shared Shaping on page 96 Configuring Interface Sets for QoS on page 205 Configuring Interface Supersets for QoS on page 204 show qos scheduler-hierarchy
weight -----8 20 40 8
To display the number of times that a QoS profile references the scheduler profile:
host1#show scheduler-profile brief scheduler-profile default referenced 39 times in qos-profiles scheduler-profile wf100 referenced 1 time in qos-profiles scheduler-profile spSV25 referenced 2 times in qos-profiles
313
host1#show scheduler-profile references scheduler-profile default Referenced by QoS profiles: atm-default serial-default ethernet-default server-default scheduler-profile wf100 Referenced by QoS profiles: ipV610 scheduler-profile spSV25 Referenced by QoS profiles: qospro25
Meaning
Table 40 on page 314 lists the show scheduler-profile command output fields.
Field Description
Name of the scheduler profile Maximum bandwidth, in bits per second, provided to a node or queue Catch-up number associated with the shaper HRR weight of a node or queue Status of strict priority, yes or no Desired bandwidth, in bits per second, provided to a node or queue, or the keyword, hierarchical, to indicate that HAR is used QoS profiles that reference this profile
Related Documentation
Configuring a Scheduler Hierarchy on page 47 Configuring Simple Shared Shaping on page 77 Configuring Compound Shared Shaping on page 96 show scheduler-profile
314
Action
To display information about configured shared shapers for a specific L2TP session:
host1#show qos shared-shaper l2tp-session session1
To display information about 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:
host1#show qos shared-shaper tunnel-server 6/0
Meaning
Table 41 on page 315 lists the show qos shared-shaper command output fields.
Field Description
Type of interface Traffic resource associated with the logical interface Configured shared-shaping rate in bits per second Individual shaping rate of a traffic resource in bits per second Actual current shaping rate in bits per second Total number of shared shapers
315
Field Description
Total number of resource constituents for all shared shapers Total number of shared shapers that are disabled (in failover mode) due to lack of resources
Total number of shared shapers that are disabled (in failover mode) due to lack of resources Compound shared shapers are [not] supported
Indication of whether compound shared shapers are supported; determined by installed hardware
Related Documentation
Configuring a Scheduler Hierarchy on page 47 Configuring Simple Shared Shaping on page 77 Configuring Compound Shared Shaping on page 96 Configuring Interface Sets for QoS on page 205 Configuring Interface Supersets for QoS on page 204 show qos shared-shaper
Action
Meaning
Table 42 on page 316 lists the show qos shared-shaper-control command output fields.
Field Description
Name of the simple shared shaper control Value of the simple shared shaper control; default values are displayed if none specified Expressed units for the value of the simple shared shaper control
units
316
Related Documentation
host1# show egress-queue events interface gigabitEthernet 1/0 committed conformed traffic forwarded drop drop interface class events events events ---------------------- ------- --------- --------- --------ip GigabitEthernet1/0 tc1 132 0 0 tc2 132 132 0 tc3 6 0 132 tc4 0 0 0
To display events for a 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:
host1#show egress-queue events tunnel-server 6/0
To display events for queues only on the specified interface and not stacked above the interface:
host1#show egress-queue events gigabitEthernet 1/0 explicit
To display the sum of events for the queues bound to interfaces that are stacked above the specified interface:
host1#show egress-queue events gigabitEthernet 1/0 summary
To filter output based on the number of events that exceed the specified value.
host1#show egress-queue events gigabitEthernet 1/0 event-exceeding committed host1#show egress-queue events gigabitEthernet 1/0 event-exceeding conformed host1#show egress-queue events gigabitEthernet 1/0 event-exceeding exceeded host1#show egress-queue events gigabitEthernet 1/0 event-exceeding forwarded
Meaning
Table 43 on page 317 lists the show egress-queue events command output fields.
Field Description
Name of the interface
317
Field Description
Name of the traffic class Number of forwarded rate events Number of committed drop events Number of conformed drop events Number of exceeded drop events Time frame during which events are counted (in seconds)
Related Documentation
The VLAN queue that is shared-shaped to 5 Mbps has a maximum rate of 5 Mbps. The VLAN node that is shaped to 8 Mbps has a maximum rate of 8 Mbps. 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:
318
host1# show egress-queue rates brief interface fastEthernet 9/0.2 traffic forwarded aggregate minimum maximum interface class rate drop rate rate rate ---------------------- ----------------------- --------- --------- ------- ------ip FastEthernet9/0.2 best-effort 0 0 25000 1000000 videoTrafficClass 0 0 375000 1000000 multicastTrafficClass 0 0 925000 1000000 internetTrafficClass 0 0 50000 1000000 Total: 0 0 Queues reported: Queues filtered (under threshold): Queues disabled (no rate period): Queues disabled (no resources): Total queues: 4 0 0 0 4
To display rate statistics all of the configured queues, along with the minimum and maximum rates for the queues, even when statistics gathering has not been enabled:
host1#show egress-queue rates full interface atm 11/0 traffic forwarded aggregate minimum maximum interface class rate drop rate rate rate ---------------------- ----------------------- --------- --------------- -----ip ATM11/0.1 best-effort * * 24979 30000000 tc1 0 0 14987510 30000000 tc2 0 0 9991673 30000000 tc3 0 0 4995836 30000000 ip ATM11/0.2 best-effort * * 19980 20000000 tc1 0 0 11988011 20000000 tc2 0 0 7992007 20000000 Queues reported: 5 Queues filtered (under threshold): 0 * Queues disabled (no rate period): 2 **Queues disabled (no resources): 0 Total queues: 7
319
0 0
0 0
0 0
interface --------------------------------svlan GigabitEthernet 11/0 svlan 0 vlan GigabitEthernet 11/0.1 ip GigabitEthernet 11/0.1 vlan GigabitEthernet 11/0.2 ip GigabitEthernet 11/0.2 Queues reported: Queues filtered (under threshold): * Queues disabled (no rate period): **Queues disabled (no resources): Total queues: 5
In the output of this command, the aggregate of all drop ratesWRED, tail, and forwarding eventsis displayed in the aggregate drop rate field. You cannot distinguish among the counters used for different drop rates from the output of this command. As a result, for ES2 10G ADV LMs, you cannot identify the counters used for committed, conformed, and exceeded packet dropping by WRED functionality from the value displayed in this field. View the value displayed for the Dropped by WRED committed field in the output of the show ip interface command to know the cumulative number of committed, conformed, and exceeded packets dropped by WRED for ES2 10G ADV LMs. To display rate statistics for the previous or current rate period:
host1#show egress-queue rates previous interface gigabitEthernet 11/0 svlan 0 host1#show egress-queue rates current interface gigabitEthernet 11/0 svlan 0
To display rate statistics for a 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:
host1#show egress-queue rates tunnel-server 6/0
To display the sum of all rates of queues bound to interfaces that are stacked above the specified interface.
host1#show egress-queue rates interface gigabitEthernet 11/0 svlan 0 summary
To filter output based on the number of queues with rates that exceed the specified value.
320
host1#show egress-queue rates gigabitEthernet 1/0 rate-exceeding committed host1#show egress-queue rates gigabitEthernet 1/0 rate-exceeding conformed host1#show egress-queue rates gigabitEthernet 1/0 rate-exceeding exceeded host1#show egress-queue rates gigabitEthernet 1/0 rate-exceeding forwarded
Meaning
Table 44 on page 321 lists the show egress-queue rates command output fields.
Field Description
Name of the interface Name of the traffic class Statistics for the rate at which packets are enqueued. In some time periods, the enqueue rate might exceed the dequeue rate. This can occur when a burst of traffic arrives at a queue which might be dequeuing at a slower rate because of a shaper or congestion. In other time periods, the enqueue rate might be less than the dequeue rate. This can occur when a buffered burst of packets are being dequeued, and no new packets are arriving at the queue.
aggregate drop rate committed drop rate conformed drop rate exceeded drop rate minimum rate maximum rate Queues reported Queues filtered (under threshold)
Total number of all drop rates Drop rate for green packets Drop rate for yellow packets Drop rate for red packets Minimum rate for queue Maximum rate for queue Number of queues reported Number of queues not reported because they are under the threshold Number of queues not displayed because statistics gathering is disabled (that is, the referenced statistics profile does not have a rate period set) Number of queues not displayed because no resources were available Total number of queues within the hierarchical scope of the command
Total queues
321
Related Documentation
Configuring Rate Statistics on page 39 For more information about the assured rate, see Configuring an Assured Rate for a Scheduler Node or Queue on page 54 show egress-queue rates
To display detailed information about the fabric queue in a specific traffic class:
host1#show fabric-queue traffic-class video detail
Meaning
Table 45 on page 322 lists the show fabric-queue command output fields.
Field Description
Name of the traffic class Egress slot for which statistics are being displayed Type of packet Number of forwarded packet Number of forwarded bytes Number of dropped packets Number of dropped bytes
Related Documentation
Configuring Rate Statistics on page 39 Configuring Event Statistics on page 40 show fabric-queue
322
To display the number of times that a QoS profile references the statistics profile:
host1#show statistics-profile rates1 brief
Meaning
Table 46 on page 323 lists the show statistics-profile command output fields.
Field Description
Name of the statistics profile Threshold above which forwarded-rate-exceeded events are counted Threshold above which committed-drop-events are counted Threshold above which conformed-drop-events are counted Threshold above which exceeded-drop-events are counted Time frame during which statistics are gathered
rate period
Related Documentation
Configuring Rate Statistics on page 39 Configuring Event Statistics on page 40 show statistics-profile
323
Action
scheduler profile -----------default default default default default strictShaper default default default default default default default
queue profile ------default default default default default default default default default default default default default
To display the interface hierarchy for a 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:
host1#show qos interface-hierarchy tunnel-server 6/0
Meaning
Table 47 on page 324 lists the show qos interface-hierarchy command output fields.
Field Description
Interface for which the hierarchy is being displayed Name of the QoS profile and its attachment point Traffic-class groups associated with the interface Type of interface to which the profile is attached
324
Field Description
Queue, node, group, or shadow node Name of the traffic class associated with the queue Scheduler profiles associated with the interface Queue profiles associated with the interface
Related Documentation
Configuring a QoS Profile on page 126 Attaching a QoS Profile to an Interface on page 128 Creating Parameter Instances on page 231 Configuring Interface Sets for QoS on page 205 Configuring Interface Supersets for QoS on page 204 show qos interface-hierarchy
Meaning
Related Documentation
Configuring a QoS Profile on page 126 Attaching a QoS Profile to an Interface on page 128 Creating Parameter Instances on page 231 Example: Port-Type QoS Profile Attachment on page 133 show qos-port-type-profile
325
This command displays groups, nodes, and queues, in that order, according to the following sequence:
not members of a traffic-class group members of the strict-priority traffic-class group members of an extended traffic-class group in the order of configuration
Action
host1# show qos-profile qpDiffServExample1 qos-profile qpDiffServExample1: interface rule traffic t-class group type type class -------------------- --------- ----- ----------ip queue tc3 ip queue tc4 ip queue tc5 expedited-forwarding ethernet group expedited-forwarding ip node expedited-forwarding ip queue voice best-effort ethernet group best-effort ip node best-effort ip queue best-effort assured-forwarding ethernet group assured-forwarding ip node assured-forwarding ip queue video
scheduler profile --------------best-effort best-effort best-effort expeditedGroup default voice bestEffortGroup default best-effort assuredGroup default video
To display information about the QoS profiles attached to an interface or port type:
host1# show qos-profile references interface fastEthernet 9/0 202 qos profile attachment -------------------------------- -------------------------------------------atm-default (qos-port-type-profile) serial-default (qos-port-type-profile) ethernet-default (qos-port-type-profile) server-default (qos-port-type-profile) lag-default (qos-port-type-profile) subscriber-data-service vlan FastEthernet9/0.1 subscriber-triple-play vlan FastEthernet9/0.2 subscriber-triple-play vlan FastEthernet9/0.3 Port attachments: 4 Interface attachments: 3 DCM Profile attachments: 0 Not attached: 0
To display the number of times the QoS profile is referenced by an interface or protocol profile:
host1#show qos-profile brief qos-profile atm-default referenced by 1 attachment qos-profile serial-default referenced by 1 attachment qos-profile ethernet-default referenced by 1 attachment qos-profile server-default referenced by 1 attachment qos-profile lag-default referenced by 1 attachment
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:
326
To display information about the QoS profiles attached to a specific L2TP session:
host1#show qos-profile references l2tp-session session1
To display attachments for QoS profiles only on the specified interface and not QoS profiles stacked above the interface:
host1#show qos-profile references interface gigabitEthernet 6/0 explicit
Meaning
Table 48 on page 327 lists the show qos-profile command output fields.
Field Description
Name of QoS profile Name of the traffic-class group associated with the interface Type of interface Whether the rule is a group node, scheduler node, queue, or shadow node Name of the traffic class associated with the interface Name of the scheduler profile associated with the interface Name of the queue profile associated with the interface Name of the drop profile associated with the interface Name of the statistics profile associated with the interface Type of interface or port type to which the QoS profile is attached Number of QoS profiles attached to port types Number of QoS profiles attached to profiles for Service Manager Number of QoS profiles attached to interfaces Number of QoS profiles that are unattached
queue profile
attachment
327
Related Documentation
Configuring a QoS Profile on page 126 Attaching a QoS Profile to an Interface on page 128 Creating Parameter Instances on page 231 show qos-profile
Action
Meaning
Table 49 on page 328 lists the related show interfaces atm command output fields.
Field Description
Per-port queuing mode status: disabled, low-latency, low-cdv, none Per-port queuing mode status: disabled, low-latency, low-cdv, none
Operational qos-mode-port
328
Field Description
Configured shaping mode for the interface:
disabledShaping mode is configured but disabled. frameDefault shaping mode for shaping and policing rates. Reports statistics such as transmitted bytes and dropped bytes based on bytes within frames. cellShaping mode for shaping and policing rates is cell-based; resulting traffic stream conforms exactly to the policing rates configured in downstream devices. Reports statistics in bytes within cells and also accounts for cell encapsulation and padding overhead. noneShaping mode is not configured.
Operational qos-shaping-mode
Actual shaping mode for the interface. The router determines the operational shaping mode based on the values configured for the qos-shaping-mode command or the qos-port-mode command. For more information, see Per-Packet Queuing on the SAR Scheduler Overview on page 157.
disabledShaping mode is configured but disabled. frameDefault shaping mode for shaping and policing rates. Reports statistics such as transmitted bytes and dropped bytes based on bytes within frames. cellShaping mode for shaping and policing rates is cell-based; resulting traffic stream conforms exactly to the policing rates configured in downstream devices. Reports statistics in bytes within cells and also accounts for cell encapsulation and padding overhead. noneShaping mode is not configured.
QoS profile attachment at or below the displayed interface. For example, if the interface being displayed is a VC, and the attachment is at the ATM AAL5 interface, the ATM AAL5 interface attachment is displayed.
Related Documentation
Configuring the QoS Shaping Mode for ATM Interfaces on page 169 Configuring a QoS Profile on page 126 Attaching a QoS Profile to an Interface on page 128 Creating Parameter Instances on page 231 For more information about other fields displayed with this command, see JunosE Link Layer Configuration Guide show atm interface
329
show interfaces
However, if the profile is configured statically, the QoS profile is attached to the ATM subinterface, and the attachment is displayed by the show atm subinterface command rather than show ip interface. Action To display the QoS configuration for an IP interface:
host1#show ip interface atm 2/0.1 ATM2/0.1 line protocol Atm1483 is up, ip is up .......................................... Attached QoS profile: test @ ATM2/0 queue 0: traffic class best-effort, bound to ip ATM2/0.1 Queue length 0 Bytes Forwarded packets 0, Bytes 0 Dropped committed packets 0, Bytes 0 Dropped conformed packets 0, Bytes 0 Dropped exceeded packets 0, Bytes 0 Dropped by WRED committed packets 0, bytes 0 Dropped by WRED conformed packets 0, bytes 0 Dropped by WRED exceeded packets 0, bytes 0 Average queue length 150576 bytes queue 1: traffic class tc1, bound to ip ATM2/0.1 Queue length 0 Bytes Forwarded packets 0, Bytes 0 Dropped committed packets 0, Bytes 0 Dropped conformed packets 0, Bytes 0 Dropped exceeded packets 0, Bytes 0 Dropped by WRED committed packets 0, bytes 0 Dropped by WRED conformed packets 0, bytes 0 Dropped by WRED exceeded packets 0, bytes 0 Average queue length 150576 bytes
Meaning
Table 50 on page 330 lists the related show ip interface command output fields.
Field Description
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.
330
Field Description
Number of the queue for which statistics are being displayed and whether the queue is under traffic class control Name of traffic class Interface to which queue is bound Size of queue in length and bytes Number of forwarded packets and bytes Number of committed packets and bytes dropped Number of conformed packets and bytes dropped Number of exceeded packets and bytes dropped Number of committed packets and bytes dropped by WRED Displays a cumulative number of committed, conformed, and exceeded packets dropped by WRED for ES2 10G ADV LMs.
traffic class bound to Queue length Forwarded Dropped committed Dropped conformed Dropped exceeded Dropped by WRED committed
Number of conformed packets and bytes dropped by WRED Displays a value of zero for ES2 10G ADV LMs because of the single counter used to calculate packets dropped by WRED functionality (as an aggregate of all colors) for these LMs.
Number of exceeded packets and bytes dropped by WRED Displays a value of zero for ES2 10G ADV LMs because of the single counter used to calculate packets dropped by WRED functionality (as an aggregate of all colors) for these LMs.
Related Documentation
Configuring a QoS Profile on page 126 Attaching a QoS Profile to an Interface on page 128 Creating Parameter Instances on page 231 show ip interface
331
Monitoring the QoS Configuration of Fast Ethernet, Gigabit Ethernet, and 10-Gigabit Ethernet Interfaces
Purpose Display information about the QoS configuration for a specific Fast Ethernet, Gigabit Ethernet, or 10-Gigabit Ethernet interface. To display the QoS configuration for a Fast Ethernet interface:
host1#show interfaces fastEthernet 6/0 GigEthernet6/0 is Up, Administrative status is Up Hardware is Intel 21440, address is 0090.1a40.5508 MAU is 100BASE-TX MTU: Operational 1522, Administrative 1522 Duplex Mode: Operational Full Duplex, Administrative Auto Negotiate Speed: Operational 100 Mbps, Administrative Auto Negotiate 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec In: Bytes 0, Unicast 0 Multicast 0, Broadcast 0 Errors 0, Discards 0, Mac Errors 0, Alignment 0 CRC 0, Too Longs 0, Symbol Errors 0 Out: Bytes 64, Unicast 0 Multicast 0, Broadcast 1 Errors 0, Discards 0, Mac Errors 0, Deferred 0, No Carrier 0 Collisions: Single 0, Multiple 0, Late 0, Excessive 0 Administrative qos-shaping-mode: cell Operational qos-shaping-mode: cell Attached QoS profile: ss
Action
Meaning
Table 51 on page 332 lists the related show interfaces command output fields.
Field Description
Configured shaping mode for the interface:
disabledShaping mode is configured but disabled. frameDefault shaping mode for shaping and policing rates. Reports QoS statistics such as transmitted bytes and dropped bytes based on bytes within frames. cellShaping mode for shaping and policing rates is cell-based; resulting traffic stream conforms exactly to the policing rates configured in downstream devices. Reports statistics in bytes within cells and also accounts for cell encapsulation and padding overhead. noneShaping mode is not configured.
332
Field Description
Actual shaping mode for the interface. The router determines the operational shaping mode based on the value configured using the qos-shaping-mode command. For more information, see QoS Shaping Mode for Ethernet Interfaces Overview on page 172.
disabledShaping mode is configured but disabled. frameDefault shaping mode for shaping and policing rates. Reports QoS statistics such as transmitted bytes and dropped bytes based on bytes within frames. cellShaping mode for shaping and policing rates is cell-based; resulting traffic stream conforms exactly to the policing rates configured in downstream devices. Reports statistics in bytes within cells and also accounts for cell encapsulation and padding overhead. noneShaping mode is not configured.
QoS profile attachment at or below the displayed interface. For example, if the interface being displayed is a VLAN subinterface, and the attachment is at the Gigabit Ethernet interface, the Gigabit Ethernet attachment is displayed.
Related Documentation
Configuring the QoS Shaping Mode for Ethernet Interfaces on page 173 Creating Parameter Instances on page 231 For more information about other fields displayed with this , see JunosE Physical Layer Configuration Guide show interfaces
Monitoring the QoS Configuration of IEEE 802.3ad Link Aggregation Group Bundles
Purpose Display information about the QoS configuration for Ethernet member links in all IEEE 802.3ad link aggregation group (LAG) bundles configured on the router, or about the member links in a specified IEEE 802.3ad LAG bundle. To display the QoS configuration for a specific LAG bundle:
host1#show interfaces lag lg0 members Lag lg0 is Up, Administrative status is Up MAC Address is 0090.1a40.01be MTU: Operational 1526 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
Action
333
Member-interface FastEthernet11/2 is Up (LACP disabled, state collecting/distributing) Member-interface FastEthernet11/3 is Down (LACP disabled, state waiting) Member-interface FastEthernet11/4 is Up (LACP disabled, state collecting/distributing)
Meaning
Table 52 on page 334 lists the related show interfaces lag memberscommand output fields.
Field Description
Name of the LAG bundle QoS parameter instance at the displayed interface QoS profile attachment at the displayed interface
Related Documentation
Configuring the Scheduler Hierarchy for Hashed Load Balancing in 802.3ad Link Aggregation Groups on page 184 Configuring the Scheduler Hierarchy for Subscriber Load Balancing in 802.3ad Link Aggregation Groups on page 185 Creating Parameter Instances on page 231 For more information about other fields displayed with this command, see the JunosE Physical Layer Configuration Guide show interfaces lag members
334
Meaning
Table 53 on page 335 lists the show qos-interface-set command output fields.
Field Description
Name of the interface set Name of the interface superset that is the parent of the interface set Interface that is the parent of the interface superset Member-interface type defined for the interface set:
vlan ip vlan
Restricted interface configured for this interface set List of interface members associated with the interface superset
Related Documentation
Meaning
Table 54 on page 336 lists the show qos-interface-superset command output fields.
335
Field Description
Name of the interface superset Interface that is the parent of the interface superset Number of interface members associated with the interface superset Restricted interface configured for this interface superset List of interface set members associated with the interface superset
restricted interface
Children
Related Documentation
Action
Meaning
Table 55 on page 336 show aaa qos downstream-rate command output fields.
Field Description
Status of the QoS downstream rate application: enabled or disabled
Related Documentation
Configuring a Parameter Definition for QoS Downstream Rate on page 289 show aaa qos downstream-rate
336
host1#show qos-parameter max-subscriber-bw references interface parameter name value --------- ----------------- ------global max-subscriber-bw 5000000 ATM11/0.1 max-subscriber-bw 6000000 Global parameter instances: Parameter instances reported: 1 2
To display the QoS profile name and attachment data for a specific interface:
host1#show qos-parameter references interface fastEthernet 9/0.3 interface parameter name value ----------------- ------------------------------ ------FastEthernet9/0.3 max-subscriber-bandwidth 8000000 subscriber-weight 6 max-subscriber-video-bandwidth 3000000 max-100Kbps-voice-calls 3 Explicit parameter instances: Hierarchical parameter instances: IP multicast parameter instances: Parameter instances reported: 4 0 0 4 instance Type -------explicit explicit explicit explicit
337
To display information about the parameter instances 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:
host1#show qos-parameter references tunnel-server 6/0
To display parameter instances only on the specified interface and not QoS parameters stacked above the interface:
host1#show qos-parameter references gigabitEthernet 6/0 explicit
Meaning
Table 56 on page 338 lists the show qos-parameter command output fields.
Field Description
Location of the interface to which the parameter instance is assigned; global indicates that the parameter is assigned to the chassis Name of the parameter instance Value assigned to the parameter instance Source of the parameter instance:
dcmParameter instance was created in a profile radiusParameter instance was created through RADIUS service managerParameter instance was created through Service Manager defaultParameter instance was created through the CLI or SNMP
Number of references of this parameter instance created through Service Manager Status of the persistence of a parameter instance in the system:
persistence
persistentParameter instance is stored in NVS and is restored after a chassis reset non-persistentParameter instance is not stored in NVS and are deleted after a chassis reset
Number of parameter instances assigned to the chassis Total number of parameter instances assigned
338
Field Description
Total number of explicit parameter instances assigned Total number of hierarchical parameter instances assigned Total number of parameter instances associated with the IP multicast bandwidth adjustment application
Related Documentation
Meaning
Table 57 on page 339 lists the show qos-parameter-define command output fields.
Field Description
Name of the parameter definition Types of controlled-interface types that are available for the parameter definition Types of instance-interface types that are available for the parameter definition
339
Field Description
Types of subscriber-interface types that are available for the parameter definition Range assigned to the parameter definition Applications and hierarchical settings assigned to the parameter definition
Related Documentation
Configuring a Basic Parameter Definition for QoS Administrators on page 227 show qos-parameter-define
340
CHAPTER 32
Troubleshooting QoS
This chapter provides information for troubleshooting QoS. QoS topics are discussed in the following sections:
Troubleshooting Memory and Processor Use for Egress Queue Rate Statistics and Events on page 341
Troubleshooting Memory and Processor Use for Egress Queue Rate Statistics and Events
Problem The E Series Broadband Services Routers uses shared processing and memory when it gathers egress queue rate statistics and events. If sufficient memory is not available, the statistics gathering is temporarily disabled and the queues are considered to be in failover mode until memory becomes available. The router displays a CLI message whenever queues are put into failover mode and when they recover from failover mode.
NOTE: When an extremely large number of statistics is being gathered over a short period of time, the router might release the processor to perform more important tasks. This can result in longer rate periods than you have configured. For example, if you configured 10,000 queues to gather statistics every second on a line module, the router might actually lengthen the rate to 2 seconds or more.
Solution
To display the number of queues that are disabled because of no resources, issue the show egress-queue rates command.
Related Documentation
Monitoring Forwarding and Drop Rates on the Egress Queue on page 318 show egress-queue rates
341
342
PART 8
Index
343
344
Index
Symbols
10-Gigabit Ethernet monitoring......................................................................332 10-Gigabit Ethernet forwarding ASIC (TFA)..............................................................69, 95, 122, 143 802.3ad link aggregation configuring for QoS.......................................................177 link redundancy and QoS..........................................178
B
backpressure...................................................................154, 161 default integrated mode.............................................161 low-cdv mode.................................................................161 low-latency mode.........................................................161 best effort...............................................................................5, 13 best-effort queue......................................................................5 best-effort scheduler node....................................................5 buffer-weight command......................................................23 burst size, setting in a shaping rate.................................60 byte adjustment application configuration example...............................................273 byte adjustment applications overview..........................................................................279
A
aaa qos downstream-rate command.........................290 Access Node Control Protocol. See ANCP ADSL traffic managing cell tax........................................................279 ANCP (Access Node Control Protocol) shaping downstream rates from.................287, 289 ASIC scheduler...........................................................................3 assured rate.................................................................................5 assured-rate command......................................................227 ATM (Asynchronous Transfer Mode) cell shaping....................................................................158 configuration guidelines for QoS.............................161 configuring for QoS.....................................................156 configuring the integrated scheduler....................153 frame shaping...............................................................158 monitoring......................................................................328 monitoring for QoS......................................................170 SAR shaping....................................................................161 shaping for QoS............................................................158 atm commands atm vp-tunnel ......................................................163, 167 atm-vp qos-parameter..............................................231 atm-vp qos-profile......................................................128 ATM modules with relative strict priority......................60 minimizing latency on the SAR................................60 oversubscribing..............................................................60 ATM SAR shaping, QoS........................................................161 ATM VP interface attachments................................................128 audience for QoS.......................................................................4
C
CDV (cell delay variation)......................................................5 CDVT (cell delay variation tolerance)......................5, 158 cell byte-adjustment application configuring.....................................................................283 cell delay variation tolerance. See CDVT cell delay variation. See CDV clear egress-queue command............................................41 clear fabric-queue command............................................42 clearing statistics.....................................................................41 color-based thresholds.........................................................18 committed drop threshold...................................................37 committed-drop-threshold command..........................40 committed-length command............................................23 committed-threshold command................................27, 31 compound shared shaping. See shared shaping configuration examples Diffserv..............................................................................137 QoS parameters.........................................232, 251, 261 QoS profiles....................................................................133 configuring. See specific feature, product, or protocol conformed drop threshold...................................................37 conformed-drop-threshold command...........................41 conformed-fraction command..........................................23
345
conformed-length command............................................23 conformed-threshold command................................27, 31 constituents, shared-shaping............................................70 controlled-interface-type command...........................228 controlling subscriber bandwidth configuration example......................................232, 251 conventions notice icons...................................................................xxvii text and syntax...........................................................xxviii convergence-factor command.........................................89 customer support.................................................................xxix contacting JTAC...........................................................xxix
Fast Ethernet monitoring......................................................................332 forwarding classes. See traffic classes forwarding rate threshold.....................................................37 forwarding-rate-threshold command............................40 frame byte adjustment application configuring.....................................................................285 frame forwarding ASIC (FFA).....................................96, 121
G
Gigabit Ethernet monitoring......................................................................332 group command............................................................127, 227 group node...................................................................................6
D
DiffServ configuration example................................................137 networks...............................................................................3 documentation set comments on................................................................xxix drop profile................................................................................25 configuration examples for RED.......................28, 29 configuration examples for WRED..........................32 configuring RED...............................................................27 configuring WRED.........................................................30 RED (random early detection).................................26 dynamic shaping of traffic...................................................67
H
HAR (hierarchical assured rate)..........................................6 hierarchical assured rate. See HAR hierarchical round-robin. See HRR hierarchy, QoS scheduler..............................................6, 307 HRR (hierarchical round-robin)....................................6, 57 HRR scheduler...............................................................153, 156 relative strict priority on.......................................58, 60
I
implicit constituents selection for compound shared shaping............105 selection for simple shared shaping.....................105 instance-interface-type command...............................228 integrated scheduler configuring for QoS......................................................153 interface profile attachments...................................................................128 IP multicast bandwidth adjustment configuration example...............................................261 configuring.....................................................................259 overview...........................................................................257
E
effective weight.........................................................................6 egress forwarding ASIC (EFA)....................................95, 121 Ethernet 802.3ad link aggregation and QoS.........................177 configuring for QoS..............................................172, 177 overview for QoS............................................................171 QoS shaping mode.......................................................172 Ethernet link aggregation commands member-interface.......................................................185 event statistics........................................................................40 exceeded drop threshold......................................................37 exceeded-drop-threshold command..............................41 exceeded-fraction command............................................23 exceeded-length command...............................................23 exceeded-threshold command...................................27, 31 expressions......................................................................48, 225
L
L2TP (Layer 2 Tunneling Protocol) calculating the transmit connect speed.............195 configuring for QoS.......................................................191 monitoring for QoS......................................................196 overview for QoS..........................................................189 L2TP sessions QoS....................................................................................189 latency...........................................................................................6 layer 2 control. See ANCP
F
fabric-strict-priority command..........................................15 fabric-weight command.......................................................15
346
Index
load balancing configuring parameters.............................................186 hashed configuring.............................................................184 overview..........................................................177, 179 munged QoS profiles..................................................178 subscriber configuring.............................................................185 enabling default configuration.......................185 overview..........................................................177, 180 load-rebalance command.......................................186, 188
Q
QoS (quality of service) administrators of......................................................4, 215 clients of......................................................................4, 215 description of.....................................................................3 differentiated services assured forwarding.................................................3 expedited forwarding.............................................3 extends Diffserv................................................................3 features.................................................................................7 overview...............................................................................3 parameters......................................................................215 terms.....................................................................................5 QoS cell mode application configuration example...............................................273 configuring......................................................................272 overview..........................................................................269 QoS commands qos-mode-port .............................................................157 qos-parameter ..............................................................231 qos-parameter-define ..............................................227 qos-port-type-profile .......................................130, 185 qos-profile ..............39, 40, 52, 63, 126, 130, 146, 184, 185, 191 qos-shaping-mode ...................................156, 169, 173 qos-shared-shaper-control command................89 QoS downstream rate application configuring.....................................................................289 overview..........................................................................287 relationship with QoS cell mode...........................270 QoS interface sets terms...............................................................................200 QoS parameters 802.3ad link aggregation...........................................178 audience...........................................................................215 configuration examples...........................232, 251, 261 configuring for QoS administrators.......................219 configuring for QoS clients......................................229 overview...........................................................................215
M
manuals comments on................................................................xxix maximum-voql command.................................................90 minimum-dynamic-rate-percent command..............90 monitoring. See specific feature, product, or protocol multiple traffic-class groups...............................................14 munged QoS profile attachments....................................................................131 Ethernet link aggregation..........................................178
N
node command.........53, 64, 127, 146, 184, 185, 195, 227 nodes best-effort scheduler......................................................5 group.....................................................................................6 scheduler.............................................................................6 system resources...........................................................121 notice icons............................................................................xxvii
O
operational QoS shaping mode......................................158
P
packet fragmentation, managing..................................285 parameters.......................................249, 257, 269, 279, 287 See also QoS parameters phantom nodes......................................................................143 port shaping...............................................................................51 port-type profile, QoS.............................................................6 attachments..................................................................130
347
parameter definitions assured rate...................................................48, 225 cell byte adjustment................................279, 283 configuring.............................................................227 expressions....................................................48, 225 frame byte adjustment..........................280, 285 IP multicast bandwidth adjustment..............................................257, 259 overview..................................................................219 QoS cell mode............................................269, 272 QoS downstream rate............................287, 289 referencing scheduler profiles........................225 shaping rate...................................................48, 225 shared-shaping rate...................................48, 225 parameter instances configuring for an interface..............................231 configuring for QoS clients.............................229 configuring globally.............................................231 overview.................................................................229 relationship with other profiles................................217 terminology.....................................................................216 using with Service Manager............................215, 232 QoS profile ATM VP attachments.................................................128 attaching..........................................................................128 configuring......................................................................126 interface attachments................................................128 monitoring.......................................................................149 munged.....................................................................131, 178 munged attachments..................................................131 overview............................................................................121 port-type attachments..............................................130 rules illustrated.............................................................140 S-VLAN attachments.................................................129 using with Service Manager.....................................126 QoS shaping mode configuring..............................................................169, 173 overview............................................................................172 qos-profile command.........................................................227 queue bandwidth....................................................................57 queue buffers....................................................................20, 24 queue command...............64, 127, 146, 184, 185, 191, 227 queue length.....................................................................20, 24 queue profiles............................................................................17 color-based thresholds................................................18 configuring........................................................................22 monitoring.........................................................................24 overview..............................................................................17 queue-profile command......................................................23
R
random early detection. See RED range command...................................................................228 rate shaping...............................................................................51 QoS........................................................................................6 rate statistics.............................................................................37 rate-period command...................................................39, 40 reaction-factor command..................................................89 RED (random early detection)......................................6, 25 and dynamic queue thresholds................................33 configuration examples........................................28, 29 configuring.........................................................................27 configuring average queue length...........................28 configuring color blind RED........................................29 configuring colored RED..............................................28 how it works.....................................................................26 monitoring.........................................................................35 relative strict-priority scheduling configuration example.................................................59 configuring........................................................................58 on ATM modules............................................................60 minimizing latency on the SAR.......................60 oversubscribing.....................................................60 setting burst size in shaping rate.............................60 shaping rate for nonstrict queues...........................60 tuning latency on strict-priority queues................63 zero-weight queues......................................................60
S
S-VLAN interface attachments................................................129 SAR (segmentation and reassembly) scheduler.....................................................................153, 156 strict-priority on..............................................................59 scheduler hierarchy.......................................................................6, 46 HRR....................................................................................153 node, best-effort best-effort scheduler.............................................5 profile........................................................................45, 225 configuring...............................................................47 SAR....................................................................................153 scheduler hierarchy monitoring......................................................................307 scheduler map. See QoS profile scheduler-profile command.............................48, 191, 227
348
Index
scheduling monitoring........................................................................117 shadow nodes configuration examples different traffic-class group............................148 same traffic-class group..................................148 VLAN and IP queues...........................................147 configuring......................................................................146 interface types...............................................................126 overview...........................................................................143 system resources..........................................................145 shadow-node command...................................................146 shapeless tunnel..........................................................165, 168 shaping using expressions for..........................................48, 225 shaping mode configuring..............................................................169, 173 overview............................................................................172 shaping rate for nonstrict queues.....................................................60 setting burst size in.......................................................60 shaping, QoS ATM................................................................158 cell......................................................................................158 frame.................................................................................158 shaping-rate command......................................................227 shared shaping active constituents........................................................70 compound........................................................................95 active constituents.............................................103 configuration..........................................................96 configuration example, VC shared shaping.................................................................98 configuration example, VP shared shaping...............................................................100 configuration limitations....................................70 hardware dependency........................................95 considerations.................................................................70 constituents.....................................................................70 active..........................................................................70 comparison of explicit and implicit..............103 inactive....................................................................103 explicit constituents example.....................................................................111 example of weighted...........................................112 selection...........................................................103, 111 implicit constituents example at best-effort node..........................105 example at best-effort queue........................106 example for mixed interface types...............107
selection.................................................................103 selection for compound...................................105 selection for simple............................................105 inactive constituents..................................................103 individual shaping and.................................................70 limiting bandwidth........................................................69 low-CDV mode.................................................................71 on the SAR, limitations of............................................71 overview.....................................................................67, 69 simple.................................................................................75 active constituents.............................................103 configuration............................................................77 configuration example, Ethernet.....................82 configuration example, VC shared shaping.................................................................79 configuration example, VP shared shaping..................................................................81 controlling the algorithm...................................85 example, basic........................................................75 example, on best-effort scheduler node.......................................................................75 traffic starvation..............................................................72 types, simple versus compound..............................69 shared-shaping-constituent command........................115 shared-shaping-rate command.......................78, 96, 227 show commands show aaa qos downstream-rate...........................336 show atm interface.....................................................328 show drop-profile.......................................................306 show egress-queue events ......................................317 show egress-queue rates .........................................318 show fabric-queue .....................................................322 show interfaces gigabitEthernet............................332 show interfaces lag members................................333 show interfaces tenGigabitEthernet....................332 show qos-parameter.................................................336 show qos-parameter-define .................................339 show qos-port-type profile ....................................325 show qos-profile..........................................................325 show qos-shared-shaper-control command...................................................................316 show queue-profile ...................................................305 show scheduler-profile ..............................................313 show statistics-profile ..............................................323 show traffic-class.......................................................300 show traffic-class-group ..........................................301 show qos commands show qos interface-hierarchy.................................324 show qos queue-thresholds ..................................302
349
show qos scheduler-hierarchy...............................307 show qos shared-shaper ..........................................314 simple shared shaping. See shared shaping statistics ATM....................................................................................158 statistics profile........................................................................37 clearing................................................................................41 committed drop threshold..........................................37 conformed drop threshold..........................................37 event statistics................................................................37 exceeded drop threshold.............................................37 failover mode.................................................................341 forwarding rate threshold............................................37 maximum..........................................................................37 monitoring.........................................................................42 overview.............................................................................37 rate period..........................................................37, 39, 40 rate statistics....................................................................37 resource use...................................................................341 thresholds.........................................................................40 statistics-profile command................................................39 strict-priority command.......................................................64 strict-priority scheduling...............................................57, 59 true versus relative........................................................59 See also relative strict-priority scheduling subscriber-interface-type command...........................228 support, technical See technical support svlan commands svlan qos-parameter..................................................232 svlan qos-profile...........................................................129
V
variables configuring for shared shaping.................................85 VDSL traffic managing packet fragmentation for....................285
W
weight command..........................................................56, 227 weight, QoS..................................................................................7 weighted random early detection. See WRED WRED (weighted random early detection)..............7, 25 configuration examples...............................................32 configuring........................................................................30 different drop behavior for each queue.....................................................................32 different treatment of colored packets..................................................................32 how it works.....................................................................26 monitoring.........................................................................35
Z
zero-weight queues...............................................................60
T
TCP friendly................................................................................51 technical support contacting 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, 191, 228 traffic-class groups monitoring.........................................................................16 multiple...............................................................................14 overview..............................................................................14 traffic-class-group command............................................15 triple play configurations...........................................98, 233
350