SDX 6.4.x Application Library Guide > Overview of Controlling Volume Usage with the VTA > Identifying Subscribers, SAEs, and Sessions

Identifying Subscribers, SAEs, and Sessions

The VTA must be able to identify each subscriber by a unique identifier. The VTA uses the identifier to manage:

• VTA accounts and sessions
• Subscriber and service sessions

You can configure the 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. Because the SDX software supports only enterprise subscribers on JUNOS routing platforms, you cannot use some identifiers with JUNOS routing platforms.

Managing VTA Accounts and Sessions

Depending on the information that identifies subscribers in your SDX configuration, you can configure the VTA to use several types of plug-in attributes as data keys to identify accounts and sessions in the VTA database. If you use a NIC with the VTA portals, the 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 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 in the VTA Subscriber ID field. See Configuring Identifiers for Subscribers and Sessions.

Table 31 shows the keys that you can specify for the VTA to query the VTA database, NIC, and SAE. For the 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/sdx/api-index.html 

 Table 31:  Keys That the 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



 

Managing Subscriber Sessions and Service Sessions

When the VTA receives plug-in events, it may need to start or stop a subscriber session or service session. The plug-in events identify the SAE that manages a subscriber; however, the VTA must construct a data key from one or more plug-in attributes to identify the subscriber session or service session. Depending on the information that identifies subscribers in your SDX configuration, you must configure the VTA to use the keys shown in Table 32. You configure these data keys in the SAE Subscriber Lookup field. See Configuring Identifiers for Subscribers and Sessions.

 Table 32:  Keys That the VTA Constructs to Manage Subscriber and Service Sessions 

 Subscriber's Identifier
 SAE Key

 DN

 PA_USER_DN


 Interface name on router

 A combination of the following plug-in attributes:

  
 PA_INTERFACE_NAME
  
 PA_ROUTER_NAME



 IP address

 A combination of the following plug-in attributes:

  
 PA_USER_IP_ADDRESS
  
 PA_EVENT_TIME



 IP address of the subscriber on an interface 

 A combination of the following plug-in attributes:

  
 PA_USER_IP_ADDRESS
  
 PA_INTERFACE_NAME
  
 PA_ROUTER_NAME



 Login name

 PA_LOGIN_NAME


 PPP login name or public DHCP name 

 PA_PRIMARY_USER_NAME