Managing SRC VTA Accounts and Sessions Overview
The SRC VTA allows service providers to manage accounts and sessions by:
Identifying Subscribers, SAEs, and Sessions
The SRC VTA must be able to identify each subscriber by a unique identifier. The SRC VTA uses the identifier to manage:
SRC VTA accounts and sessions
Subscriber and service sessions
You can configure the SRC VTA to use data keys to identify corresponding data values for these management tasks. The data keys depend on the subscriber’s identifier and comprise one or more plug-in attributes. Some identifiers are suitable for residential subscribers and some for enterprise subscribers.
Managing SRC VTA Accounts and Sessions
Depending on the information that identifies subscribers in your SRC configuration, you can configure the SRC VTA to use several types of plug-in attributes as data keys to identify accounts and sessions in the SRC VTA database. If you use a NIC with the SRC VTA, the SRC VTA can also use some of these plug-in attributes to construct a data key that the NIC can use to determine which SAE manages a subscriber. When the NIC identifies an SAE, the SRC VTA can also obtain a key to identify the subscriber session that the SAE is managing for the subscriber.
You configure the data keys that identify accounts and sessions with the shared vta group name statement and specifying the data keys by setting the subscriber-id-solution option.