[Contents] [Prev] [Next] [Index] [Report an Error]

Using the CLI to Activate Subscriber Service Sessions

A subscriber session represents a specific subscriber—the session consists of the subscriber’s name, the interface used for the session, and any active services for the subscriber. A subscriber can have one subscriber session active at any given time.

You create a subscriber’s service session when you assign a service definition to a subscriber session. Like an AAA-created service, a single subscriber session can have multiple simultaneous service sessions. You can use one method to create the subscriber session, and then a different method to activate the subscriber’s service session. For example, you might use RADIUS to create the AAA subscriber session, then use the CLI to activate the service session for the subscriber, You can optionally specify a service session profile that you want to attach to the service session.

You can use the CLI to activate a service session based on subscriber information or owner information:

Subscriber name and interface method—Activates the service session based on the subscriber name and the interface that the subscriber is using for this subscriber session. host1(config)#service-management subscriber-session client1@isp1.com interface atm 4/0.1 service-session “ tiered(1280000, 5120000)”

Owner name and ID method—Activates the service session based on the owner that created the subscriber session and the ID that was generated by the owner. For example, if RADIUS is used to create the subscriber session, the owner name is AAA and the owner ID is the Acct-Session-ID that was generated by RADIUS during subscriber creation.



host1(config)#service-management owner-session
AAA 537446 service-session  “ tiered(1280000,
5120000)”

Note: You must specify the parameter values in the order in which the parameters appear in the template name of the service definition file. Enclose the service definition name in double quotation marks, with the service’s parameter values in parentheses. For example, for the tiered service that is defined in Figure 27, the template name is:



<# tiered(inputBW, outputBW) #>

Use the following format with the service-session keyword:



“ tiered(1280000, 5120000)”

service-management owner-session

Use to activate a service for an existing subscriber by identifying the owner used to create the subscriber session and specifying the service session to use.
The subscriber session must exist before you use this command.
Use this command in Privileged Exec mode to create a dynamic subscriber session—dynamic sessions are deleted after a router reboot.
Use this command in Global Configuration mode to create persistent subscriber sessions that are retained across reboots.
Specify the name of the owner (the method originally used to create the subscriber session), and the ID generated by the of the owner. For example, if RADIUS was used to create the subscriber session, the owner name is AAA and the owner ID is the Acct-Session-ID generated by RADIUS when the subscriber session was created.
Include the optional service-session-profile keyword to assign a profile to the service session. The service session profile includes additional attributes, such as the type of statistics to be captured for the service session.
You can activate one subscriber session for a subscriber—and multiple service sessions for a particular subscriber session. If you create a second subscriber session for the same subscriber, only the newest subscriber session, with its services, is used.
Example 1—Activate a service session for an existing subscriberhost1(config)#service-management owner-session aaa 573498 service-session “video(4500000, 192.168.10.3)”
Example 2—Activate multiple service sessions for an existing subscriberhost1(config)#service-management owner-session aaa 573498 service-session “video(4500000, 192.168.10.3)” host1(config)#service-management owner-session aaa 573498 service-session “tiered(1000000, 2000000)” host1(config)#service-management owner-session aaa 573498 service-session “voice(1000000, 10.10.10.1)”
Example 3—Include a service session profile when you activate a subscriber’s service sessionhost1(config)#service-management owner-session aaa 426777 service-session “video(4500000, 192.168.10.3)” service-session-profile vodISP1
Use the no version to deactivate service sessions based on owner information. See Using the CLI to Deactivate Subscriber Service Sessions for more information about deactivating subscriber service sessions.
See service-management owner-session

service-management subscriber-session service-session

Use to activate a service for a subscriber by creating a subscriber session and a service session.

Note: Always activate at least one service session for a subscriber session. The ability to create a subscriber session without a service session (by omitting the service-session keyword) is not currently supported.

Use this command in Privileged Exec mode to create a dynamic subscriber session—dynamic sessions are deleted after a router reboot.
Use this command in Global Configuration mode to create persistent subscriber sessions that are retained across reboots.
Include the optional service-session-profile keyword to assign a profile to the service session. The service session profile includes additional attributes, such as the type of statistics to be captured for the service session.
You can create one subscriber session for a subscriber—and multiple service sessions for a particular subscriber session. If you create a second subscriber session for the same subscriber, only the newest subscriber session, with its services, is used.
Example 1—Activate a subscriber session with a single service session host1(config)#service-management subscriber-session client1@isp1.com interface atm 4/0.1 service-session “video(4500000, 192.168.10.3)”
Example 2—Activate a single subscriber session with multiple service sessionshost1(config)#service-management subscriber-session client1@isp1.com interface atm 4/0.1 service-session “video(4500000, 192.168.10.3)” host1(config)#service-management subscriber-session client1@isp1.com interface atm 4/0.1 service-session “tiered(1000000, 2000000)” host1(config)#service-management subscriber-session client1@isp1.com interface atm 4/0.1 service-session “voice(1000000, 10.10.10.1)”
Example 3—Include a service session profile when you activate a subscriber’s service sessionhost1(config)#service-management subscriber-session client1@isp1.com interface atm 4/0.1 service-session “video(4500000, 192.168.10.3)” service-session-profile vodISP1
Use the no version to deactivate service sessions. See Using the CLI to Deactivate Subscriber Service Sessions for more information about deactivating subscriber service sessions.
See service-management subscriber-session service-session

[Contents] [Prev] [Next] [Index] [Report an Error]