You can configure a subscriber interface so that subscribers receive initial CoS parameters that the router obtains from the RADIUS authentication server when subscribers log in using that logical interface on the router.
This topic includes the following tasks:
Configure external RADIUS server return VSA 26–108 with traffic–shaping parameters and VSA 26–146 with scheduler parameters for a router interface you expect subscribers to log in on.
See Router Interaction with RADIUS Servers Overview and Configuring RADIUS Server Parameters for Subscriber Access.
See Extended DHCP Local Server Overview and Juniper Networks VSAs Supported by the AAA Service Framework.
Configure a subscriber interface that supports hierarchical CoS. The following types of subscriber interfaces support hierarchical CoS:
For general information about configuring interfaces, see the JUNOS Network Interfaces Configuration Guide.
Attach a client dynamic profile to a subscriber interface that supports hierarchical CoS. To configure, include statements at the [edit dynamic-profiles client-profile-name interfaces] hierarchy level:
- [edit]
- interfaces {
-
. . . supported_interface_configuration . . .
- }
For general information about configuring interfaces, see the JUNOS Network Interfaces Configuration Guide.
Attach a client dynamic profile to a subscriber interface that supports hierarchical CoS. To configure, include statements at the [edit dynamic-profiles client-profile-name interfaces] hierarchy level:
- [edit]
- dynamic-profiles {
-
-
client-profile-name {
-
-
class-of-service {
-
-
traffic-control-profiles {
-
-
tc-profile-name {
-
scheduler-map “$juno-cos-scheduler-map”;
-
shaping-rate “$junos-cos-shaping-rate”;
-
guaranteed-rate “$junos-cos-guaranteed-rate”;
-
delay-buffer-rate “$junos-cos-delay-buffer-rate”;
- }
- }
- }
- }
- }
Configure scheduler maps in the static [edit class-of-service scheduler-maps] hierarchy level:
- [edit]
-
class-of-service {
-
-
forwarding-class ( # Associate queue numbers with class names
- queue number scheduler-name;
- queue number scheduler-name;
- }
-
-
scheduler-maps {
# Associates queues withscheduler
-
-
smap-name {
-
forwarding-class class-name scheduler scheduler-name;
- }
- }
- }
Attach a client dynamic profile to a subscriber interface that supports hierarchical CoS. To configure, include statements at the [edit dynamic-profiles client-profile-name interfaces] hierarchy level:
- [edit]
- dynamic-profiles {
-
-
client-profile-name {
-
-
class-of-service {
-
-
schedulers {
-
-
scheduler $junos-cos-scheduler
{
-
transmit-rate “$juno-cos-scheduler-tx”;
-
buffer-size “$junos-cos-scheduler-bs”;
-
priority “$junos-cos-scheduler-pri”;
-
drop-profile-map loss-priority low protocol any “$junos-cos-scheduler-low”;
-
drop-profile-map loss-priority medium-low protocol any “$junos-cos-scheduler-medium-low”;
-
drop-profile-map loss-priority medium-high protocol any “$junos-cos-scheduler-medium-high”;
-
drop-profile-map loss-priority high protocol any “$junos-cos-scheduler-high”;
-
drop-profile-map loss-priority any protocol any “$junos-cos-scheduler-any”;
- }
- }
- }
- }
- }
- }
To associate the RADIUS-obtained CoS parameters with the subscriber interface when a subscriber logs in, include the output-traffic-control-profile in the [edit dynamic-profiles client-profile-name class-of-service interfaces] hierarchy level:
- [edit]
- dynamic-profiles {
-
-
client-profile-name {
-
-
class-of-service {
-
- interfaces {
-
. . .
-
. . .
-
output-traffic-control-profile client-profile-name;
- }
- }
- }
- }