Juniper Networks
Log in
|
How to Buy
|
Contact Us
|
United States (Change)
Choose Country
Solutions
Products & Services
Company
Partners
Support
Education
Community
Security Intelligence Center

Technical Documentation

Download Software
Research a Problem Login required
Case Management Login required
Contract & Product Management Login required
Technical Documentation
Documentation Archive
Report Documentation Bug
Enterprise MIBs
File Format Help
Glossary
Portable Libraries
End-of-Life Products
Contact Support
Guidelines and Policies
Security Resources
Home > Support > Technical Documentation > JunosE Software > Configuring Traffic-Class Groups That Define Service Levels
Print
FeedbackFeedback

Documentation Search

Advanced Search |  Search Tips
 

Related Documentation

  • Configuring Traffic Classes That Define Service Levels
  • Monitoring Traffic Classes and Traffic-Class Groups for Defined Levels of Service
  • traffic-class
  • traffic-class-group
 

Configuring Traffic-Class Groups That Define Service Levels

You can configure a traffic-class group and enter Traffic Class Group Configuration mode, from which you can add classes to or delete classes from the group.

Each traffic class can appear in only one traffic-class group. If not explicitly added to a traffic-class group, the traffic class is considered to be ungrouped.

To configure a traffic-class group:

  1. 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.

    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
  • Monitoring Traffic Classes and Traffic-Class Groups for Defined Levels of Service
  • traffic-class
  • traffic-class-group
 

Published: 2010-12-20


 
  • About Juniper
  • The New Network
  • Investor Relations
  • Press Releases
  • Newsletters
  • Juniper Offices
  • Resources
  • How to Buy
  • Partner Locator
  • Image Library
  • Visio Templates
  • Security Center
  • Community
  • Forums
  • Blogs
  • Junos Central
  • Social Media
  • 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-2011 Juniper Networks, Inc. All rights reserved.

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
Help
|
My Account
|
Log Out