OnePop Scenario

The OnePop scenario illustrates a configuration that supports one POP. The realm for this configuration accommodates the situation in which IP address pools are configured locally on each VR. The resolution process takes a subscriber’s IP address as the key and returns a reference to the SAE managing this subscriber as the value.

Figure 15 shows the resolution graph for this realm.

Figure 15: Resolution Process for ip Realm

The following agents collect information for resolvers in this realm:

• Directory agent PoolVr collects and publishes information about the mappings of IP address pools to VRs.
• Directory agent VrSaeId collects and publishes information about the mappings of VRs to SAEs.

The OnePop sample provides two host configurations: a centralized configuration and a distributed configuration. The OnePop Centralized configuration also provides an example of NIC host redundancy.

Centralized Configuration

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

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

Figure 16 shows the interactions of the NIC components for this realm.

Figure 16: OnePop 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 host OnePopBO, the components execute the same actions as they do in the centralized configuration.

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

Figure 17: OnePop Distributed Configuration

Redundancy

This sample data includes host redundancy for the centralized configuration. The hosts DemoHost/One and DemoHost/Two, which are installed on different machines, provide host redundancy. These hosts form the community DemoHost, which does not include a monitor.

Figure 18: Redundancy for OnePop Centralized Configuration

Related Topics

• Overview of NIC Configuration Scenarios
• Configuring a NIC Scenario (SRC CLI)

Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.