Setting up GSLB in a cluster 编辑

Note

Supported from NetScaler 10.5 Build 52.11 onwards.

To set up GSLB in a cluster you must bind the different GSLB entities to a node group. The node group must have a single member node.

Notes

• If you have configured the static proximity GSLB method, make sure that the static proximity database is present on all the cluster nodes. It happens by default if the database file is available at the default location. However, if the database file is maintained in a directory other than /var/netscaler/locdb/, you must manually sync the file to all the cluster nodes.
• The show gslb domain command is not supported in a cluster setup.

To set up GSLB in a cluster by using the CLI:

Log on to the cluster IP address and perform the following operations at the command prompt:

1. Configure the different GSLB entities. For information, see GSLB Configuration Entities.

   Note

   When creating the GSLB site, make sure that you specify the cluster IP address and public cluster IP address. The public cluster IP address is needed only when the cluster is deployed behind a NAT device. While configuring a GSLB site, you must use the cluster IP address of the same site. These parameters are required to ensure the availability of the GSLB auto-sync functionality.

   add gslb site <siteName> <siteType> <siteIPAddress> -publicIP <ip_addr> -clip <ip_addr> <publicCLIP><!--NeedCopy-->

2. Create a cluster node group.

   add cluster nodegroup <name> <name>@ [-strict ( YES | NO )] [-sticky ( YES | NO )] [-state <state>] [-priority <positive_integer>]<!--NeedCopy-->

   Note

   Enable the sticky option if you want to set up GSLB based for VPN users.

3. Bind a single cluster node to the node group.

   bind cluster nodegroup <name> -node <nodeId><!--NeedCopy-->

4. Bind the local GSLB site to the node group.

   bind cluster nodegroup <name> -gslbSite <string><!--NeedCopy-->

   Note

   Make sure that the IP address of the local GSLB site IP address is striped (available across all cluster nodes).

5. Bind the ADNS (or ADNS-TCP) service or the DNS (or DNS-TCP) load balancing virtual server to the node group.

   To bind the ADNS service:

   ```bind cluster nodegroup-service

   
   **To bind the DNS load balancing virtual server:**
   
   ```bind cluster nodegroup <name> -vServer <string><!--NeedCopy-->