Before configuring load balancers, perform these prerequisites.
- NSX - Before you can start a high-availability implementation of VMware Aria Automation or VMware Aria Automation Orchestrator using NSX as a load balancer, ensure that your NSX topology is configured and that your version of NSX is supported. This document covers the load balancing aspect of an NSX configuration and assumes that NSX is configured and validated to work properly on the target environment and networks. To verify that your version is supported, see the VMware Product Interoperability Matrix.
- F5 BIG-IP LTM - Before you can start a high-availability implementation of VMware Aria Automation or VMware Aria Automation Orchestrator using F5 LTM load balancer, ensure that the load balancer is installed and licensed and that the DNS server configuration is complete.
- NetScaler - Before you can start a high-availability implementation of VMware Aria Automation or VMware Aria Automation Orchestrator using the NetScaler load balancer, ensure that NetScaler is installed and has at least a Standard Edition license.
- Certificates - Request Certificate Authority (CA) signed certificate containing the load-balancer fully qualified domain name and the hostnames of the cluster nodes in the SubjectAltNames section. This configuration enables the load balancer to serve traffic without SSLerrors.
- Identity provider - The identity provider is Workspace ONE Access, which is deployed external to the VMware Aria Automation appliances and cluster.
For more information on installation and configuration, see VMware Aria Automation documentation on docs.vmware.com.
If necessary, an external VMware Aria Automation Orchestrator cluster can be configured to work with the VMware Aria Automation system. This can be done after the VMware Aria Automation system is up and running. However, a VMware Aria Automation Highly Available setup already includes an embedded VMware Aria Automation Orchestrator cluster.
