This scenario describes an enterprise that is distributed across continents. The clients in the remote offices in the United States and Canada use the local DNS nameserver in Europe to resolve their DNS queries.
The enterprise's requirements are as follows:
The managers want to create new content and deliver it to a large number of employees quickly. They want employees to view training videos from their desktops instead of traveling to attend training.
The following illustration shows the deployment for the enterprise and the path of a request from a client to the closest GRM agent cache to the client that can serve the requested content.
In this scenario, a GRM L7 server is deployed in the data center so that requests from clients in the remote offices can be served by the GRM agent caches that are closest to those clients. Because GRM L7 server redirection is based on the client IP address, the GRM L7 server can determine which GRM agent caches are truly close to the clients. In contrast, a GRM DNS server sees only the IP address of the DNS server, not the IP address of the client.
The goal with GRM L7 redirection is to force all client requests to the GRM L7 server so that the GRM L7 server can redirect the requests based on client IP address. In this scenario, GRM DNS servers are deployed to force client requests to the GRM L7 server. This deployment is referred to as a mixed hierarchy.
The GRM L7 server is also configured as a GRM agent cache, which enables the cache to send proximity data to the GRM DNS servers. (Only GRM agents can send proximity data to GRM servers.) The GRM DNS server determines the closest GRM L7 server to direct the client to based, on the IP address of the client's local DNS nameserver and the proximity information it receives from each GRM DNS agent.
Copyright © 1994-2002, Network Appliance, Inc. All rights
reserved.
Part No. 210-00372
File: grmdply5.htm
Last updated: 11/13/02 18:12:10