Locating the SAE That Manages a Subscriber for the SRC-VTA
You can use NIC proxies if the SRC-VTA software needs to locate the SAE that manages a particular subscriber. For example, if the VTA receives an account update event and determines that it needs to reconfigure the corresponding SAE session, the VTA must find the SAE that is managing the session. The VTA can do this through the NIC.
You can also use the NIC with the SRC-VTA to allow the following:
- Automatically log in subscribers to the VTA Web portals—The NIC maps the subscriber’s IP address to the subscriber’s login name, DN, or name of the interface and VR to which the subscriber connects. This scenario is for subscribers who connect to the SRC network through a JUNOSe router.
- Immediately activate subscriptions to quota services—The
VTA immediately activates a subscriber’s quota service when
a deposit is made to the subscriber’s account. In this case,
the NIC maps the subscriber’s identifier to the SAE reference.
This scenario is for subscribers who connect to the network through
JUNOSe routers or JUNOS routing platforms.
If you do not set up a NIC for this purpose or you use an identifier that the NIC cannot map to an SAE reference, subscribers must log out and log in again before the VTA can activate their quota services when deposits are made to their accounts.
- Allow subscribers to log in with their IP addresses. The NIC maps the subscriber’s IP address to the identifier that you use for subscribers in the VTA database. To use the sample VTA portals, you must implement this type of NIC. If you do not implement this NIC, you can provide another way for subscribers to log in, such as a central Web page on which subscribers can enter their usernames and passwords. This scenario is for subscribers who connect to the SRC network through a JUNOSe router.