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 Three-Level Hierarchical Scheduling for MPLS Pseudowire Subscriber Interfaces (Logical Interfaces over a Pseudowire Interface Set)

date_range 29-Nov-23

Before configuring three-level scheduling on pseudowire logical interfaces over a pseudowire logical interface set, you must first complete the following 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.

Three-level scheduling on pseudowire logical interfaces over a pseudowire logical interface set requires you to apply the traffic-control profiles at both the pseudowire logical interface and the pseudowire logical interface-set. To configure CoS policies on MPLS pseudowire subscriber interfaces using three-level implicit hierarchical scheduling:

  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.
    content_copy zoom_out_map
    [edit]
    user@host#edit interfaces ps-anchor-device-name
    user@host#set hierarchical-scheduler implicit-hierarchy
    
  2. Specify the traffic-control profile to use on the pseudowire logical interfaces.
    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. Define a pseudowire logical interface set and configure the traffic-control profile used for the interface set.
    content_copy zoom_out_map
    [edit class-of-service]
    user@host#edit interfaces
    user@host#edit interface-set interface-set-name
    user@host#edit output-traffic-control-profile profile-name
    
  4. Group the pseudowire logical interfaces in the pseudowire logical interface set.
    content_copy zoom_out_map
    [edit ]
    user@host#edit interfaces
    user@host#edit interface-set interface-set-name
    user@host#edit interface ps ps-device-name 
    user@host#edit unit logical-unit-number 
    
  5. 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 interfaces ps ps-device-name 
    user@host#edit unit logical-unit-number
    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)
    
  6. 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 interfaces ps ps-device-name 
    user@host#edit unit logical-unit-number
    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]
    
  7. Apply the rewrite rule and classifier to the pseudowire interfaces.

    For the interface_name parameter, specify the ps 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