Overview of Activating Subscriber Service Sessions Using the CLI

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.
• 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.

  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 Creating Service Definitions, the template name is: <# tiered(inputBW, outputBW) #> Use the following format with the service-session keyword: “ tiered(1280000, 5120000)”