Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Hierarchical Class of Service User Guide
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Configuring CoS Two-Level Hierarchical Scheduling for MPLS Pseudowire Subscriber Interfaces

date_range 29-Nov-23

Before configuring CoS parameters for MPLS pseudowire subscriber interfaces, 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.

To configure CoS policies on MPLS pseudowire subscriber interfaces using two-level scheduling:

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

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

    content_copy zoom_out_map
    [edit class-of-service]
    user@host#edit rewrite-rules (dscp | inet-precedence) rewrite-name
    user@host#edit forwarding-class class-name
    user@host#set loss-priority class-name code-point (alias | bits)
    
  4. Configure the classifier.

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

    content_copy zoom_out_map
    [edit class-of-service]
    user@host#edit classifiers (dscp | inet-precedence) classifier-name
    user@host#edit forwarding-class class-name
    user@host#set loss-priority class-name code-points [aliases] [bit-patterns]
    
  5. Apply the rewrite rule and classifier to the pseudowire interface.

    For the interface_name parameter, specify the pseudowire device name.

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