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.
Related Documentation
- Creating and Configuring an SRC VTA Shared Group Configuration (SRC CLI)
- SRC VTA Overview
- Configuring a Database to Store Account and Session Data (SRC CLI)
- Configuring the Initial Balance and Status of a Subscriber Account in the External Database (SRC CLI)
- Keys Used to Specify the Subscriber ID Solution (SRC CLI)
- Example: Limiting Subscriber Access Based on Account Balances