Skip to content

Configuration of Virtual IP in Two-node Active-Passive Cluster

Using HyWorks Controller active-passive two-node deployments, the administrator can configure a virtual IP on the controller cluster and use that virtual IP to connect from endpoints. This feature requires the virtual IP to be managed by the HyWorks Controller and to be attached only to those servers running with the primary HyWorks Controller role. An important scenario is when the endpoints are operating in write-protected mode.

Prerequisites

To enable the virtual IP feature:

  1. Deployment type: Two-node active-passive deployment.

  2. Network adapter on HyWorks Controller servers.

    1. Must not have any spaces or special characters.

    2. Both HyWorks Controller servers must have network adapters with the same name.

  3. A Static IP address should be configured on both HyWorks Controller Servers.

  4. Recommended Release: v3.4-SP1-HF2 (Some important bug-fixes are included in this hotfix)

How to configure Virtual IP

  1. Open the browser and navigate to the HyWorks Management Console of the primary HyWorks Controller.

  2. Navigate to HyWorks Settings > General > Advance Settings.

  3. Apply group filter Clustering to and search with string virtual to view relevant configurations.

  4. Locate the following configurations and update as specified below:

    1. Virtual IP address: Virtual IP address to be used by controller cluster. This should not be used anywhere in the network and should be from the same subnet in which HyWorks Controller servers are running. Providing an invalid IP address may cause session failures.

    2. Set the NIC card name the same as used on HyWorks Controllers e.g. Ethernet0.

    3. Set Virtual subnet correctly and as being used on HyWorks controller servers.

    4. Set Enable virtual IP configuration as True.

  5. Save the configurations and click on the Update button to push the saved configurations.

  6. Once updated, the primary HyWorks Controller will configure virtual IP on its network adapter first.

  7. Provide this virtual IP to end-users to connect to the controller.

  8. Any subsequent switching of HyWorks controllers in the cluster will also move the virtual IP to the new primary controller.

Troubleshooting and Known Limitations

  1. On controller service restart, controller servers may update their IP address with the virtual one and this could cause some problems. This can be avoided by following this article.

    1. Here the actual controller IP should be configured in the registry, so that the controller always uses it for binding and updating.

  2. The following scripts must be present on HyWorks Controllers:

    1. Primary HyWorks Controller: C:\Program Files (x86)\Accops\HyWorks\Service\Script\OnPrimary.bat

    2. Secondary HyWorks Controller: C:\Program Files (x86)\Accops\HyWorks\Service\Script\OnNonPrimary.bat

  3. The following logs are generated during virtual IP configuration, and switching and can be used for troubleshooting. In the absence of these logs, the configuration can be assumed to be faulty and should need to be troubleshoot.

    1. Info - Updated advance setting 'Enable virtual IP configuration', old value: 'false' new value: 'true' > Suggesting administrator has changed the virtual IP configurations in Advance settings.

    2. Script creation Logs:

      1. Warning - Virtual IP script C:\Program Files (x86)\Accops\HyWorks\Service\Script\OnPrimary.bat not found. Creating the file. > Suggesting the needed script file is not available and will be created.

        1. Info - VIP script file created C:\Program Files (x86)\Accops\HyWorks\Service\Script\OnPrimary.bat > Logs will be generated once the script file is created.

    3. Info - Virtual IP verified successfully. > Suggesting virtual IP configuration is saved successfully. Details of these logs will suggest the virtual IP address and network adapter details.

    4. Warning - Virtual IP script C:\Program Files (x86)\Accops\HyWorks\Service\Script\OnNonPrimary.bat not found. Creating the file. > This will be created on secondary on the first switching if does not exist.

      1. Info - VIP script file created C:\Program Files (x86)\Accops\HyWorks\Service\Script\OnNonPrimary.bat. > Logs will be generated once the script file is created

    5. Info - The attached virtual IP was removed successfully. > Suggesting virtual IP is removed from the server which has now become secondary.

  4. If the HyWorks Controller service process is killed manually or automatically then the virtual IP switching will not work though HyWorks controllers have switched.

  5. On disabling virtual IP configuration, the controller does not remove the virtual IP and hence, this has to be done manually. (#29789)

  6. The virtual IP configuration is not intended for the HyLabs environment and may cause functional failures. As RMS service tries to connect to HyWorks Controller virtual IP and fails. (#9892)