Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    OnePopLogin Scenario

    This scenario illustrates a configuration that is very similar to the OnePop scenario. The realm for this configuration accommodates two independent resolution processes, which are used by the SRC Volume Tracking Applications (SRC VTAs) and may be used for other purposes.

    Figure 1 shows the resolution graphs for this realm.

    Figure 1: Resolution Processes login Realm

    Resolution Processes login Realm

    The following agents interact with resolvers in this realm:

    • SAE plug-in agent IpLoginName collects and publishes information about the mappings of IP addresses to login names.
    • SAE plug-in agent LoginNameVr collects and publishes information about the mappings of login names to VRs.
    • Directory agent Pool collects and publishes information about the IP address pools used by the VRs in a POP. The agent uses the information about the IP address pools to determine which resolver to communicate with, rather than communicating with all resolvers that are running role D.
    • Directory agent VrSaeId collects and publishes information about the mappings of VRs to SAEs.

    The OnePopLogin scenario provides two host configurations: a centralized configuration and a distributed configuration.

    Centralized Configuration

    In this configuration, single host DemoHost supports all agents and resolvers. Two NIC proxies are associated with this NIC configuration; one NIC proxy (called NIC proxy 1 in this documentation) submits subscribers’ login names, and the other (called NIC proxy 2 in this documentation) submits subscribers’ IP addresses.

    When NIC proxy 1 sends a login name to the host DemoHost, the following sequence of events occurs:

    1. The host passes the login name to resolver A1.
    2. Resolver A1 obtains a domain name for the login name.
    3. Resolver A1 forwards the login name and the domain to resolver B1.
    4. Resolver B1 obtains a VR name for the login name and returns the VR name to resolver A1.
    5. Resolver A1 forwards the VR name to resolver C1.
    6. Resolver C1 obtains an SAE reference for the VR and returns the SAE reference to resolver A1.
    7. Resolver A1 returns the SAE reference to its host.
    8. The host returns the SAE reference to the NIC proxy.

    When NIC proxy 2 sends a subscriber’s IP address to host DemoHost, the following sequence of events occurs.

    1. The host passes the IP address to resolver A1.
    2. Resolver A1 obtains an IP pool for the IP address.
    3. Resolver A1 forwards the IP address and the IP pool to resolver D1.
    4. Resolver D1 obtains a login name for the IP address and returns the login name to resolver A1.
    5. Resolver A1 passes the login name to its host.
    6. The host returns the login name to the NIC proxy.

    Figure 2 illustrates the interactions of the NIC components for this realm.

    Figure 2: OnePopLogin Centralized Configuration

    OnePopLogin Centralized Configuration

    Distributed Configuration

    In this configuration, the agents and resolvers are distributed among several hosts. When the NIC proxy sends a subscriber’s IP address to the host OnePopBO, the resolvers execute the same actions as they do in the in the centralized configuration. Figure 3 illustrates the interactions of the NIC components for this realm.

    Figure 3: OnePopLogin Distributed Configuration

    OnePopLogin Distributed Configuration

    Modified: 2016-12-29