The OnePopPrimaryUser scenario is similar to one of the resolutions in the OnePopLogin scenario. In the OnePopPrimaryUser scenario, subscriber primary username, as identified by the PA_PRIMARY_USER_NAME attribute, is resolved to a reference for a managing SAE. The realm for this configuration accommodates a situation in which a NIC proxy provides a primary username.
Figure 1 show the resolution graph for this realm.
The following agents interact with resolvers in this realm:
Directory agent VrSaeId collects and publishes information about virtual routers and the mappings between virtual routers and SAEs.
SAE plug-in agent UserNameVr collects and publishes information about the mappings of subscriber primary usernames to VR names.
The OnePopPrimaryUser scenario provides two host configurations: a centralized configuration and a distributed configuration.
In this configuration, a single host called DemoHost supports all agents and resolvers. When a NIC proxy send a subscriber’s primary username to host Demo Host, the following sequence of events occurs:
The host passes the primary username to resolver A1.
(Optional) Resolver A1 resolves the primary username to its domain.
Resolver A1 forwards the primary username to resolver B1.
Resolver B1 obtains the name of the VR associated with the subscriber’s primary username and returns the VR to resolver A1.
Resolver A1 forwards the VR to resolver C1.
Resolver C1 obtains the SAE reference for the SAE managing the VR and returns the SAE reference to resolver A1.
Resolver A1 returns the SAE reference to the host.
The host returns the SAE reference to the NIC proxy.
Figure 2 illustrates the interactions of the NIC components for this realm.
In this configuration, the agents and resolvers are distributed among two hosts, When a NIC proxy sends a subscriber’s primary username to the host OnePopBO, the resolvers execute the same actions as they do in the centralized configuration. Figure 3 illustrates the interactions of the NIC components for this realm.