Juniper Networks
Log in
|
How to Buy
|
Contact Us
|
United States (Change)
Choose Country
Close

Choose Country

North America

  • United States

Europe

  • Deutschland - Germany
  • España - Spain
  • France
  • Italia - Italy
  • Россия - Russia
  • United Kingdom

Asia Pacific

  • Asean Region (Vietnam, Indonesia, Singapore, Malaysia)
  • Australia
  • 中国 - China
  • India
  • 日本 - Japan
  • 대한민국 - Korea
  • 台灣 - Taiwan
Solutions
Products & Services
Company
Partners
Support
Education
Community
Security Intelligence Center

Technical Documentation

Support
Technical Documentation
Content Explorer New
 
Enterprise MIBs
 
EOL Documentation
 
Feature Explorer Login required New
 
File Format Help
 
Glossary
 
Portable Libraries
 
 
Home > Support > Technical Documentation > JunosE Software > traffic-class-group
Print
Rate and give feedback:  Feedback Received. Thank You!
Rate and give feedback: 
Close
This document helped resolve my issue.  Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  
E-mail: 
Submitting...
 

Related Documentation

  • Configuring Traffic Classes That Define Service Levels
  • Configuring Traffic-Class Groups That Define Service Levels
  • Configuring QoS for an L2TP Session
 

traffic-class-group

Syntax

[ no ] traffic-class-group trafficClassGroupName
[ slot slotNumber | auto-strict-priority | extended ]

Release Information

Command introduced before JunosE Release 7.1.0.

Description

Configures a traffic-class group. The no version deletes the selected traffic-class group. You must remove all local (slot-based) instances of a traffic-class group before you can remove the global group.

Options

  • trafficClassGroupName—Name of the traffic class group; up to 31 characters
  • slotNumber—Number of the slot associated with the group, in the range 0—17
  • auto-strict-priority—Specifies strict-priority scheduling for the group, regardless of whether the scheduler profile associated with the group node specifies strict-priority scheduling. Only one auto-strict-priority group can exist; this is the default behavior for a group.
  • extended—Specifies that strict-priority scheduling for the group is determined by the scheduler profile associated with the group node; scheduling is either hierarchical round-robin or strict priority, but if a strict-priority traffic-class group already exists, this group must scheduled via HRR

Mode

Global Configuration

 

Related Documentation

  • Configuring Traffic Classes That Define Service Levels
  • Configuring Traffic-Class Groups That Define Service Levels
  • Configuring QoS for an L2TP Session
 

Published: 2012-06-29

 
  • About Juniper
  • Investor Relations
  • Press Releases
  • Newsletters
  • Juniper Offices
  • Green Networking
  • Resources
  • How to Buy
  • Partner Locator
  • Image Library
  • Visio Templates
  • Security Center
  • Community
  • Forums
  • Blogs
  • Junos Central
  • Social Media
  • Developers
  • Support
  • Technical Documentation
  • Knowledge Base (KB)
  • Software Downloads
  • Product Licensing
  • Contact Support
Site Map / RSS Feeds / Careers / Accessibility / Feedback / Privacy & Policy / Legal Notices
Copyright© 1999-2012 Juniper Networks, Inc. All rights reserved.
Help
|
My Account
|
Log Out