- play_arrow Hierarchical Class of Service
- play_arrow Configuring Hierarchical Class of Service on MX Series 5G Universal Routing Platforms
- Hierarchical Class of Service Overview
- Hierarchical Class of Service Network Scenarios
- Understanding Hierarchical Scheduling
- Priority Propagation in Hierarchical Scheduling
- Hierarchical CoS for Metro Ethernet Environments
- Hierarchical Schedulers and Traffic Control Profiles
- Example: Building a Four-Level Hierarchy of Schedulers
- Scheduling and Shaping in Hierarchical CoS Queues for Traffic Routed to GRE Tunnels
- Example: Performing Output Scheduling and Shaping in Hierarchical CoS Queues for Traffic Routed to GRE Tunnels
- Configuring Ingress Hierarchical CoS
- Hierarchical Class of Service for Network Slicing
- play_arrow Configuring Hierarchical Class of Service on MICs, MPCs, MLCs, and Aggregated Ethernet Interfaces
- Understanding Hierarchical Scheduling for MIC and MPC Interfaces
- Configuring Ingress Hierarchical CoS on MIC and MPC Interfaces
- Per-Unit Scheduling and Hierarchical Scheduling for MPC Interfaces
- Dedicated Queue Scaling for CoS Configurations on MIC and MPC Interfaces Overview
- Jitter Reduction in Hierarchical CoS Queues
- Example: Reducing Jitter in Hierarchical CoS Queues
- Hierarchical Schedulers on Aggregated Ethernet Interfaces Overview
- Configuring Hierarchical Schedulers on Aggregated Ethernet Interfaces
- Example: Configuring Scheduling Modes on Aggregated Interfaces
- Increasing Available Bandwidth on Rich-Queuing MPCs by Bypassing the Queuing Chip
-
- play_arrow Configuration Statements and Operational Commands
Subscriber Interfaces That Provide Initial CoS Parameters Dynamically Obtained from RADIUS
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 5G Universal Routing Platforms.
To configure a dynamic profile to provide initial CoS Services, make sure you understand the following concepts:
Dynamic Configuration of Initial CoS in Access Profiles
When a router interface receives a join message from a DHCP
subscriber, the Junos OS applies the values configured in the dynamic
profile associated with that router interface. A dynamic profile that
is activated through its association with a subscriber interface is
known as an access dynamic profile. 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.
The Junos OS supports predefined variables for obtaining CoS parameters from the RADIUS authentication server. When a client authenticates over a router interface associated with the access dynamic profile, the router replaces the predefined variables with interface-specific values obtained from the RADIUS server.
To associate dynamically configured initial CoS features with a subscriber interface, reference Junos OS predefined variables—and not user-defined variables—in an access dynamic profile for that interface.
Predefined Variables for Dynamic Configuration of Initial Traffic Shaping
You can configure an access dynamic profile that provides initial traffic-shaping parameters when a subscriber logs in. The Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the access dynamic profile is attached.
If you define the Juniper Networks authentication and authorization VSA for CoS traffic-shaping parameter values (attribute number 26–108) on the RADIUS authentication server, the RADIUS server includes the values in RADIUS Access-Accept messages it sends to the router when a subscriber successfully authenticates over the interface.
To provide an initial scheduler map name and traffic shaping parameters obtained from the RADIUS authentication server when a subscriber logs in, reference the Junos OS predefined variables for CoS listed in Table 1 in an access dynamic profile associated with the subscriber interface.
Variable | Description |
|---|---|
$junos-cos-scheduler-map | Scheduler-map name to be dynamically configured in a traffic-control profile in the access dynamic profile when a subscriber logs in.
|
$junos-cos-shaping-rate | Shaping rate to be dynamically configured in a traffic-control profile in the access dynamic profile when a subscriber logs in. You can configure a RADIUS authentication server to include this information in the Accept-Accept message when a subscriber successfully authenticates over the static or dynamic subscriber interface to which the access dynamic profile is attached. |
$junos-cos-guaranteed-rate | Guaranteed rate to be dynamically configured in a traffic-control profile in the access dynamic profile when a subscriber logs in. You can configure a RADIUS authentication server to include this information in the Accept-Accept message when a subscriber successfully authenticates over the static or dynamic subscriber interface to which the access dynamic profile is attached. |
$junos-cos-delay-buffer-rate | Delay-buffer rate to be dynamically configured in a traffic-control profile in the access dynamic profile when a subscriber logs in. You can configure a RADIUS authentication server to include this information in the Accept-Accept message when a subscriber successfully authenticates over the static or dynamic subscriber interface to which the access dynamic profile is attached. |
Predefined Variables for Dynamic Configuration of Initial Scheduling and Queuing
You can configure an access dynamic profile that provides initial traffic-shaping parameters when a subscriber logs in. The Junos OS obtains this information from the RADIUS server when a subscriber authenticates over the static or dynamic subscriber interface to which the access dynamic profile is attached.
If you define the Juniper Networks authentication and authorization VSA for CoS scheduling and queuing parameter values (attribute number 26–146) on the RADIUS authentication server, the RADIUS server includes the values in RADIUS Access-Accept messages it sends to the router when a subscriber successfully authenticates over the interface.
To provide an initial scheduler name and scheduler and queuing parameters obtained from the RADIUS authentication server when a subscriber logs in, reference the Junos OS predefined variables listed in Table 2 in an access dynamic profile associated with the subscriber interface.
Variable | Description |
|---|---|
$junos-cos-scheduler | Name of a scheduler to be dynamically configured in the access dynamic profile. You can configure a RADIUS authentication server to include this information in the Accept-Accept message when a subscriber successfully authenticates over the static or dynamic subscriber interface to which the access dynamic profile is attached. |
$junos-cos-scheduler-transmit-rate | Transmit rate to be dynamically configured for the scheduler in the access dynamic profile. You can configure a RADIUS authentication server to include this information in the Accept-Accept message when a subscriber successfully authenticates over the static or dynamic subscriber interface to which the access dynamic profile is attached. |
$junos-cos-scheduler-bs | Buffer size, as a percentage of total buffer, to be dynamically configured for the scheduler in the access dynamic profile. You can configure a RADIUS authentication server to include this information in the Accept-Accept message when a subscriber successfully authenticates over the static or dynamic subscriber interface to which the access dynamic profile is attached. |
$junos-cos-scheduler-pri | Packet-scheduling priority value to be dynamically configured for the scheduler in the access dynamic profile. You can configure a RADIUS authentication server to include this information in the Accept-Accept message when a subscriber successfully authenticates over the static or dynamic subscriber interface to which the access dynamic profile is attached. |
$junos-cos-scheduler-dropfile-low | Name of the drop profile for RED for loss-priority level
|
$junos-cos-scheduler-dropfile-medium-low | Name of the drop profile for RED for loss-priority level
|
$junos-cos-scheduler-dropfile-medium-high | Name of the drop profile for RED for loss-priority level
|
$junos-cos-scheduler-dropfile-high | Name of the drop profile for RED for loss-priority level
|
$junos-cos-scheduler-dropfile-any | Name of the drop profile for RED for loss-priority level
|
