- play_arrow Hierarchical CoS for Subscriber Management
- play_arrow Hierarchical Class of Service for Subscriber Management
- Hierarchical Class of Service for Subscriber Management Overview
- Understanding Hierarchical CoS for Subscriber Interfaces
- Hardware Requirements for Dynamic Hierarchical CoS
- Configuring Static Hierarchical Scheduling in a Dynamic Profile
- Configuring Hierarchical CoS for a Subscriber Interface of Aggregated Ethernet Links
- Configuring Hierarchical CoS on a Static PPPoE Subscriber Interface
- Example: Maintaining a Constant Traffic Flow by Configuring a Static VLAN Interface with a Dynamic Profile for Subscriber Access
- play_arrow Applying CoS to Groups of Subscriber Interfaces
- play_arrow Configuring Hierarchical Scheduling for MPLS Pseudowire Interfaces
- Hierarchical CoS on MPLS Pseudowire Subscriber Interfaces Overview
- CoS Configuration Overview for MPLS Pseudowire Subscriber Interfaces
- CoS Two-Level Hierarchical Scheduling on MPLS Pseudowire Subscriber Interfaces
- Configuring CoS Two-Level Hierarchical Scheduling for MPLS Pseudowire Subscriber Interfaces
- CoS Three-Level Hierarchical Scheduling on MPLS Pseudowire Subscriber Interfaces
- Configuring CoS Three-Level Hierarchical Scheduling for MPLS Pseudowire Subscriber Interfaces (Logical Interfaces over a Transport Logical Interface)
- Configuring CoS Three-Level Hierarchical Scheduling for MPLS Pseudowire Subscriber Interfaces (Logical Interfaces over a Pseudowire Interface Set)
- play_arrow Configuring Hierarchical Scheduling for L2TP
- play_arrow Preventing Bandwidth Contention on Subscriber Interfaces
- Hierarchical CoS Shaping-Rate Adjustments Overview
- Shaping Rate Adjustments for Subscriber Local Loops Overview
- Guidelines for Configuring Shaping-Rate Adjustments for Subscriber Local Loops
- Configuring the Minimum Adjusted Shaping Rate on Scheduler Nodes for Subscribers
- Configuring Shaping-Rate Adjustments on Queues
- Enabling Shaping-Rate Adjustments for Subscriber Local Loops
- Disabling Shaping-Rate Adjustments for Subscriber Local Loops
- Disabling Hierarchical Bandwidth Adjustment for Subscriber Interfaces with Reverse-OIF Mapping
- Example: Configuring Hierarchical CoS Shaping-Rate Adjustments for Subscriber Local Loops
- Verifying the Configuration of Shaping-Rate Adjustments for Subscriber Local Loops
- Verifying the Configuration of ANCP for Shaping-Rate Adjustments
- Using Hierarchical CoS to Adjust Shaping Rates Based on Multicast Traffic
- play_arrow Configuring Targeted Distribution of Subscribers on Aggregated Ethernet Interfaces
- Distribution of Demux Subscribers in an Aggregated Ethernet Interface
- Providing Accurate Scheduling for a Demux Subscriber Interface of Aggregated Ethernet Links
- Configuring the Distribution Type for Demux Subscribers on Aggregated Ethernet Interfaces
- Configuring Link and Module Redundancy for Demux Subscribers in an Aggregated Ethernet Interface
- Configuring Rebalancing of Demux Subscribers in an Aggregated Ethernet Interface
- Example: Separating Targeted Multicast Traffic for Demux Subscribers on Aggregated Ethernet Interfaces
- Verifying the Distribution of Demux Subscribers in an Aggregated Ethernet Interface
- Configuring the Distribution Type for PPPoE Subscribers on Aggregated Ethernet Interfaces
- Verifying the Distribution of PPPoE Subscribers in an Aggregated Ethernet Interface
- play_arrow Applying CoS Using Parameters Received from RADIUS
- Subscriber Interfaces That Provide Initial CoS Parameters Dynamically Obtained from RADIUS
- Changing CoS Services Overview
- CoS Traffic Shaping Attributes for Dynamic Interface Sets and Member Subscriber Sessions Overview
- Guidelines for Configuring CoS Traffic Shaping Attributes for Dynamic Interface Sets and Member Subscriber Sessions
- Configuring Initial CoS Parameters Dynamically Obtained from RADIUS
- Configuring Static Default Values for Traffic Scheduling and Shaping
- Applying CoS Traffic-Shaping Attributes to Dynamic Interface Sets and Member Subscriber Sessions
- CoS Traffic Shaping Predefined Variables for Dynamic Interface Sets
- Example: Configuring Dynamic Hierarchical Scheduling for Subscribers
-
- play_arrow Configuration Statements and Operational Commands
Hierarchical Schedulers and Traffic Control Profiles
When used, the interface set level of the hierarchy falls between the physical interface level (Level 1) and the logical interface (Level 3). Queues are always Level 4 of the hierarchy.
Beginning with Junos OS Release 16.1, certain MPCs on MX Series devices support up to five levels of scheduler hierarchies. The concepts presented in this topic apply similarly to five scheduler hierarchy levels.
Hierarchical schedulers add CoS parameters to the interface-set level of the configuration. They use traffic control profiles to set values for parameters such as shaping rate (the peak information rate [PIR]), guaranteed rate (the committed information rate [CIR] on these interfaces), scheduler maps (assigning queues and resources to traffic), and so on.
The following CoS configuration places the following parameters in traffic control profiles at various levels:
Traffic control profile at the port level (
tcp-port-level1):A shaping rate (PIR) of 100 Mbps
A delay buffer rate of 100 Mbps
Traffic control profile at the interface set level (
tcp-interface-level2):A shaping rate (PIR) of 60 Mbps
A guaranteed rate (CIR) of 40 Mbps
Traffic control profile at the logical interface level (
tcp-unit-level3):A shaping rate (PIR) of 50 Mbps
A guaranteed rate (CIR) of 30 Mbps
A scheduler map called
smap1to hold various queue properties (level 4)A delay buffer rate of 40 Mbps
In this case, the traffic control profiles look like this:
[edit class-of-service traffic-control-profiles]
tcp-port-level1 { # This is the physical port level
shaping-rate 100m;
delay-buffer-rate 100m;
}
tcp-interface-level2 { # This is the interface set level
shaping-rate 60m;
guaranteed-rate 40m;
}
tcp-unit-level3 { # This is the logical interface level
shaping-rate 50m;
guaranteed-rate 30m;
scheduler-map smap1;
delay-buffer-rate 40m;
}
Once configured, the traffic control profiles must be applied to the proper places in the CoS interfaces hierarchy.
[edit class-of-service interfaces]
interface-set level-2 {
output-traffic-control-profile tcp-interface-level-2;
}
ge-0/1/0 {
output-traffic-control-profile tcp-port-level-1;
unit 0 {
output-traffic-control-profile tcp-unit-level-3;
}
}
In all cases, the properties for level 4 of the hierarchical schedulers are determined by the scheduler map.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.
