Using the network infrastructure to locate a GRM L7 server

Using a device in the networking infrastructure to locate the GRM L7 server

If your network has in place an intelligent means of selecting the closest GRM L7 server, you can use your network infrastructure to direct client requests to the GRM L7 servers, as the following example shows.

In this type of deployment, all GRM L7 servers are authoritative for the same set of domains, and they all maintain proximity information for the agent caches within those domains. Transport time is saved because the device in the network infrastructure selects the GRM L7 server that is close to the client. For example, the request from a client in Asia is sent to the GRM L7 server in Asia, not to the GRM L7 server in the United States or Australia.

The following table describes the path of the request in the previous illustration.

Stage	Description
1	The client makes a request (www.netapp.com in the example), which is received by the networking infrastructure.
2	The networking infrastructure identifies the closest GRM L7 server to the client. It then redirects the client to that GRM L7 server. (The method used to identify the closest GRM L7 server varies by device.)
3	The client sends the request to the closest GRM L7 server.
4	The GRM L7 server applies its policies and other criteria to determine eligible caches and determines which GRM agent cache is closest to the client. The GRM L7 server then sends the rewritten request back to the client.
5	The client sends the request to the GRM agent cache to which it was redirected.
6	The cache delivers the content to the client.