Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Changing CoS Services Overview

This topic describes how to provide CoS when subscribers dynamically upgrade or downgrade services in an access environment.

You can configure your network with a dynamic client profile that provides all subscribers with default CoS parameters when they log in. For example, all subscribers can receive a basic data service. By configuring the client profile with Junos OS predefined variables for RADIUS-provided CoS parameters, you also enable the service to be activated for those subscribers at login.

Note:

The dynamic client profile is also referred to as a dynamic client access profile, or sometimes just access profile for brevity. Do not confuse this profile, configured at the [edit dynamic-profiles profile-name] hierarchy level, with the access profile configured at the [edit access profile profile-name] hierarchy level. These static access profiles are used to configure authentication, accounting, and authorization parameters for subscriber access, some session attributes, and client-specific properties for L2TP and PPP sessions. Access profiles are applied at various configuration levels with the access-profile statement.

To enable subscribers to activate a service or upgrade to different services through RADIUS change-of-authorization (CoA) messages after login, configure a dynamic service profile that includes user-defined variables.

Types of CoS Variables Used in a Service Profile

You can configure variables for the following CoS parameters in a service profile:

  • Shaping rate

  • Delay buffer rate

  • Guaranteed rate

  • Scheduler map

For each CoS parameter, you must associate a RADIUS vendor ID. For each vendor ID, you must assign an attribute number and a tag. The tag is used to differentiate between values for different CoS variables when you specify the same attribute number for those variables. These values are matched with the values supplied by RADIUS during subscriber authentication. All of the values in the dynamic profile must be defined in RADIUS or none of the values are passed.

Optionally, you can configure default values for each parameter. Configuring default values is beneficial if you do not configure RADIUS to enable service changes. During service changes, RADIUS takes precedence over the default value that is configured.

Static and Dynamic CoS Configurations

Depending on how you configure CoS parameters in the access and service profiles, certain CoS parameters are replaced or merged when subscribers change or activate new services.

Static configuration is when you configure the scheduler map and schedulers in the static [edit class-of-service] hierarchy and reference the scheduler map in the dynamic profile. Dynamic configuration is when you configure the scheduler map and schedulers within the dynamic profile.

The CoS configuration also depends on whether you have enabled multiple subscribers on the same logical interface using the aggregate-clients statements in the dynamic profile referenced by DHCP. When you specify the aggregate-clients replace statement, the scheduler map names are replaced. In both cases, if the length of the scheduler map name exceeds 128 characters, subscribers cannot log in. When you specify the aggregate-clients merge statement, the scheduler map names specified in the dynamic profile are appended.

Best Practice:

To improve CoS performance in IPv4, IPv6, and dual-stack networks, we recommend that you use the aggregate-clients replace statement rather than the aggregate-clients merge statement.

Scenarios for Static and Dynamic Configuration of CoS Parameters

Table 1 lists the scenarios for static and dynamic configuration of CoS parameters in access profiles and service profiles at subscriber login. The table also lists the behavior for each configuration for service activation and service modification using RADIUS CoA messages.

Table 1: CoS Services and Variables

Scenario

Static CoS Configuration (Single Subscriber)

Dynamic CoS Configuration (Single Subscriber)

Dynamic CoS Configuration (Multiple Subscribers Enabled on a Logical Interface with the aggregate-clients merge Statement)

Dynamic CoS Configuration (Multiple Subscribers Enabled on a Logical Interface with the aggregate-clients replace Statement)

Subscriber login

  • Configure RADIUS values or default values for all parameters in access profile

  • Configure scheduler map in edit class-of-service hierarchy and reference in access profile

  • Configure RADIUS values or default values for all parameters in access profile

  • Configure scheduler map and schedulers in access profile

  • Configure RADIUS values or default values for all parameters in access profile

  • Configure scheduler map and schedulers in access profile

  • Configure RADIUS values or default values for all parameters in access profile

  • Configure scheduler map and schedulers in access profile

RADIUS CoA for service or variable change

Replaces the following parameters:

  • Delay buffer rate

  • Guaranteed rate

  • Scheduler map

  • Shaping rate

Replaces the following parameters:

  • Delay buffer rate

  • Guaranteed rate

  • Shaping rate

  • Scheduler map

Combines the values of the following parameters to their maximum scalar value:

  • Delay buffer rate

  • Guaranteed rate

  • Shaping rate

Appends the scheduler map parameter

Replaces the following parameters:

  • Delay buffer rate

  • Guaranteed rate

  • Shaping rate

  • Scheduler map

RADIUS CoA for service activation

Does not merge queues

NOTE:In this case, use a similar configuration to the access profile, including the same name for the traffic-control-profile. During service activation, this configuration replaces the original configuration in the access profile.

Merge queues if the queue specified in the service profile is not already in use for the subscriber

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

Merge queues if the queue specified in the service profile is not already in use for the subscriber

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

Merge queues if the queue specified in the service profile is not already in use for the subscriber

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

Related Documentation