Activating Subscriber Sessions by Using the CLI

You can use the CLI to activate a service session based on subscriber information or owner information. You can activate a service session by performing one of the following tasks:

Activating a Service for an Existing Subscriber

You can use the service-management owner-session command 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.

You can use this command in Privileged Exec mode to create a dynamic subscriber session—dynamic sessions are deleted after a router reboot. You can use this command in Global Configuration mode to create persistent subscriber sessions that are retained across reboots.

You can 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.

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.

You can 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.

Use the no version to deactivate service sessions based on owner information. See Deactivating Subscriber Service Sessions by Using the CLI Overview for more information about deactivating subscriber service sessions.

Creating and Activating a Service for a Subscriber

You can use the service-management subscriber-session service-session command 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.

You can use this command in Privileged Exec mode to create a dynamic subscriber session—dynamic sessions are deleted after a router reboot. You can use this command in Global Configuration mode to create persistent subscriber sessions that are retained across reboots.

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.

You can 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.

Related Documentation