Example: Configuring Static Scheduling and Queuing for Subscriber Access

This example shows you how to configure CoS for a subscriber in a dynamic profile. The CoS parameters configure a best-effort, data service for subscribers.

1. Configure the static CoS parameters in the [edit class-of-service] hierarchy.

   You must configure the scheduler maps in this hierarchy; it will get referenced in the dynamic profile.

   class-of-service {

   forwarding-classes {

   queue 0 best-effort;

   queue 1 expedited-forwarding;

   queue 3 network-control;

   queue 2 assured-forwarding;

   }

   scheduler-maps {

   data_smap {

   forwarding-class best-effort scheduler be_sch;

   }

   }

   schedulers {

   be_sch {

   transmit-rate percent 10;

   buffer-size remainder;

   priority low;

   }

   }

   }

2. Configure the subscriber interface in the [edit interfaces] hierarchy. Enable hierarchical scheduling for the interface.

   interfaces {

   ge-2/2/0 {

   hierarchical-scheduler;

   vlan-tagging;

   unit 100 {

   vlan-id 100;

   family inet {

   unnumbered-address lo0.0 preferred-source-address 100.0.0.1;

   }

   }

   }

3. Configure CoS in the dynamic profile.

   dynamic-profiles {

   data-service {

   interfaces {

   "$junos-interface-ifd-name" {

   unit "$junos-underlying-interface-unit" {

   family inet;

   }

   }

   }

   class-of-service {

   traffic-control-profiles {

   tcp1 {

   scheduler-map data_smap;

   shaping-rate 50k;

   guaranteed-rate 10k;

   }

   }

   interfaces {

   "$junos-interface-ifd-name" {

   unit "$junos-underlying-interface-unit" {

   output-traffic-control-profile tcp1;

   }

   }

   }

   }

   }

   }