- play_arrow Hierarchical Class of Service
- play_arrow Configuring Hierarchical Class of Service on MX Series 5G Universal Routing Platforms
- Hierarchical Class of Service Overview
- Hierarchical Class of Service Network Scenarios
- Understanding Hierarchical Scheduling
- Priority Propagation in Hierarchical Scheduling
- Hierarchical CoS for Metro Ethernet Environments
- Hierarchical Schedulers and Traffic Control Profiles
- Example: Building a Four-Level Hierarchy of Schedulers
- Scheduling and Shaping in Hierarchical CoS Queues for Traffic Routed to GRE Tunnels
- Example: Performing Output Scheduling and Shaping in Hierarchical CoS Queues for Traffic Routed to GRE Tunnels
- Configuring Ingress Hierarchical CoS
- Hierarchical Class of Service for Network Slicing
- play_arrow Configuring Hierarchical Class of Service on MICs, MPCs, MLCs, and Aggregated Ethernet Interfaces
- Understanding Hierarchical Scheduling for MIC and MPC Interfaces
- Configuring Ingress Hierarchical CoS on MIC and MPC Interfaces
- Per-Unit Scheduling and Hierarchical Scheduling for MPC Interfaces
- Dedicated Queue Scaling for CoS Configurations on MIC and MPC Interfaces Overview
- Jitter Reduction in Hierarchical CoS Queues
- Example: Reducing Jitter in Hierarchical CoS Queues
- Hierarchical Schedulers on Aggregated Ethernet Interfaces Overview
- Configuring Hierarchical Schedulers on Aggregated Ethernet Interfaces
- Example: Configuring Scheduling Modes on Aggregated Interfaces
- Increasing Available Bandwidth on Rich-Queuing MPCs by Bypassing the Queuing Chip
-
- play_arrow Configuration Statements and Operational Commands
CoS Two-Level Hierarchical Scheduling on MPLS Pseudowire Subscriber Interfaces
Two-level hierarchical scheduling limits the number of hierarchical levels in the scheduling hierarchy to two. In a two-level scheduling hierarchy, all logical interfaces and interface sets share a single level 2 node. Table 1 summarizes the interface hierarchy and the CoS scheduler node levels for two-level hierarchical scheduling.
Level 1 | Level 2 | Level 3 | Level 4 |
|---|---|---|---|
Physical interface | – | Pseudowire transport logical interface | One or more queues |
Physical interface | – | Interface set | One or more queues |
Physical interface | – | Pseudowire service logical interface | One or more queues |
You use the two-level hierarchical scheduling when you have many pseudowires but you do not require shaping specific to the subscriber logical interface. For example, when your configuration is one subscriber per pseudowire interface.
Figure 1 shows a two-level hierarchical scheduling configuration for the MPLS pseudowires. In this configuration, level 1 is the physical interface used for the logical tunnel anchor node. All of the pseudowire transport interfaces share a single level 2 node. The level 3 nodes are the pseudowire transport logical interfaces (ps0.0, ps1.0, and ps2.0). In this configuration, interface sets are not configured and only the logical interfaces have traffic control profiles.
Two-level hierarchical scheduling has up to eight class of service queues. For this configuration,
include the maximum-hierarchy-levels 2 option under the [edit interfaces interface-name hierarchical-scheduler] hierarchy level at the physical interface for the anchor logical
tunnel.
You cannot configure shaping policies on both the pseudowire logical interfaces and the subscriber logical interfaces over the same pseudowire. If a traffic-control profile is configured on a pseudowire logical interface, and CoS policies are configured on the subscriber logical interface over another pseudowire, all of the logical interfaces are at level 3 and act as peers.
