ADC

Use case: Deployment of domain name based autoscale service group

August 1, 2023

Contributed by:

Tip

For information about the GSLB service groups, see Configuring a GSLB Service Group

Deployment scenario

Two datacenters are deployed in two AWS regions, one in Sydney and one in North Virginia. Another datacenter is deployed in Azure. An AWS ELB in each AWS region is used to load balance the application servers. ALB is used for Azure to load balancing the application server. The NetScaler appliances are configured for GSLB for the ELBs and ALB using GSLB domain name based autoscale service group.

Important

You must configure the required security groups in AWS and attach it to the GSLB instance. Port 53 must be allowed in the security group inbound and outbound rules. Also, ports (3009 or 3011 depending on secure MEP configuration) for MEP communication must be open. For application monitoring, the corresponding ports must be allowed in the security group outbound rules.

The configuration steps for the above deployment scenario and the corresponding CLI commands are as follows:

Create datacenters (represented by GSLB sites).

add gslb site aws-sydney 192.0.2.2

add gslb site aws-nvirginia 198.51.100.111

add gslb site alb-southindia 203.0.113.6
Add a name server with the DNS gateway IP address where the GSLB node is added. This must be done in all datacenters.

add dns nameServer 8.8.8.8
Add servers for ELB and ALB.

add server aws-sydney_server lb-sydney-1052691850.ap-southeast-2.elb.amazonaws.com

add server aws-nvirginia_server LB-nvirginia-860559595.us-east-1.elb.amazonaws.com

add server alb-southindia_server alb.southindia.cloudapp.azure.com
Add GSLB autoscale service groups for each ELB and ALB and bind each server to the respective service group.

add gslb serviceGroup aws-nvirginia_sg HTTP -autoScale DNS -siteName aws-nvirginia

add gslb serviceGroup aws-sydney_sg HTTP -autoScale DNS -siteName aws-sydney

add gslb serviceGroup alb-southindia_sg HTTP -autoScale DNS -siteName alb-southindia

bind gslb serviceGroup aws-nvirginia_sg aws-nvirginia_server 80

bind gslb serviceGroup aws-sydney_sg aws-sydney_server 80

bind gslb serviceGroup alb-southindia_sg alb-southindia_server 80
Add a GSLB virtual server and bind the application domain and the service groups to this virtual server.

add gslb vserver gv1 HTTP

bind gslb vserver gv1 -serviceGroupName aws-nvirginia_sg

bind gslb vserver gv1 -serviceGroupName aws-sydney_sg

bind gslb vserver gv1 -serviceGroupName alb-southindia_sg

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Use case: Deployment of domain name based autoscale service group

August 1, 2023

Contributed by:

August 1, 2023

Contributed by:

Use case: Deployment of domain name based autoscale service group

Deployment scenario

In this article