This scenario is similar to the OnePop configuration scenario. It illustrates a configuration in which an assigned subscriber IP address managed by a network device such as a cable modem termination system (CMTS) device resolves to a reference to the SAE managing this subscriber. In this situation, the SAE acts as an application manager and interacts with the CMTS through a policy server.
The OnePopPcmm configuration scenario supports a PacketCable Multimedia Specification (PCMM) environment in which you use the assigned IP subscriber method to log in subscribers and in which you use the NIC to determine the subscriber’s SAE. The realm for this configuration accommodates the situation in which IP pools are configured locally on each application manager group object. These IP pools represent an IP pools-managed policy decision point (PDP) group for one or more CMTS devices.
Figure 23 shows the resolution graph for this realm.
This scenario uses the same agents as the OnePop scenario. For the OnePopPcmm configuration scenario, the agent collects information from the application manager object instead of the virtual router entry. A virtual router name is generated in the format "default"@<pdpGroup>.
The OnePopPcmm scenario provides two host configurations: a centralized configuration and a distributed configuration.
In this configuration, the single host DemoHost supports all agents and resolvers. When a NIC proxy sends a subscriber’s IP address to host DemoHost, the following sequence of actions occurs:
The host passes an assigned subscriber IP address resolver A1.
Resolver A1 obtains the IP pool name and the interface name, and forwards the request to resolver B1.
Resolver B1 obtains the VR name for the IP pool name and interface name, and returns the VR name to resolver A1.
Resolver A1 forwards the VR name to resolver C1.
Resolver C1 obtains an SAE reference for the VR and returns it to resolver A1.
Resolver A1 passes the SAE reference to its host.
The host returns the SAE reference to the NIC proxy.
Figure 24 show the interactions of the NIC components for this realm.
In this configuration, the agents and resolvers are distributed among two 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 25 illustrates the interactions of the NIC components for this realm.