Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Management of Subscriber Services with Multiple Instances

Subscriber Services with Multiple Instances Overview

Services are activated for subscribers either at login, or by using Change of Authorization (CoA) RADIUS messages or command-line interface (CLI) requests. A subscriber can have multiple instances of the same named service, provided that each instance of the subscriber service has a different set of parameters. Support for multiple instances of a subscriber service enables you to use service parameters to customize the same service to meet different needs for a particular subscriber.

Subscriber Service Instances and Service Parameters

In a subscriber access network, each subscriber has its own set of services. You can configure a specific service instance for a particular subscriber by specifying a service name, also referred to as a service profile, and unique service parameters for that service instance. Service parameters can include a combination of policy lists, filters, rate-limit profiles, class of service (CoS) profiles, and interface profiles.

For example, filter-service(up-filter,down-filter) and filter-service(upstream-filter,downstream-filter) are considered two different instances of the same service (filter-service) because their parameters, enclosed in parentheses after the service name, are different.

Each service instance is uniquely identified by the combination of its service name and service parameters. In CoA messages, the router identifies a subscriber service by its complete activation string, which consists of the service name and, if configured, one or more service parameters in the order specified.

CLI Deactivation of Subscriber Services with Multiple Instances

You can use the Junos OS CLI to deactivate subscriber services with multiple instances in either of the following ways:

  • Deactivate a single instance of a subscriber service by specifying the name and parameters of the service to be deactivated.

    With this feature, you can deactivate a particular instance of a subscriber service while other instances of that same service remain active. For example, assume that a subscriber identified by a particular session ID has two instances of filter-service activated: filter-service(up-filter,down-filter) and filter-service(upstream-filter,downstream-filter). If you specify “filter-service(up-filter,down-filter)” in the request network-access aaa subscriber delete session-id command, the router deactivates only filter-service(up-filter,down-filter); filter-service(upstream-filter,downstream-filter) remains active.

    The ability to use both service names and service parameters to identify the particular service instance to be deactivated is analogous to the subscriber service deactivation feature in use on Juniper Networks E Series Broadband Services Routers that run JunosE Software.

  • Deactivate all instances of a subscriber service by specifying only the name of the service to be deactivated, with no service parameters.

    With this feature, you can deactivate all instances of the same subscriber service with a single operational command. Using the same subscriber service example, if you specify “filter-service” in the request network-access aaa subscriber delete session-id command, the router deactivates both filter-service(up-filter,down-filter) and filter-service(upstream-filter,downstream-filter).

Subscriber Services with Multiple Instances in RADIUS Accounting Messages

RADIUS Acct-Start, Interim-Acct, and Acct-Stop accounting messages include the subscriber service name and, if configured, service parameters. If RADIUS logging is enabled, the router logs all subscriber service attributes, including service names and parameters, in messages sent to and received from the RADIUS authentication server.

For example, assume that the router receives the following RADIUS Access-Accept message from the RADIUS server:

Table 1 shows sample logged RADIUS Acct-Start, Interim-Acct, and Acct-Stop messages that the router sends to the RADIUS server in response to the Access-Accept message. In each of these accounting messages, the Activate-Service-Session-Name is the full activation string that includes both the service name (filter-service) and service parameters (up-filter,down-filter) to identify the service instance.

Table 1: Subscriber Services and Service Parameters in RADIUS Accounting Messages

RADIUS Accounting Message Type

RADIUS Accounting Message Text

Acct-Start

Jul 13 12:37:02 radius-acct-start: Activate-Service-Session-Name (Juniper-ERX-VSA) added: filter-service(up-filter,down-filter)

Interim-Acct

Jul 13 12:47:00 radius-acct-interim: Activate-Service-Session-Name (Juniper-ERX-VSA) added: filter-service(up-filter,down-filter)

Acct-Stop

Jul 13 12:53:59 radius-acct-stop: Activate-Service-Session-Name (Juniper-ERX-VSA) added: filter-service(up-filter,down-filter)

Deactivating a Single Instance of a Subscriber Service

For subscriber services that have multiple instances, you can use the Junos OS CLI to deactivate a service in either of the following ways:

  • Deactivate a single instance of a service by specifying the name and parameters of the service to be deactivated.

  • Deactivate all instances of a service by specifying only the name of the service to be deactivated.

This topic describes how to deactivate a single instance of a subscriber service.

To use the Junos OS CLI to deactivate a single instance of a subscriber service with multiple instances:

  1. Display the active services for the subscriber identified by the specified session ID.

    For example, the following command displays the active services for the DHCP subscriber identified by session ID 6. In this example, two instances of economy-service are active: economy-service(up-filter,down-filter) and economy-service(upstrm-filter,dwnstrm-filter). A single instance of premium-service named premium-service(up-filter,down-filter) is also active.

  2. Deactivate the specified instance of a subscriber service by specifying its service name and parameters.

    For example, the following command deactivates only the instance of economy-service named economy-service(up-filter,down-filter).

  3. (Optional) Verify that the deactivated service instance is no longer active for the subscriber.

    For example, the following command displays the services still active for the DHCP subscriber identified by session ID 6. In this example, economy-service(up-filter,down-filter) is no longer listed because it was deactivated, but economy-service(upstrm-filter,dwnstrm-filter) and premium-service(up-filter,down-filter) are still active.

Deactivating All Instances of a Subscriber Service

For subscriber services that have multiple instances, you can use the Junos OS CLI to deactivate a service in either of the following ways:

  • Deactivate a single instance of a service by specifying the name and parameters of the service to be deactivated.

  • Deactivate all instances of a service by specifying only the name of the service to be deactivated.

This topic describes how to deactivate all instances of a subscriber service.

To use the Junos OS CLI to deactivate all instances of a subscriber service with multiple instances:

  1. Display the active services for the subscriber identified by the specified session ID.

    For example, the following command displays the active services for the DHCP subscriber identified by session ID 6. In this example, two instances of economy-service are active: economy-service(up-filter,down-filter) and economy-service(upstrm-filter,dwnstrm-filter). A single instance of premium-service named premium-service(up-filter,down-filter) is also active.

  2. Deactivate all instances of the specified service by specifying the service name without parameters.

    For example, the following command deactivates both instances of economy-service.

  3. (Optional) Verify that all instances of the deactivated service are no longer active for the subscriber.

    In the following example, only premium-service(up-filter,down-filter) is still active. Neither economy-service(up-filter,down-filter) nor economy-service(upstrm-filter,dwnstrm-filter) is listed because all instances of economy-service were deactivated.

Verifying Subscriber Services with Multiple Instances

Purpose

Display information about the active services for a subscriber identified by the specified session ID.

Action

The following example displays information about the active services for the DHCP subscriber identified by session ID 6.

Meaning

If parameters are configured when a subscriber service with multiple instances is activated, the Service name field in the show network-access aaa subscribers session-id command displays both the service name and, in parentheses following the service name, the service parameters. If parameters are not configured for a particular service, the show network-access aaa subscribers session-id command displays only the service name. The value SvcActive in the Service State field indicates that the service is active.

In this example, two instances of economy-service are active: economy-service(up-filter,down-filter) and economy-service(upstrm-filter,dwnstrm-filter). For premium-service, which is also active, the command output displays only the service name, indicating that no parameters were configured for this service.