Related Documentation
Keys Used to Specify the Subscriber ID Solution (SRC CLI)
You use the subscriber-id-solution option under the shared vta group name configuration statement to specify keys for managing accounts and sessions. Table 1 shows the keys that you can specify for the SRC VTA to query the database, NIC, and SAE. For the SRC VTA to use a subscriber identifier, the plug-in event must include the corresponding NIC or SAE attributes that are listed in Table 1 (attributes that start with PA_). For more information about plug-in attributes, see the documentation for the SAE CORBA plug-in on the Juniper Networks website at
Table 1: Keys That the SRC VTA Constructs to Manage Accounts and Sessions
Subscriber’s Identifier | Database Key | Corresponding NIC Key | Corresponding SAE Key |
|---|---|---|---|
accounting-id | PA_ACCOUNTING_ID | PA_ACCOUNTING_ID | IP address that is returned from the NIC lookup |
user-dn | PA_USER_DN | PA_USER_DN | PA_USER_DN |
interface-alias | PA_INTERFACE_ALIAS | None | None |
interface-alias-and-router | PA_INTERFACE_ALIAS@ | PA_ROUTER_NAME | None |
interface-and-router | PA_INTERFACE_NAME@ | PA_ROUTER_NAME | PA_INTERFACE_NAME |
login-name | PA_LOGIN_NAME | PA_LOGIN_NAME | PA_LOGIN_NAME (default) |
mac-address | PA_USER_MAC_ | None | None |
primary-user-name (PPP login name or public DHCP name) | PA_PRIMARY_USER_ | None | PA_PRIMARY_USER_ |
nas-port-id-and-router | PA_PORT_ID@ | None | None |
login-name, user-dn, and interface-and-router also provide data keys for the NIC and the SAE; the other settings do not.
