Supported Platforms
Related Documentation
- M, MX Series
- Dynamic Profiles Overview
- MX Series
- Subscriber Activation and Service Management in an Access Network
- Dynamic Variables Overview
- Junos OS Predefined Variables
- Subscriber Interfaces That Provide Initial CoS Parameters Dynamically Obtained from RADIUS
- Configuring Initial CoS Parameters Dynamically Obtained from RADIUS
Example: Configuring Initial CoS Parameters Dynamically Obtained from RADIUS
The following configuration is an example of a client dynamic profile in which initial CoS parameters are dynamically obtained from the RADIUS server when a subscriber authenticates over the interface to which the dynamic profile is applied.
For this example, assume that the RADIUS authentication server has been configured with traffic-shaping parameters (at Juniper Networks VSA 26-108) and CoS scheduling and queuing parameters (at Juniper Networks VSA 26–146).
The subscriber interface is a single-unit static gigabit Ethernet VLAN interface on an EQ DPC port:
The client dynamic profile residential_silver attaches the traffic-control profile tcp_1 to the subscriber interface that is defined in the dynamic profile using the $junos-interface-ifd-name predefined variable.
The traffic-control profile tcp_1, references Junos OS predefined variables to obtain a scheduler-map name and traffic-shaping parameter values from RADIUS when a subscriber logs in. For this example, assume that the RADIUS server replaces the Junos OS predefined variable $junos-cos-scheduler-map scheduler-map name business_smap_1. The scheduler map business_smap_1 is configured in the client dynamic profile:
A scheduler definition references Junos OS predefined variables to obtain scheduler configurations from RADIUS when a subscriber logs in. For this example, assume that the RADIUS server provides scheduler configurations for schedulers named be_sched and home_sched, which are included in the scheduler map business_smap_1:
Static configurations for CoS consist of configurations for the forwarding classes used in the scheduler map business_smap_1 and configurations for drop-profile names provided by RADIUS for as part of the scheduler configurations provided (for be_sched and home_sched) when a subscriber logs in:
Related Documentation
- M, MX Series
- Dynamic Profiles Overview
- MX Series
- Subscriber Activation and Service Management in an Access Network
- Dynamic Variables Overview
- Junos OS Predefined Variables
- Subscriber Interfaces That Provide Initial CoS Parameters Dynamically Obtained from RADIUS
- Configuring Initial CoS Parameters Dynamically Obtained from RADIUS
Published: 2013-02-11
Supported Platforms
Related Documentation
- M, MX Series
- Dynamic Profiles Overview
- MX Series
- Subscriber Activation and Service Management in an Access Network
- Dynamic Variables Overview
- Junos OS Predefined Variables
- Subscriber Interfaces That Provide Initial CoS Parameters Dynamically Obtained from RADIUS
- Configuring Initial CoS Parameters Dynamically Obtained from RADIUS
