How to Configure GSLB on NetScaler Gateway

GSLB Persistence

In NetScaler, we can configure GSLB persistence based on source IP or HTTP cookies. In source IP persistence, based on IP of user device, persistence is maintained. NetScaler maintains a persistence table for each user device connected and sends the user to appropriate data centre.

HTTP cookie-based GSLB persistence is based on cookie in HTTP headers. Gateway virtual server checks the cookie in the HTTP header and accepts, proxies or redirects the request. Cookie-based persistence is recommended for Gateway because all requests are HTTP based and it is most reliable persistence method. This persistence can be configured as connection proxy or HTTP redirect. In connection proxy, when a request with HTTP cookie lands on another datacenter Gateway virtual server, the vserver tunnels the request to the original datacenter, gets the response and sends back to the client.

To configure HTTP redirect, sitePrefix needs to be added. It is the site’s prefix string concatenated to GSLB virtual server domain name as a prefix. This is stored internally for each bound service-domain pair. When a Gateway virtual server gets a request with cookie of other Gateway virtual server then the first Gateway virtual server sends a redirect response with the domain name i.e. the stored concatenated site prefix and domain name. Client on receiving the redirect connects to the concatenated domain name it received. This way, the persistence is maintained.

Note: Configuring persistence is optional and is not covered in this article.

Configuration Steps

Prerequisite: Gateway virtual server on all the sites should already be configured. To know how to configure gateway virtual server please see – http://support.citrix.com/article/CTX127044.

For configuring GSLB, it is required to do same configuration on all the sites participating in GSLB. Here the configuration from only one site is shown.

Step 1: Add GSLB sites

Add a local site and one or more remote site(s).

CLI:

add gslb site site_1 <site SNIP>

GUI:

Go to Traffic Management > GSLB > Sites.

User-added image

Step 2: Add GSLB services

Add a GSLB service for the local Gateway virtual server and one or more GSLB service(s) for remote site(s).

CLI:

> add gslb service <GSLB service name> <gateway vserver IP> SSL 443 -siteName <GSLB site name to which the gateway vserver belong>

GUI:

Go to Traffic Management > GSLB > Services.

User-added image

Step 3: Add GSLB virtual server

Add a GSLB vertical server (in each site) which will take the GSLB DNS request and select the appropriate site for the user.

CLI:

> add gslb vserver <GSLB virtual server name> SSL

> bind gslb vserver <GSLB virtual server name> -serviceName <GSLB service name>

> bind gslb vserver <GSLB virtual server name> domainName <GSLB vserver domain name>

GUI:

Go to Traffic Management > GSLB > Virtual Servers

User-added image

User-added image

User-added image

User-added image

To get more details on how GSLB works, please see http://docs.citrix.com/en-us/netscaler/11/traffic-management/gslb/how-gslb-works.html.

For more information on HTTP cookie based persistence, please see http://docs.citrix.com/en-us/netscaler/11/traffic-management/gslb/configure-persist-connections.html.

Related:

Leave a Reply