Activating Subscribers and Managing Services in an Access Network
The subscriber access feature uses dynamic profiles to
activate subscribers and manage services.
A dynamic profile is a set of characteristics, defined in a
template, that the router uses to provide dynamic subscriber access
By using dynamic profiles you can:
Define access for your network
Define different service levels for subscribers
Preprovision services that you can activate later
Using AAA-based login (RADIUS-based login
or RADIUS CoA) you can:
Provide subscribers with dynamic activation and deactivation
based on service selection
Provide greater flexibility and efficient management for
a large number of subscribers and services
Components of a Dynamic Profile
You can use dynamic profiles to define various router components
for subscriber access.
These components include the following:
Dynamic firewall filters—Includes input and output
filters to enforce rules that define whether to permit or deny packets
that are transmitting an interface on the router. To apply dynamic
firewall filters to the subscriber interface, you configure static
input and output firewall filters and reference those filters in dynamic
Dynamic Class of Service (CoS)—Includes CoS values
that define a service for a subscriber. For example, you can configure
the shaping rate for traffic in a video service by referencing CoS
statements in a dynamic profile.
Dynamic signaling protocol—Includes dynamic IGMP
configuration for host to router signaling for IPv4 to support IP
Router Predefined Variables Used by Dynamic Profiles
router contains several predefined variables that enable dynamic association
of interfaces and logical units to incoming subscriber requests. You
must specify these predefined variables in certain statements within
a dynamic profile. When a client accesses the router, the dynamic
profile configuration replaces the predefined variable with the actual
interface name or unit value for the interface the client is accessing.
The predefined variables include:
$junos-interface-ifd-name—Replaced with the actual
interface device name.
$junos-underlying-interface-unit—Replaced with the
actual logical unit number.