Supported Platforms
Related Documentation
- MX Series
- Pseudowire Subscriber Logical Interfaces Overview
- Configuring a Pseudowire Subscriber Logical Interface
- Hierarchical CoS on MPLS Pseudowire Subscriber Interfaces Overview
- CoS Three-Level Hierarchical Scheduling on MPLS Pseudowire Subscriber Interfaces
- CoS Configuration Overview for MPLS Pseudowire Subscriber Interfaces
- Configuring CoS Two-Level Hierarchical Scheduling for MPLS Pseudowire Subscriber Interfaces
CoS Two-Level Hierarchical Scheduling on MPLS Pseudowire Subscriber Interfaces
The MPLS pseudowire subscriber interface two-level scheduler configuration effectively uses only level 1 and level 3 for each pseudowire. The two-level scheduling hierarchy is as follows:
- Level 4—Forwarding class-based queues
- Level 3—Pseudowire transport interface
- Level 2—Common/shared level 2 node
- Level 1—Common/shared physical interface of the logical tunnel
You use the two-level 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 the scheduling hierarchy for the MPLS pseudowire subscriber interface two-level scheduler configuration. In two-level scheduling, the level 3 nodes are the pseudowire transport interfaces denoted as ps0.0, ps1.0, and ps2.0 (psN.0, where N= a number). At level 1 is the physical interface used for the logical tunnel anchor node. All of the pseudowire transport interfaces share a common level 2 node. You apply the traffic-control profile on the pseudowire transport interfaces at level 3.
Figure 1: MPLS Pseudowire Subscriber Interface Two-Level Scheduler Configuration

The two-level scheduler configuration has up to eight class of service queues over the level 3 scheduler node. For this configuration, include the hierarchical-scheduler maximum-hierarchy-levels 2 option at the physical interface for the anchor logical tunnel.
![]() | Note: 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. |
Related Documentation
- MX Series
- Pseudowire Subscriber Logical Interfaces Overview
- Configuring a Pseudowire Subscriber Logical Interface
- Hierarchical CoS on MPLS Pseudowire Subscriber Interfaces Overview
- CoS Three-Level Hierarchical Scheduling on MPLS Pseudowire Subscriber Interfaces
- CoS Configuration Overview for MPLS Pseudowire Subscriber Interfaces
- Configuring CoS Two-Level Hierarchical Scheduling for MPLS Pseudowire Subscriber Interfaces
Published: 2013-02-11
Supported Platforms
Related Documentation
- MX Series
- Pseudowire Subscriber Logical Interfaces Overview
- Configuring a Pseudowire Subscriber Logical Interface
- Hierarchical CoS on MPLS Pseudowire Subscriber Interfaces Overview
- CoS Three-Level Hierarchical Scheduling on MPLS Pseudowire Subscriber Interfaces
- CoS Configuration Overview for MPLS Pseudowire Subscriber Interfaces
- Configuring CoS Two-Level Hierarchical Scheduling for MPLS Pseudowire Subscriber Interfaces