This article describes, how to configure High Availability for Versa Director.
Please Note: In case of any Firewall between 2 Versa Director nodes following ports need to opened
22, 4566, 4570, 5432
Versa Director supports Active-Standby High Availability between its nodes.
Prerequisite
- Two nodes of Versa Director- Versa Director1 ( vdirector1) and Versa Director2 (vdirector2) are up and running.
- Both the Versa Directors are running on the same software version with same package id as shown below for an example.
Configuration
- Login to the Versa Director1 GUI using <VD IP> as shown below
- Navigate to Administration > System > High Availability, click on the edit button and enter the Active IP Address, Standby IP Address and Designated Active IP Address, then click OK as shown in the screenshot.
- Check in the task bar the auto configuration of HA.
- Once successful, the HA will be enabled and can be verified via below screen:
- Also , try to login to standby Versa Director URL and verify that the HA is enabled. The standby Versa Director will throw the message “ This instance of Versa Director is running in a passive mode. Login to this instance is not allowed.”
- Go to the CLI of Active Versa Director node and check the HA status as shown below
- Go to the CLI of standby Versa Director node and check the HA status as shown below
- In order to perform the fail over operation – to change standby Versa Director to become active Versa Director, execute the below command in the Active Versa Director:
- Verify that the vdirector1 (Versa Director 1) has now become standby and vdiector2 (versa Director 2) has become active Node as shown below:
- For disabling the HA, run the below command from the Active Versa Director cli.
- For re-enabling the HA, run the below command from the Versa Director cli
- Verify that the HA is enabled using the below commands