Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

CoS Three-Level Hierarchical Scheduling on MPLS Pseudowire Subscriber Interfaces

CoS also supports three levels of hierarchical scheduling for MPLS pseudowire subscriber interfaces. Three-level scheduling hierarchies have up to eight classes of service. There are two variations of the three-level scheduling hierarchy depending on the location of the interface set. In both cases, the physical interface on which the logical tunnel resides is at level 1.

Three-Level Scheduling Hierarchy Case 1: Pseudowire Logical Interfaces over a Transport Logical Interface

The first variation of the three-level scheduling hierarchy is the pseudowire logical interface over the pseudowire transport logical interface. This scheduling hierarchy is as follows:

• Level 4—Forwarding class-based queues
• Level 3—Pseudowire service interfaces
• Level 2—Pseudowire transport logical interface
• Level 1—Common/shared physical interface of the logical tunnel

Figure 1 shows this three-level scheduling hierarchy. At level 3 are the pseudowire service interfaces for the subscriber sessions, denoted as ps0.1 and ps0.2, at level 2 are the pseudowire transport logical interfaces, denoted as ps0.0, and at level 1 is the physical interface of the logical tunnel. You apply the traffic-control profiles at both the pseudowire transport logical interfaces (level 2) and the pseudowire service interfaces (level 3).

Figure 1: Three-Level Scheduling Hierarchy Case 1: Pseudowire Service (Logical) Interfaces over a Transport Logical Interface

Three-Level Scheduling Hierarchy Case 2: Pseudowire Service Interfaces over a Pseudowire Service Interface Set

The second variation of the three-level hierarchical scheduling is the pseudowire service interfaces over the pseudowire service interface-set. This scheduling hierarchy is as follows:

• Level 4—Forwarding class-based queues
• Level 3—Pseudowire service interfaces
• Level 2—Interface set of the pseudowire service interfaces
• Level 1—Common/shared physical interface of the logical tunnel

Figure 2 shows this three-level scheduling hierarchy. At level 3 are the pseudowire service (logical) interfaces, denoted as ps0.1 and ps0.2, at level 2 is the interface set for the pseudowire service interfaces, and at level 1 is the physical interface of the logical tunnel. You apply the traffic-control profile at the pseudowire service interfaces (level 3) and at the interface-set (level 2) for the pseudowire service interfaces. This case is most useful for subscriber edge customers.

Figure 2: Three-Level Scheduling Hierarchy Case 2: Pseudowire Service (Logical) Interfaces over a Pseudowire Service (Logical) Interface Set

Three-Level Scheduling Hierarchy Combined Deployment Scenario

Figure 3 shows a deployment scenario that uses both Case 1 and Case 2 of the three-level hierarchical scheduling. At level 3 are the pseudowire service (logical) interfaces, denoted as ps0.1 through ps0.4. At level 2 is the interface set for pseudowire service interfaces ps0.1 and ps0.2 and the pseudowire transport logical interface ps1.0 for the pseudowire service (logical) interfaces ps0.3 and ps0.4. You apply the traffic-control profiles to the interfaces at both level 2 and 3, as well as interface set at level 2.

Figure 3: Three-Level Hierarchical Scheduling for MPLS Pseudowire Subscriber Interfaces-Deployment Scenario