[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]

Subscriber Interfaces that Provide Initial CoS Parameters Dynamically Obtained from RADIUS Overview

You can configure interface-specific CoS parameters that the router obtains when subscribers log in at appropriately configured static or dynamic subscriber interfaces. This feature is supported only for interfaces on Enhanced Queuing Dense Port Concentrators (EQ DPCs) in MX-series routers.

To configure a client dynamic profile to providing initial CoS Services, make sure you understand the following concepts:

Dynamic Configuration of Initial CoS in Client Profiles

When a router interface receives a join message from a DHCP client, the JUNOS software applies the values configured in the client dynamic profile associated with that router interface. You can associate a dynamic profile with a subscriber interface on the router by including statements at the [edit dynamic-profiles profile-name class-of-service interfaces] hierarchy level. A dynamic profile that is activated through its association with a subscriber interface is known as a client profile.

This release supports a set of internal variables for obtaining a scheduler-map name and traffic-shaping parameters from the RADIUS authentication server, and another set of internal variables for obtaining a scheduler name and scheduler parameters from the RADIUS authentication server. When a client authenticates over a router interface associated with the client dynamic profile, the router replaces the internal variables with interface-specific values obtained from the RADIUS server.

Note: For this release of the JUNOS software, configure dynamic configuration of initial CoS features in a client dynamic profile by referencing JUNOS internal variables; do not define and reference user-defined variables in a client dynamic profile.

Internal Variables for Dynamic Configuration of Initial Traffic Shaping

To provide a scheduler map name and traffic shaping parameters obtained from the RADIUS authentication server when a subscriber authenticates, you can reference the following JUNOS internal variables for CoS at the [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] hierarchy level for the client dynamic profile associated with the subscriber interface:

Table 28 provides detailed descriptions of the JUNOS internal variables for CoS that you can reference in a client dynamic profile to dynamically configure an initial traffic-control profile when a subscriber logs in.

Table 28: JUNOS Internal Variables for Dynamic Configuration of Initial Traffic Shaping

Internal Variable Name and DescriptionStatic and Dynamic Statement Syntax Options

$junos-cos-scheduler-map

Scheduler-map name configured in a traffic-control profile in a client dynamic profile. The JUNOS software obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the client dynamic profile is attached.

You reference this variable from the scheduler-map statement at the [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] hierarchy level.

NOTE: The scheduler map referenced by the scheduler-map statement can be defined dynamically (at the [edit dynamic-profiles profile-name class-of-service scheduler-maps] hierarchy level) or statically (at the [edit class-of-service scheduler-maps] hierarchy level).

$junos-cos-shaping-rate

Shaping rate configured in a traffic-control profile in a client dynamic profile. The JUNOS software obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the client dynamic profile is attached.

You reference this variable from the shaping-rate statement at the [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] hierarchy level.

$junos-cos-guaranteed-rate

Guaranteed rate configured in a traffic-control profile in a client dynamic profile. The JUNOS software obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the client dynamic profile is attached.

You reference this variable from the guaranteed-rate statement at the [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] hierarchy level.

$junos-cos-delay-buffer-rate

Delay-buffer rate configured in a traffic-control profile in a client dynamic profile. The JUNOS software obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the client dynamic profile is attached.

You reference this variable in the delay-buffer-rate statement at the [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] hierarchy level.

Internal Variables for Dynamic Configuration of Initial Scheduling and Queuing

To provide a scheduler name and parameters obtained from a RADIUS authentication server when a subscriber logs in, you can reference the following JUNOS internal variables for CoS in the [edit dynamic-profiles profile-name class-of-service schedulers] configuration for the client dynamic profile associated with the subscriber interface:

Table 29 provides detailed descriptions of the JUNOS internal variables for CoS that you can reference in a client dynamic profile to dynamically configure an initial scheduler when a subscriber logs in .

Table 29: JUNOS Internal Variables for Dynamic Configuration of Initial Scheduling and Queuing

Internal Variable Name and DescriptionStatic and Dynamic Statement Syntax Options

$junos-cos-scheduler

Name of a scheduler configured in a client dynamic profile. The JUNOS software obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the client dynamic profile is attached.

You reference this variable from the scheduler statement at the [edit dynamic-profiles profile-name class-of-service schedulers] hierarchy level.

$junos-cos-scheduler-tx

Transmit rate specified for a scheduler configured in a client dynamic profile. The JUNOS software obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the client dynamic profile is attached.

You reference this variable from the transmit-rate statement at the [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name] hierarchy level.

$junos-cos-scheduler-bs

Buffer size as a percentage of total buffer, specified for a scheduler configured in a client dynamic profile. The JUNOS software obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the client dynamic profile is attached.

You reference this variable from the buffer-size statement with the percent option at the [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name] hierarchy level.

$junos-cos-scheduler-pri

Packet-scheduling priority value specified for a scheduler configured in a client dynamic profile. The JUNOS software obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the client dynamic profile is attached.

You reference this variable from the priority statement at the [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name] hierarchy level.

  • priority (low | medium-low | medium-high | high | strict-high);
  • priority $junos-cos-scheduler-pri;

$junos-cos-scheduler-dropfile-low

Name of the drop profile for RED for loss-priority level low specified for a scheduler configured in a client dynamic profile. The JUNOS software obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the client dynamic profile is attached.

You reference this variable from the drop-profile statement at the [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name drop-profile-map loss-priority low protocol any] hierarchy level.

NOTE: The drop profile must be configured statically (at the [edit class-of-service schedulers scheduler-name drop-profiles] hierarchy level) for loss-priority low.

$junos-cos-scheduler-dropfile-medium-low

Name of the drop profile for RED for loss-priority level medium-low specified for a scheduler configured in a client dynamic profile. The JUNOS software obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the client dynamic profile is attached.

You reference this variable from the drop-profile statement at the [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name drop-profile-map loss-priority medium-low protocol any] hierarchy level.

NOTE: The drop profile must be configured statically (at the [edit class-of-service schedulers scheduler-name drop-profiles] hierarchy level).

$junos-cos-scheduler-dropfile-medium-high

Name of the drop profile for RED for loss-priority level medium-high specified for a scheduler configured in a client dynamic profile. The JUNOS software obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the client dynamic profile is attached.

You reference this variable from the drop-profile statement at the [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name drop-profile-map loss-priority medium-high protocol any] hierarchy level.

NOTE: The drop profile must be configured statically (at the [edit class-of-service schedulers scheduler-name drop-profiles] hierarchy level).

$junos-cos-scheduler-dropfile-high

Name of the drop profile for RED for loss-priority level high specified for a scheduler configured in a client dynamic profile. The JUNOS software obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the client dynamic profile is attached.

You reference this variable from the drop-profile statement at the [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name drop-profile-map loss-priority high protocol any] hierarchy level.

NOTE: The drop profile must be configured statically (at the [edit class-of-service schedulers scheduler-name drop-profiles] hierarchy level).

$junos-cos-scheduler-dropfile-any

Name of the drop profile for RED for loss-priority level any specified for a scheduler configured in a client dynamic profile The JUNOS software obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the client dynamic profile is attached.

You reference this variable from the drop-profile statement at the [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name drop-profile-map loss-priority any protocol any] hierarchy level.

NOTE: The drop profile must be configured statically (at the [edit class-of-service schedulers scheduler-name drop-profiles] hierarchy level).

Related Topics


[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]