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 Multiclass MLPPP
- Configuring Traffic Classes on Multiclass MLPPP Interfaces

# ppp multilink multiclass traffic-class

#### Syntax

[ no ] ppp multilink multiclass traffic-class best-effort [ trafficClassName ]*

#### Release Information

Command introduced in JunosE Release 11.1.0.

#### Description

Configures mapping of QoS traffic classes to multilink classes. The no version deletes the mapping of QoS traffic classes to multilink classes.

#### Options

- best-effort—Specifies best-effort as the default traffic class for the router. The best-effort traffic class forwards as many packets as possible in as reasonable a time as possible. The best-effort traffic class is mapped to multilink class 0 by default. You must specify the best-effort traffic class in the command or the command fails.
- trafficClassName—Name of a QoS traffic class. You can map up to eight traffic classes to multilink classes. The order of the traffic class names specified determines the multilink class number which is used for the traffic class; for example, trafficClassName1 corresponds to multilink class 1, trafficClassName2 corresponds to multilink class 2, and so on.
- *—Indicates that one or more parameters can be repeated multiple times in a list in the command line

#### Mode

Interface Configuration, Profile Configuration, Subinterface Configuration

## Related Documentation

- Configuring Multiclass MLPPP
- Configuring Traffic Classes on Multiclass MLPPP Interfaces

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