Using One SRC VTA Account for Multiple Subscriber Sessions
The SRC VTA allows multiple subscriber sessions to share the same SRC VTA account. The SRC VTA debits usage for all the subscriber sessions from the account. When the account is empty, service sessions for all subscribers are stopped. When the account is refilled, the SRC VTA starts services for all subscriber sessions that share the account.
To use this feature, you use the subscriberId event attribute to map a group of subscribers to the SRC VTA account. You then use the accounting-id attribute as the subscriber-id-solution parameter under the shared vta group name configuration statement. For information about this option, see Creating and Configuring an SRC VTA Shared Group Configuration (SRC CLI). You also set up the NIC to use the accounting ID to look up the SAE that manages a subscriber.
To set up the SRC software to use one SRC VTA account for multiple subscribers:
In the subscriber classifier script, assign a value to the accountingUserId attribute. For example, you could assign it to the userName, interfaceName, loginName, or a combination of classification criteria. The purpose of the assignment is to allow the SRC VTA to identify subscribers by many different subscriber attributes using accountingUserId as a wrapper.
For example, the following subscriber classifier script assigns the value of the userName to the accountingUserId attribute:[<-retailerDn->?accountingUserId=<-userName->?sub?(uniqueID=<-userName->)]
Configure the SAE to publish the PA_ACCOUNTING_ID plug-in attribute in subscriber-tracking events to the NIC SAE agent plug-in.
Configure the NIC to use the OnePopAcctId NIC scenario.
Configure the SRC VTA shared group configuration in the SRC CLI as follows:
For the subscriber-id-solution option enter accounting-id.
For the nic-proxy option, enter the name of the NIC proxy configuration you entered for the shared vta nic-proxy-configuration name statement. Be sure to configure the NIC proxy so that it uses a NIC that maps from the accounting ID to the SAE.
(Optional) Set up an action to apply functions to all subscriber sessions that share the same SRC VTA account. For example, the following action starts services for all subscriber sessions that have the same subscriber ID.[edit shared vta group vta1]user@host# edit action xyz[edit shared vta group vta1 action xyz]user@host#y# set function sae-start-service[edit shared vta group pear action xyz]user@host## show
function sae-start-service; parameter;
Make sure that the current-subscriber-only option is set to false (not present). If it is set, delete it.