This section covers the following configuration steps required to setup GSLB sites.

  • Setting up Individual Controller Clusters

  • Configuring a Local DNS virtual service on All Active Sites that host DNS

  • Configuring Local Application Virtual services

  • Designating the GSLB Leader and Adding Site Configuration

  • Configuring Additional Domain

Setting up Individual Controller Clusters

Create two or more Controller clusters (depending on the number of DCs/locations), and run through the initial system configuration steps. Each of the Controller clusters could be a 1-node (test & development) or a 3-node (production) cluster. In the following example, Santa Clara (10.10.25.10) and Boston (10.160.0.20) are the two NSX Advanced Load Balancer Controller running on respective locations/DCs/sites.

Configuring a Local DNS Virtual Service on All Active Sites that host DNS

Configure a local DNS virtual service on all the clusters where the DNS service needs to be hosted, bound to the local g-dns SE group.

For each Controller cluster, configure a SE group to host the DNS virtual service (named g-dns in this example). To configure the SE group navigate to Infrastructure > Cloud > Service Engine Group.

Note:
  • It is assumed that the Controller is up and running and cloud configuration is done.

  • The virtual service and SE group names need not be identical across all GSLB sites.

In the following screenshot, the value for virtual services per Service Engine is set as 1 (the default value is 10) as a recommended best practice.



In Santa Clara (10.10.25.10):

  1. Configure a DNS virtual service on all the clusters where the DNS service needs to be hosted and bound to the g-dns SE group:

  2. Create a virtual service in the Advanced Setup.



  3. Select an application profile as System-DNS. Accept the default for the TCP/UDP Profile field (System-UDP-Per-Pkt).



  4. Click Next to proceed to Step 2 Policies.

  5. Click Switch to Advanced in the Service Port section, add a new port 53, override TCP/UDP profile for this one and select System-TCP-Proxy. This is optional and required if you need DNS over TCP. No pool is required if you are using NSX Advanced Load Balancer DNS for GSLB only and NSX Advanced Load Balancer DNS is not the primary DNS server as mentioned here.



  6. Configure Network Security rules, if required.

  7. Click Next to proceed to Step 3 Analytics.

  8. Accept the defaults for analytics or change them as shown in the screenshot below:



  9. Click Next to proceed to Step 4 Advanced.

  10. Under Other Settings, select the SE Group that was created to host this DNS virtual service.



  11. Optionally create static DNS records.



  12. Click Save to complete the process of defining the DNS virtual service for the Santa Clara site.

Similarly, create a DNS virtual service on other site/DC i.e. Boston(10.160.0.20 as per our example). DNS virtual service is named as colo-dns with VIP = 10.160.110.100.

Configuring Local Application Virtual services

Create application virtual services. For example, create an HTTP virtual service vs-1 in Controller cluster 1, and virtual service vs-2 in Controller cluster 2.

Refer to Configuring Virtual Services for more details:

On 10.10.25.10 (Santa Clara):

On 10.160.0.20 (Boston):