Configuring Per-Unit Scheduling in a Dynamic Profile for Subscriber Access

Per-unit scheduling enables one set of output queues for each logical interface configured under the physical interface. In per-unit scheduling configurations, each Layer 3 scheduler node is allocated a dedicated set of queues.

If you do not explicitly configure CoS parameters, a default traffic profile with queues is attached to the logical interface.

1. Configure the static CoS parameters in the [edit class-of-service] hierarchy.
   1. Enable the per-unit scheduler for the physical interface.
      [edit interfaces interface-name]user@host# set per-unit-scheduler
   2. Configure the drop profiles.

      See Configuring RED Drop Profiles.

   3. Configure the forwarding classes.

      See Configuring Forwarding Classes

   4. Configure the rewrite-rules and classifier definitions.

      See Configuring Rewrite Rules and Defining Classifiers.

   See the Junos OS Class of Service Configuration Guide for information about configuring the remaining CoS parameters.

2. Configure a static or dynamic subscriber interface that can be referenced in the dynamic profile.
   • For static VLAN interfaces, see Configuring Static Subscriber Interfaces in Dynamic Profiles.
   • For dynamic IP demux interfaces, see Configuring Dynamic Subscriber Interfaces Using IP Demux Interfaces in Dynamic Profiles.
   • For dynamic PPPoE interfaces, see Configuring Dynamic PPPoE Subscriber Interfaces Using Dynamic Profiles.
3. Configure CoS parameters in a dynamic profile.
   1. Configure the dynamic profile.

      See Configuring a Basic Dynamic Profile.

   2. Configure traffic shaping and scheduling parameters in the dynamic profile using a traffic-control profile.

      See Configuring Traffic Scheduling and Shaping for Subscriber Access.

   3. Configure the schedulers and scheduler map in the dynamic profile.

      You can configure the schedulers using dynamic variables or a combination of both static values and dynamic variables.

      See Configuring Schedulers in a Dynamic Profile for Subscriber Access.

   4. Apply CoS parameters to a subscriber interface by referencing an interface in the dynamic profile.
      • For traffic shaping and scheduling, see Applying Traffic Shaping and Scheduling to a Subscriber Interface in a Dynamic Profile.
      • For rewrite rules, see Applying a Rewrite Rule Definition to a Subscriber Interface in a Dynamic Profile.
      • For classifiers, see Applying a Classifier to a Subscriber Interface in a Dynamic Profile.
4. (Optional) Configure variables in access and service profiles to enable RADIUS to activate subscriber and upgrade services through CoA.

   Note: Do not instantiate a CoA request using a service dynamic profile that is already in use on the same logical interface.

   Because you have configured the scheduler map in the dynamic profile, queues are merged when subscribers change services. Other CoS parameters are replaced.

   When multiple subscribers are enabled on a DHCP subscriber interface, and the dynamic profile referenced by DHCP does not have the replace keyword configured, the system does not replace the parameters. Instead, it combines the values of the parameters to their maximum scalar value.

   1. Configure CoS variables in a dynamic profile.

      See Configuring User-Defined CoS Variables in a Dynamic Service Profile

   2. (Optional) Enable multiple clients for the same subscriber (logical interface) to aggregate attributes by configuring the aggregate-clients option for the dynamic profile attached to a DHCP subscriber interface.

      See Attaching Dynamic Profiles to DHCP Subscriber Interfaces.