Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

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

    OnePopTunnel Scenario

    The OnePopTunnel scenario illustrates a configuration in which subscribers have a tunnel ID, as defined by the combination of the plug-in attributes PA_TUNNEL_ID, PA_TUNNEL_SESSION_ID, and PA_LAC_IP.

    The resolution process takes a subscriber’s Tunnel ID as the key and returns a reference to the SAE managing this subscriber as the value. Figure 1 depicts the resolution process for this scenario.

    Figure 1: Resolution Process for Tunnel Realm

    Resolution Process
for Tunnel Realm

    The following agents collect information for resolvers in this realm:

    • The SAE plug-in agent TunnelIdVr collects and publishes information about the mapping of TunnelId (Tunnel ID + Tunnel Session ID + LAC IP Address) to VRs.
    • The directory agent VrSaeId collects and publishes information about the mappings of VRs to SAEs.

    The OnePopTunnel sample provides a centralized configuration.

    Centralized Configuration

    In this configuration, a single host (DemoHost) supports all agents and resolvers. When the NIC proxy sends a subscriber’s TunnelId to host DemoHost, the following sequence of actions occurs:

    1. The host passes the tunnel ID to resolver A1.
    2. Resolver A1 obtains a VR name for the tunnel ID.
    3. Resolver A1 forwards the VR name to resolver B1.
    4. Resolver B1 obtains an SAE reference for the VR and returns the VR identity to resolver A1.
    5. Resolver A1 passes the SAE reference to its host.
    6. The host returns the SAE reference to the NIC proxy.

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

    Figure 2: OnePopTunnel Centralized Configuration

Centralized Configuration

    Published: 2014-12-10