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
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Class of Service on demux Interfaces

date_range 25-Sep-24

This topic describes class of service (CoS) functionality and configuration on demux interfaces. demux interfaces support basic CoS functionality including behavior aggregate (BA) classifiers, rewrite rules, fixed classification, and port-level scheduling with targeted distribution.

Demultiplexing (demux) interfaces are logical interfaces that share a common, underlying interface. You can create logical subscriber interfaces using static or dynamic demultiplexing interfaces. In addition, you can use IP demultiplexing interfaces or VLAN demultiplexing interfaces when creating logical subscriber interfaces.

Overview of CoS on demux Interfaces

demux interfaces support basic CoS functionality, including:

  • Classifiers including INET precedence, DSCP, IEEE 802.1p, and IEEE 802.1ad

  • Rewrite rules including INET precedence, DSCP, IEEE 802.1p, and IEEE 802.1ad

  • Fixed classification

Note:

demux interfaces do not support MPLS EXP classifiers or rewrite rules.

Figure 1 shows the demux interface (demux0) with an underlying aggregated Ethernet (AE) interface. You can assign classifiers and rewrite rules to the logical interfaces (demux0.x) of the demux interface. You can then configure schedulers, scheduler maps, traffic control profiles, and so on, for the underlying AE interface.

Figure 1: demux interface with an underlying aggregated Ethernet interface demux interface with an underlying aggregated Ethernet interface

Configuring CoS on demux Interfaces

This section provides a simple example of how to configure a classifier and a rewrite rule for demux logical interfaces as well as a traffic control profile for the underlying AE interface.

  1. Configure a classifier and apply it to a demux logical interface.
    content_copy zoom_out_map
    [edit class-of-service]
    user@host# set classifiers ieee-802.1ad test forwarding-class expedited-forwarding loss-priority low code-points 0000
    user@host# set interfaces demux0 unit 0 classifiers ieee-802.1ad test
    
  2. Configure a rewrite rule and apply it to a demux logical interface.
    content_copy zoom_out_map
    [edit class-of-service]
    user@host# set rewrite-rules ieee-802.1ad test forwarding-class expedited-forwarding loss-priority low code-point 1011
    user@host# set interfaces demux0 unit 1 rewrite-rules ieee-802.1ad test
    
  3. Configure a traffic control profile and apply it to the underlying AE interface.
    content_copy zoom_out_map
    [edit class-of-service]
    user@host# set schedulers s1 shaping-rate 500m
    user@host# set scheduler-maps testmap forwarding-class expedited-forwarding scheduler s1
    user@host# set traffic-control-profiles tcp1 scheduler-map testmap
    user@host# set interfaces ae0 output-traffic-control-profile tcp1
    user@host# set interfaces ae0 member-link-scheduler replicate
  4. Commit and show the configuration.
    content_copy zoom_out_map
    [edit class-of-service]
    user@host# commit
    user@host# show
    classifiers {
        ieee-802.1ad test {
            forwarding-class expedited-forwarding {
                loss-priority low code-points 0000;
            }
        }
    }
    traffic-control-profiles {
        tcp1 {
            scheduler-map testmap;
        }
    }
    interfaces {
        ae0 {
            output-traffic-control-profile tcp1;
            member-link-scheduler replicate;
        }
        demux0 {
            unit 0 {
                classifiers {
                    ieee-802.1ad test;
                }
            }
            unit 1 {
                rewrite-rules {
                    ieee-802.1ad test;
                }
            }
        }
    }
    rewrite-rules {
        ieee-802.1ad test {
            forwarding-class expedited-forwarding {
                loss-priority low code-point 1011;
            }
        }
    }
    scheduler-maps {
        testmap {
            forwarding-class expedited-forwarding scheduler s1;
        }
    }
    schedulers {
        s1 {
            shaping-rate 500m;
        }
    }
    

In the very simple example above, IEEE802.1ad traffic arriving on demux0.0 with a code point of 0000 is assigned a forwarding class of expedited-forwarding and a loss priority of low. Through the traffic control profile, this traffic has up to 500 Mb of bandwidth as it traverses the router. Upon exiting the router through demux0.1, the traffic's code point is rewritten to 1011.

footer-navigation