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:
You can configure external RADIUS server VSAs with values that you expect subscribers to log in with.
See Configuring Router Interaction with RADIUS Servers and Configuring RADIUS Server Parameters for Subscriber Access.
See Extended DHCP Local Server Overview and Juniper Networks VSAs Supported by the AAA Service Framework.
You need to use different configuration statements and JUNOS predefined variables to associate an access dynamic profile with a static or dynamic subscriber interface:
To associate an access dynamic profile with a static subscriber interface, configure the interface at the static [edit interfaces] hierarchy level and reference the interface at the [edit dynamic-profiles profile-name] hierarchy level by using the JUNOS predefined variables $junos-interface-ifd-name and $junos-underlying-interface-unit to specify the interface name and logical unit number:
- [edit]
- interfaces {
- ... supported_interface_configuration ...
- }
- dynamic-profiles {
-
- }
To associate an access dynamic profile with a dynamic subscriber interface, create the interface at the [edit dynamic-profiles profile-name] hierarchy level by using the JUNOS predefined variables $junos-underlying-interface, $junos-interface-unit, and $junos-subscriber-ip-address to specify the interface name, interface logical unit number, and subscriber IP address:
- [edit]
- dynamic-profiles {
-
- profile-name {
-
- interfaces {
-
- demux0 { # The
logical demux interface
-
- unit “$junos-underlying-interface-unit”
{ # Logical unit number
-
- demux-options {
- underlying-interface "$junos-underlying-interface";
- }
-
- family inet { #
-
- demux-source {
- $junos-subscriber-ip-address;
- }
- }
- }
- }
- }
- }
- }
To apply a traffic-control profile to the subscriber interface when a subscriber logs, include the output-traffic-control-profile in the [edit dynamic-profiles profile-name class-of-service interfaces interface-name unit logical-unit-number] hierarchy level:
- [edit]
- dynamic-profiles {
-
- profile-name {
-
- class-of-service {
-
- interfaces { #
Interface-specific CoS for incoming packets
-
- “$junos-interface-ifd-name” {
-
- unit “$junos-underlying-interface-unit”
{
- output-traffic-control-profile tc-profile-name;
- }
- }
- }
- }
- }
- }
Configure a traffic-control profile to specify initial traffic-shaping parameters to be dynamically obtained from RADIUS when a subscriber logs in. To configure, include statements at the [edit dynamic-profiles profile-name class-of-service traffic-control-profiles tc-profile-name] hierarchy level:
- [edit]
- dynamic-profiles {
-
- 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 forwarding classes and scheduler maps at the static [edit class-of-service scheduler-maps] hierarchy level:
- [edit]
- class-of-service {
-
- forwarding-class ( # Include a queue for each class and associate queue
numbers with class names
- queue number scheduler-name;
- }
-
- scheduler-maps {
# Associates queues with scheduler
-
- smap-name {
- forwarding-class class-name scheduler scheduler-name;
- }
- }
- }
Configure a scheduler to specify initial scheduling and queuing parameters to be dynamically obtained from RADIUS when a subscriber logs in. To configure, include statements at the [edit dynamic-profiles profile-name class-of-service schedulers] hierarchy level:
- [edit]
- dynamic-profiles {
-
- profile-name {
-
- class-of-service {
-
- schedulers {
-
- “$junos-cos-scheduler” {
- buffer-size “$junos-cos-scheduler-bs”;
- priority “$junos-cos-scheduler-pri”;
- transmit-rate “$juno-cos-scheduler-tx”;
- 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”;
- }
- }
- }
- }
- }