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

Configuring CoS Three-Level Hierarchical Scheduling for MPLS Pseudowire Subscriber Interfaces (Logical Interfaces over a Transport Logical Interface)

Before configuring CoS three-level scheduling on pseudowire logical interfaces over a transport logical interface, you must first complete these tasks:

1. Configure the pseudowire logical interfaces. See Configuring a Pseudowire Subscriber Logical Interface.
2. Configure the pseudowire device count. See Configuring the Maximum Number of Pseudowire Logical Interface Devices Supported on the Router.
3. Configure the pseudowire device including the logical tunnel anchor point. See Configuring a Pseudowire Subscriber Logical Interface Device.
4. Configure the pseudowire transport logical interface. See Configuring the Transport Logical Interface for a Pseudowire Subscriber Logical Interface.
5. Configure the pseudowire signaling (either Layer 2 circuit signaling or Layer 2 VPN signaling). See Configuring Layer 2 Circuit Signaling for Pseudowire Subscriber Logical Interfaces or Configuring Layer 2 VPN Signaling for Pseudowire Subscriber Logical Interfaces.
6. Configure the pseudowire logical interfaces. See Configuring the Service Logical Interface for a Pseudowire Subscriber Logical Interface.

1. Configure the hierarchical scheduler for the physical interface used for the logical tunnel (anchor point). For three-level scheduling the hierarchical scheduler must be set to implicit-hierarchy.
   [edit]user@host#edit interfaces ps-anchor-device-nameuser@host#set hierarchical-scheduler implicit-hierarchy
2. Specify the traffic-control profile to use on the pseudowire logical interface.
   [edit class-of-service]user@host#edit interfaces ps ps-device-name user@host#edit unit logical-unit-numberuser@host#set output-traffic-control-profile profile-name
3. Specify the traffic-control profile to use on the pseudowire transport logical interface.
   [edit class-of-service]user@host#edit interfaces ps ps-device-name user@host#edit unit logical-unit-numberuser@host#set output-traffic-control-profile profile-name
4. Configure the rewrite rule.

   The available rewrite rule types for pseudowire interfaces are dscp and inet-precedence.

   [edit class-of-service]user@host#edit interfaces ps ps-device-name user@host#edit unit logical-unit-numberuser@host#edit rewrite-rules (dscp | inet-precedence) rewrite-nameuser@host#edit forwarding-class class-nameuser@host#set loss-priority class-name code-point (alias | bits)
5. Configure the classifier.

   The available classifier types for pseudowire interfaces are dscp and inet-precedence.

   [edit class-of-service]user@host#edit interfaces ps ps-device-name user@host#edit unit logical-unit-numberuser@host#edit classifiers (dscp | inet-precedence) classifier-nameuser@host#edit forwarding-class class-nameuser@host#set loss-priority class-name code-points [aliases] [bit-patterns]
6. Apply the rewrite rule and classifier to the pseudowire interfaces.

   For the interface_name parameter, specify the pseudowire device name.

   [edit class-of-service interfaces interface_name unit logical-unit-number]user@host#set rewrite-rule (dscp | inet-precedence) (rewrite-name | default) protocol protocol-typesuser@host#set classifiers (dscp | inet-precedence) (classifier-name | default)