Log in
|
How to Buy
|
Contact Us
|
United States (Change)

## 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

Remember my choice

# Technical Documentation

Download Software
Research a Problem
Case Management
Contract & Product Management
Technical Documentation
Documentation Archive
Enterprise MIBs
File Format Help
Glossary
Portable Libraries
End-of-Life Products
Contact Support
Guidelines and Policies
Security Resources
Rate and give feedback: Feedback Received. Thank You!
Rate and give feedback:
This document helped resolve my issue. Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:
E-mail:

## 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: 2011-10-04

Site Map / RSS Feeds / Careers / Accessibility / Feedback / Privacy & Policy / Legal Notices
Copyright© 1999-2011 Juniper Networks, Inc. All rights reserved.
Help
|
My Account
|
Log Out