Numerics A B C D E F G H I L M N O P Q R S T U W X Z
Index
Numerics
- 302 location changed response
- 302 redirection response
A
- accelerator rules
- when to use for content handling
- alias for appliance interface
- application-level redirection, defined
- ASX file
- how L7 redirection occurs with
- authoritative DNS nameserver
- defined
- GRM DNS server interaction with
- assuming identity of
- authoritative for CDN name space
- passing query to nameserver
- proxying DNS requests to
- taking over for
- recursive DNS queries and
- testing connectivity to
- automatic proxy configuration file
- browsers that support
- use with GRM L7 server
- example
- load balancing with
- uploading to appliance
- what you modify
B
- back-end DNS nameserver
- associating with GRM domains
- defined
- GRM DNS server proxying requests for
- GRM DNS server taking over for
- testing connectivity to
- billing for content
- binding GRM domains to protocols
C
- cache hit, defined
- cache miss
- defined
- how GRM handles
-
- CDNs
- defined
- goals for CDN service
- requirements that GRM fulfills
- strategy when spread over continents
- center caches
- as edge caches also
- characteristics
- defined
- failover for edge caches
- license requirement for
- load balancing over
- planning for
- protocol services on
- proximity data provided
- status to GRM server
- CPU load
- proximity
- system health
- testing client redirection to
- when needed
- center groups, defined
- CIDR address
- association with an edge group
- defined
- GRM server evaluation of
- CIDR blocks
- association with an edge group
- defined
- GRM server evaluation of
-
- CNAME defined
- CNAME records
- defined
- when URL rewriting is used
- CNAME rewriting
- advantage of
- defined
- DNS configuration to support
- when to use
- configuration overview, GRM
- content handling with GRM
- accelerator rules
- when to use
- billing for content
- DNS CNAME rewriting
- when to use
- fetching Internet content
- how content is obtained
- methods
- when GRM L7 server serves
- ContentDirector
- planning for use with GRM
- product description
- pushing content to GRM caches
- ContentReporter
- billing for content
- product description
- where to obtain
- CPU load, GRM server evaluation of
D
- dig utility
- defined
- identifying DNS lookup TTL
- initiating a zone transfer
- DNS
- defined
- GRM handling specific domains
- requirements to support GRM DNS server
- configuration overview
- routing with GRM
- DNS CNAME rewriting
- advantage of
- defined
- DNS configuration to support
- when to use
- DNS nameserver
- authoritative
- IP address to GRM DNS server
- configuring for URL rewriting
- redirection to GRM L7 server
- disadvantages of
- DNS queries
- non-CDN, GRM DNS server resolving
- proxying by GRM DNS server
- recursive
- DNS-based redirection
- DOC files
- how L7 redirection works with
-
- domains, GRM
- and multiple CDNs
- DNS domains and
- filters for
E
- edge caches
- as center caches also
- characteristics
- defined
- failover to center caches
- license requirement for
- load balancing over
- planning for
- protocol services on
- status to GRM server
- CPU load
- proximity
- system health
- testing
- client redirection to
- reporting to GRM server
- when needed
- edge groups
- CIDR address associated with
- defined
- testing client redirection to
- enterprises spread over continents
- deployment strategy
F
- failover, GRM
- center cache, testing
- deployment strategies
- edge caches to center caches
- edge group, testing
- if no GRM agent caches exist
- method provided
- reasons for using
- filtering for GRM domains
- group filter
- location filter
- protocol filter
- firewalls
- blocking GRM proximity messages
- troubleshooting for GRM
- Force Redirection option, described
- FQDNs
- and CNAME rewriting
- using as domain filters
- with GRM domains
-
G
- GRM
- advantage over transparent proxying
- communication port
- components
- center caches
- edge caches
- GRM agent caches
- GRM servers
- configuration overview
- content handling with
- caches misses
- how content is obtained
- methods
- taking over DNS
- URL rewriting
- deployments
- components
- when to deploy a GRM DNS server
- when to deploy a GRM L7 server
- DNS configuration to support
- failover
- if no GRM agent caches exist
- methods
- reasons for using
- how GRM works
- licensing requirements
- planning summary
- port for communication
- redirection methods
- testing
- troubleshooting
- configuration
- with CDN clients
- GRM agent caches
- defined
- determining how many needed
- determining types needed
- fetching Internet content
- requirements
- license
- load balancing over
- protocols to run on
- status to GRM server
- types
- GRM DNS servers
- assigning IP address aliases
- content handling with
- GRM domain list entries
- handling all DNS queries
- URL rewriting
- deployment example
- determining location of
- directing requests to GRM L7 servers
- advantages and disadvantages
- DNS requirements
- configuration to support
- DNS requirements for
- failover
- load balancing mechanisms
- multiple back-end DNS servers with
- proximity measurements with
- proxying of DNS queries
- queries for CDN content
- methods to support
- queries for non-CDN DNS queries, resolving
- redirection method
- redirection to GRM L7 servers
- testing configuration
- testing connectivity to a DNS server
- when IANA database is used for proximity
- when to deploy
- GRM domains
- and multiple CDNs
- defined
- DNS domains and
- filters for
- examples
- FQDNs and
- group
- how filters work together
- location
- protocols
- when to set
- FQDNs with
- identifying to GRM server
- multiple back-end nameservers, association with
- GRM L7 servers
- deployment example
- DNS nameserver for redirection to
- GRM DNS server for redirection to
- network infrastructure for redirection to
- proxy.pac file for redirection to
- failover
- load balancing mechanisms
- overload with DNS nameserver redirection
- proximity measurement with
- redirection method
- redirection of requests for large files
- redirection to
- DNS nameserver
- methods
- using a GRM DNS server
- using a proxy.pac file
- using the network infrastructure
- request rewriting, how it works
- 302 request redirection response
- with HTTP content
- with streaming content
- when they serve content directly
- when to deploy
- GRM server access log
- checking after configuration
- IP addresses returned
- GRM servers
-
- center caches
- mechanisms to determine proximity
- proximity measurements
- consideration of proximity data
- defined
- factors determining IP addresses returned
- failover
- functions
- GRM domains
- filtering
- role of
- handling non-GRM content
- identifying GRM domains
- license requirement for
- location of
- number needed
- proximity measurements with
- status from GRM agent caches
- communication protocol used
- types
- GRM DNS server
- GRM L7 server
- GRM testing
- center cache failover
- clients outside edge groups
- connectivity to back-end nameserver
- edge group failover
- edge group redirection
- overview
- reporting of GRM agent caches
H
- Host header
- host-name rewriting
- methods for
- using accelerator rules
- using CNAME rewriting
- HTTP Redirection Suffix option, use of
- HTTP, L7 request rewriting with
I
- IANA database
- use for proximity measurements
- Installed Base Group, license purchase
- interface aliases
- IP addresses
- authoritative DNS nameserver
- to GRM DNS server
- returned by GRM server
- how determined
- viewing
L
- L4 switch versus GRM
- L7 redirection, defined
- L7 request rewriting
- with HTTP content
- with streaming content
- license
- center cache
- edge cache
- GRM agent caches
- licensing requirements for GRM
- load balancing
- automatic proxy configuration file
- GRM DNS server mechanism
- GRM L7 server mechanism
- how GRM server handles
- proxy.pac file
- load, CPU
- local DNS nameservers
- IP address list from GRM DNS server
- how long cached
- proximity measurements to
- DNS configuration to support
- obstacles
- recursive queries
- problem with
- sending queries to GRM server
- locator device in network
- directing requests to GRM L7 server
- transparent proxying
- how it differs from GRM
- log files
- GRM server
- viewing
- GRM server access log
- configuration testing
- log files, GRM server
- creating reports with
M
-
- mixed hierarchy, defined
- MMS, defined
N
- nslookup, defined
O
- Origin Server Failover option
P
- PDF files
- how L7 redirection works with
- planning for GRM
- configuration planning
- ContentDirector use
- ContentReporter use
- deployment considerations
- port for GRM communication
- PPT files
- how L7 redirection works with
- protocols
- binding GRM domains to
- running on GRM agent caches
- proximity data
- client-to-edge cache
- how determined
- GRM DNS servers
- DNS configuration to support
- GRM server consideration of
- how center caches provide
- if GRM DNS server has none
- if GRM L7 server has none
- measurements
- problem with LDNS recursive queries
- with center caches
- mechanisms to determine proximity
- proxy.pac file
- browsers that support
- use with GRM L7 server
- example
- load balancing with
- uploading to appliance
- what you modify
- pure GRM server deployment, defined
Q
- queries for CDN content
- support needed for GRM DNS server
R
- recursive queries with LDNS
- problem for GRM DNS server
- redirection methods available with GRM
- request routing
- for CDNs spread over continents
- with L4 switches
- RTSP
- defined
- L7 request rewriting with
S
- status sent to GRM server
- communication protocol used
- CPU load
- proximity data
- system health
- streaming media
- defined
- L7 request rewriting with
- streaming media cache, defined
- system health, sent to GRM server
T
- TCP port 89
- firewalls and
- used for GRM communication
- testing GRM
- center cache failover
- client to GRM agent cache redirection
- clients outside edge groups
- connectivity to authoritative DNS nameserver
- edge group failover
- edge group redirection
- network
- overview
- reporting of GRM agent caches
-
- transparent proxying
- defined
- how it differs from GRM
- troubleshooting GRM
- configuration
- with CDN clients
- TTL, LDNS
- caching and
U
- URL rewriting
- defined
- GRM domain listings for
- returning CNAME
- when used
- URL, defined
W
- WCCP routers, defined
- Web cache, defined
- WebWasher ContentReporter
- billing for content
- described
- where to obtain
X
- XLS files
- how L7 redirection works with
Z
- zone transfer, defined
Numerics A B C D E F G H I L M N O P Q R S T U W X Z
Copyright © 1994-2002, Network Appliance, Inc. All rights
reserved.
Part No. 210-00374
File: bookix.htm
Last updated: 11/12/02 17:45:20