Using SRC-VTA Keys to Manage Accounts and Sessions
Table 1 shows the
keys that you can specify for the SRC-VTA to query the VTA database,
NIC, and SAE. For the SRC-VTA to use a subscriber identifier, the
plug-in event must include the corresponding attribute(s) that are
listed in the subscriber identifier row (attributes start with PA_).
For more information about plug-in attributes, see the documentation
for the SAE CORBA plug-in on the Juniper Networks Web site at
-
http://www.juniper.net/techpubs/software/management/src/api-index.html
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
|
|
Subscriber DN
|
PA_USER_DN
|
PA_USER_DN
|
PA_USER_DN
|
|
Interface alias
|
PA_INTERFACE_ALIAS
|
None
|
None
|
|
Interface alias & VR
|
PA_INTERFACE_ALIAS@ PA_ROUTER_NAME
|
PA_ROUTER_NAME
|
None
|
|
Interface name & VR
|
PA_INTERFACE_NAME@ PA_ROUTER_NAME
|
PA_ROUTER_NAME
|
PA_INTERFACE_NAME
|
|
Login name
|
PA_LOGIN_NAME
|
PA_LOGIN_NAME
|
PA_LOGIN_NAME
(default)
|
|
MAC address
|
PA_USER_MAC_ ADDRESS
|
None
|
None
|
|
PPP login name or public DHCP name
|
PA_PRIMARY_USER_ NAME
|
None
|
PA_PRIMARY_USER_ NAME
|
|
Port on router
|
PA_PORT_ID@ PA_ROUTER_NAME
|
None
|
None
|