Navigation
Table of Contents
Guide That Contains This Content
[+] Expand All
[-] Collapse All
Related Documentation
- M Series
- Configuring Static Hierarchical Scheduling and Queuing in a Dynamic Profile for Subscriber Access
- Configuring Dynamic Hierarchical Scheduling and Queuing in a Dynamic Profile for Subscriber Access
- MX Series
- For hardware requirements and configuration guidelines, see Guidelines for Configuring Dynamic CoS for Subscriber Access
- Configuring Static Hierarchical Scheduling and Queuing in a Dynamic Profile for Subscriber Access
- Configuring Dynamic Hierarchical Scheduling and Queuing in a Dynamic Profile for Subscriber Access
- Example: Configuring Static Hierarchical Scheduling and Queuing for Subscriber Access
- Example: Configuring Dynamic Hierarchical Scheduling and Queuing for Subscriber Access
- Verifying the Scheduling and Shaping Configuration for Subscriber Access
- CoS for Subscriber Access Overview
Applying Traffic Shaping and Scheduling to a Subscriber Interface in a Dynamic Profile
After you configure the traffic shaping and scheduling CoS parameters in a dynamic profile, you apply them to an interface. The output-traffic control profile enables you to provide traffic scheduling to the interface.
To apply CoS attributes to an interface in a dynamic profile:
- Specify that you want to apply CoS attributes to an interface
in the dynamic profile. user@host# edit dynamic-profiles profile-name class-of-service
- Configure the interface name and logical interface using
a variable, and apply the output-traffic control profile to the interface.[edit dynamic-profiles profile-name class-of-service interfaces]user@host# set interfaces $junos-interface-ifd-name unit $junos-underlying-interface-unit output-traffic-control-profile profile-name
You can use one of the following methods to specify the output-traffic control profile you want to use:
- Reference the $junos-cos-traffic-control-profile predefined variable. At subscriber login, subscriber management
takes one of the following actions, in the order listed:
- If RADIUS is being used and it returns a value for the traffic-control profile, subscriber management uses the RADIUS value.
- If RADIUS is not being used, subscriber management uses
the default traffic-control profile (which is specified by the predefined-variables-default statement at the [edit dynamic-profiles] hierarchy).
For example:
user@host# set interfaces $junos-interface-ifd-name unit $junos-underlying-interface-unit output-traffic-control-profile $junos-cos-traffic-control-profile
- Explicitly reference the name of the traffic-control profile.
For example:
user@host# set interfaces $junos-interface-ifd-name unit $junos-underlying-interface-unit output-traffic-control-profile tcp-sales-2
- Reference the $junos-cos-traffic-control-profile predefined variable. At subscriber login, subscriber management
takes one of the following actions, in the order listed:
Related Documentation
- M Series
- Configuring Static Hierarchical Scheduling and Queuing in a Dynamic Profile for Subscriber Access
- Configuring Dynamic Hierarchical Scheduling and Queuing in a Dynamic Profile for Subscriber Access
- MX Series
- For hardware requirements and configuration guidelines, see Guidelines for Configuring Dynamic CoS for Subscriber Access
- Configuring Static Hierarchical Scheduling and Queuing in a Dynamic Profile for Subscriber Access
- Configuring Dynamic Hierarchical Scheduling and Queuing in a Dynamic Profile for Subscriber Access
- Example: Configuring Static Hierarchical Scheduling and Queuing for Subscriber Access
- Example: Configuring Dynamic Hierarchical Scheduling and Queuing for Subscriber Access
- Verifying the Scheduling and Shaping Configuration for Subscriber Access
- CoS for Subscriber Access Overview
