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
Junos CLI Reference
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

dynamic-class-of-service-options (Dynamic Traffic Shaping)

date_range 16-Jun-24

Syntax

content_copy zoom_out_map
dynamic-class-of-service-options {
    vendor-specific-tags tag;
}

Hierarchy Level

content_copy zoom_out_map
[edit dynamic-profiles profile-name class-of-service]

Description

Configure CoS attributes applied to dynamic interfaces or interface sets based on access line information received in PPPoE discovery packets on dynamic subscriber interfaces. The packets convey the information in PPPoE-IA tags.

Options

vendor-specific-tags tag—Specify one or more of the following PPPoE-IA tags to set CoS attributes:

  • access-loop-encapsulation—Set the overhead-accounting CoS attribute based on the Access-Loop-Encapsulation tag (0x91). The tag enables the router to determine whether the access loop is cell-based or frame-based.

  • actual-data-rate-downstream—Set the shaping-rate class-of-service attribute based on the Actual-Data-Rate-Downstream tag (0x82).

  • apply-to-interface-set—Enable CoS to determine the node to which it conditionally applies the adjusted downstream rate. By default, when a CoS traffic control profile is configured for both a logical interface and the underlying (child) interface set, the adjusted rate values (shaping rate, overhead bytes, and overhead mode) are applied to the logical interface, according to the adjustment control profile. When you specify this option, the following conditions are evaluated:

    • If the $junos-interface-set-name has been resolved by AAA authorization, CoS applies the adjusted values to the underlying interface set to which the logical interface belongs. The name for this predefined variable is supplied by the Juniper Networks Qos-Set-Name VSA, 26–130. The application of the adjusted values is governed by the adjustment control profile, regardless of whether a traffic control profile is present for the logical interface.

    • If the $junos-interface-set-name has not been resolved by AAA authorization, CoS applies the adjusted values to the logical interface, governed by the adjustment control profile. If a traffic control profile is not present for the logical interface, then the adjusted values are applied to the underlying interface set.

    This option is appropriate for both five-level and four-level CoS hierarchies.

Required Privilege Level

interface—To view this statement in the configuration.

interface-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 12.1.

apply-to-interface-set option added in Junos OS Release 19.3R1.

footer-navigation