Supported Platforms
Using the CLI to Modify Traffic-Control Profiles That Are Currently Applied to Subscribers
Subscriber management enables you to use the CLI to modify a traffic-control profile that is currently applied to existing subscribers. This feature allows you to update subscribers who are initially assigned the default traffic-control profile, which might have limited features.
 | Tip: You specify the default traffic-control profile with the predefined-variable-defaults statement and the cos-traffic-control-profile variable at the [edit dynamic-profiles profile-name class-of-service] hierarchy level. |
There are two methods you can use to modify an traffic-control profile that is in use—global and per-subscriber. The global method modifies the traffic-control profile for all subscribers currently using the traffic-control profile. The per-subscriber method modifies the traffic-control profile for a particular subscriber—all other subscribers currently using the traffic-control profile remain unaffected.
The global and per-subscriber methods share the following characteristics:
- They modify traffic-control profiles that are currently applied to active subscribers.
- Neither method creates new traffic-control profiles; they modify existing traffic-control profiles that have been previously created using the traffic-control-profiles statement at the [edit dynamic-profiles profile-name class-of-service] hierarchy level.
- Modifications are transparent to the active subscribers who are using the modified profile. The modified traffic-control profile is assigned without requiring any action by the subscriber.
- Both methods are useful when updating subscribers who are initially assigned the default traffic-control profile, which might have limited features. You specify the default traffic-control profile with the predefined-variable-defaults statement and the cos-traffic-control-profile variable at the [edit dynamic-profiles profile-name class-of-service] hierarchy level.
 | Note: To support CLI modification of traffic-control profiles in an IPv4/IPv6 dual-stack environment, you must have the aggregate-clients replace statement enabled at the [edit system services dhcp-local-server group group-name dynamic-profile profile-name] hierarchy |
This topic includes the following tasks:
Using the CLI to Globally Modify a Traffic-Control Profile Currently Applied to Multiple Subscribers
To make a global modification for all current subscribers assigned a particular traffic-control profile, you change one or more parameters for the traffic-control profile and commit the changes.
In this example, the statement changes the shaping rate for the existing traffic-control profile named TCP-silver. After the change, the new shaping rate applies to all subscribers currently using TCP-silver.
- Access the traffic-control profile you want to modify.[edit dynamic-profiles business-profile class-of-service]user@host# edit traffic-control-profiles TCP-silver
- Specify the parameters that you want to modify in the
traffic-control profile. [edit dynamic-profiles business-profile class-of-service traffic-control-profiles TCP-silver]user@host# set shaping-rate 20m
- Commit the configuration change to update the traffic-control profile. All current subscribers using TCP-silver now have the new shaping-rate.
Using the CLI to Modify a Traffic-Control Profile for a Specific Current Subscriber
To make a per-subscriber modification for a specific subscriber that is currently assigned a traffic-control profile, you specify the name of the new traffic-control profile to use.
In this example, the command replaces the existing traffic-control profile with the profile named TCP-gold. The new traffic-control profile applies only to the subscriber identified by session ID 2551.
- Request that the traffic-control profile named TCP-gold be applied to session ID 2551. user@host> request network-access aaa subscriber modify session-id 2551 junos-cos-traffic-control-profile TCP-gold
The system then displays the status message, Successful completion, indicating that the modification is successful. The subscriber identified by session ID 2551 now uses the TCP-gold traffic-control profile.
