What you need to plan for

GRM servers

Plan the type and number of GRM servers you need. Consider the type of redirection that you need to support your organization's requirements.

Section B, Components of a GRM deployment; Chapter 2, Examples of GRM Deployments. Number of GRM servers

Determine whether you need GRM domains.

• If you are deploying GRM with ContentDirector 2.0.1 and later

  ContentDirector can automatically detect domains. See the ContentDirector documentation for more information.

• If you are not deploying GRM with ContentDirector 2.0.1 and later

  You must add GRM domains to the NetCache configuration.  

GRM domains and their use for IP address filtering

GRM agent caches

Plan the number of center and edge caches you need and where to locate them.

Determining the types of GRM agent caches you need; Section E, Failover strategies

Determine the protocols that each GRM agent cache will handle.

Determining the protocols to run on a GRM agent cache

Content management

Decide whether you want to use ContentDirector to push content to your caches.

The chapter on pushing content in the Deployment Guide and the ContentDirector product documentation (available at http://now.netapp.com).

Plan how you want to set up host-name rewriting to handle cache misses for CDN content that is not cached on a GRM agent cache and, therefore, must be fetched from a CDN origin server.

How GRM obtains content

DNS requirements for GRM DNS servers

Decide how to set up the interaction between the DNS back-end nameserver and the GRM DNS server.

Section A, Planning for interaction with a back-end DNS nameserver

Determine the method that you need to use to support DNS queries for CDN content.

Section B, Planning for supporting queries for CDN content