This feature is not intended to provide high availability. Administrators can use third- party global load balancers such as F5, Cisco, and RadWare.
Health checks from external load balancers is allowed on appliances, which allows the load balancer to know which services are running on the appliance so that traffic can be failed over to another system in the event of maintenance or failure.
There is no centralized management capability for synchronizing the node configuration across the cluster. To keep your settings synchronized across the cluster, you must make the configuration changes on one node, export the configuration, and then import the configuration to the other nodes in the cluster.
You may also use Replication option to keep the settings synchronized on all nodes behind load balancer.
Important configurations to remember while setting up SMA appliances behind load balancer:
You can configure the E-Class SRA appliance to use either a single-homed or dual- homed configuration.
Configure the SSL certificate to contain the load balancer' s virtual IP address or host name (not the host name or address for the individual appliance) Set the default external gateway on the appliance(s) to the IP address of the load balancer or switch connected to load balancer
To check the appliance status, we may need to create health check monitors for the following on external load balancer:-
Workplace service which runs on the external interface of the appliance using https port 443
AMC Service which runs on the internal Interface of the appliance using port 8443.
Any SNMP based monitors (using Aventail MIBs) in order to perform Health check monitoring.