Appendix

HA and vRA with SovLabs

If you’re using HA clustering with vRA, please make sure you have followed VMware’s guidelines for HA configuration with regards to VIP configuration.

The Recommendations for Persistence settings on the VIPs are especially important.

SovLabs modules persist data on vRO and if the connections are not persisted properly (i.e. VIPs have no persistence set), inconsistency between nodes can result in errors and missing data in items created by the SovLabs modules.

If using external vROs clustered in HA mode behind a load balancer, please make sure you have set Persistence on the vRO application server VIP to either SSL Session or Source Address. Do not leave as “none”.

  • If using the embedded vRO within vRA, this will not apply to your configuration.

VMware’s Documentation on Load Balancing:


Clustering/HA in Trial, POC, and Lab Environments

Factors in an environment, such as slower hardware or network latency, are contributing factors to HA cluster synchronization issues on any type of active/active cluster, not just vRA.

From a general clustering/HA best practices standpoint, it is not recommended to set up an active/active HA cluster in a an environment where latency/slow response times might be a known issue, or might not be controlled as may be the case in a shared development or lab environment.

A single-node configuration or active/passive configuration would be more desirable in an environment where latency or load could be an issue.


EMCs FEHC

Only perform the following steps if using EMC’s Federation Enterprise Hybrid Cloud 3.x and 4.x

Steps

1. SSH as user root to the vRO server (e.g. SSH via PuTTy)

2. Modify the setenv.sh file:

vi /usr/lib/vco/app-server/bin/setenv.sh

3. Press the i key on the keyboard to edit the file

4. Copy & paste the following line to the end of the JVM_OPTS variable:

-Djsse.enableSNIExtension=false

5. Press the esc key on the keyboard

6. Type in :wq and press the Enter key to save the file

7. Restart the vRO server

service vco-server restart

8. Repeat if you have more than one vRO (or vRA if using embedded vRO)