NetScaler VPX

High availability across different AWS availability zones

August 28, 2024

Contributed by:

You can configure two NetScaler VPX instances on two different subnets or two different AWS availability zones, as a high availability active-passive pair in Independent Network Configuration (INC) mode. If for any reason, the primary node is unable to accept connections, the secondary node takes over.

For more information about high availability, see High availability. For more information about INC, see Configuring high availability nodes in different subnets.

Points to note

Read the following documents before you start your deployment:
The VPX high availability pair can either reside in the same availability zone in a different subnet or in two different AWS availability zones.
Citrix recommends that you use different subnets for management (NSIP), client traffic (VIP), and back-end server (SNIP).
High availability must be set in Independent Network Configuration (INC) mode for a failover to work.
The two instances must have port 3003 open for UDP traffic as that is used for heartbeats.
The management subnets of both the nodes must have access to internet or to AWS API server through internal NAT so that the rest APIs are functional.
IAM role must have E2 permission for the public IP or elastic IP (EIP) migration and EC2 Route Table permissions for the private IP migration.

You can deploy high availability across AWS availability zones in the following ways:

Additional References

For more information on NetScaler Application Delivery Management (ADM) for AWS, see Install the NetScaler ADM agent on AWS.

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.

Was this helpful

High availability across different AWS availability zones

August 28, 2024

Contributed by:

August 28, 2024

Contributed by:

High availability across different AWS availability zones

Points to note

Additional References

In this article