Table Of Contents
Global Server Load Balancing Summary
Global Server Load Balancing Summary
After you create your GSSM (primary and standby) and GSS devices and configure them to connect to your network, you can begin to configure request routing and global server load balancing on your GSS network. When you perform GSLB configuration and monitoring for your GSS network, in most cases you have the option of using either the centralized GUI or CLI on the primary GSSM.
For tasks that you can perform using either the CLI or the GUI of the primary GSSM, choosing when to use the CLI or the GUI is a matter of personal or organizational choice. However, not every GSLB configuration and monitoring task is available from the GUI and the CLI of the primary GSSM. A few examples include:
•
You configure sticky and proximity groups using the CLI of the primary GSSM
•You create DNS view filters using the GUI of the primary GSSM
•You perform sticky database and proximity database management using the CLI of each GSS device.
For an overview of different global server load-balancing configuration tasks that you can perform from either the primary GSSM GUI or CLI, from only the primary GSSM GUI , or from only the primary GSSM CLI, refer to Table 1-2 in Chapter 1, Using the CLI and GUI to Manage a GSS Network.
Refer to either the Cisco Global Site Selector GUI-based Global Server Load-Balancing Configuration Guide or the Cisco Global Site Selector CLI-based Global Server Load-Balancing Configuration Guide for detailed procedures on how to configure your GSS devices to perform global server load balancing.
Use the following procedures to configure your GSS devices and resources from the primary GSSM for global server load-balancing:
1. Create regions, locations, and owners—Optional. Use these groupings to organize your GSS network resources by customer account, physical location, owner, or other organizing principle. Refer to Chapter 2, Configuring Resources, for details.
2. Create one or more source address lists—Optional. Use these lists of IP addresses to identify the name servers (D-proxy) that forward requests for the specified domains. The default source address list is Anywhere to match any incoming DNS request to the domains. Refer to Chapter 3, Configuring Source Address Lists, for details.
3. Create one or more domain lists—Establish lists of Internet domains, possibly using wildcards, that are managed by the GSS and queried by users. Refer to Chapter 4, Configuring Domain Lists, for details.
4. Modify the default global keepalive settings or create any shared keepalives—Optional. These are GSS network resources that are regularly polled to monitor the online status of one or more GSS resources linked to the keepalive. Shared keepalives are required for any answer that uses the KAL-AP keepalive type. Refer to Chapter 5, Configuring KeepAlives, for details.
5. Create one or more answers and answer groups—Answers are resources that match requests to domains. Answer groups are collections of resources that balance requests for content. Refer to Chapter 6, Configuring Answers and Answer Groups, for details.
6. Build the DNS rules that will control global server load balancing on your GSS network. Refer to Chapter 7, Building and Modifying DNS Rules for details.
7. If you plan to use DNS sticky for your global server load-balancing application, configure local and global DNS sticky for GSS devices in your network —Stickiness enables the GSS to remember the DNS response returned for a client D-proxy and to later return that answer when the client makes the same request. Refer to Chapter 8, Configuring DNS Sticky, for details.
8. If you plan to use network proximity for your global server load-balancing application, configure proximity for GSS devices in your network—Proximity determines the best (most proximate) resource for handling global load-balancing requests. Refer to Chapter 9, Configuring Network Proximity, for details.
