Skip to content

Cluster Management

Changing Server Modes

Administrator can manually change the server modes from HyWorks Controller section.

The feature is useful when administrator wants to do some maintenance activities (e.g. Upgrade) on one server and willing to keep services down for some time. In such cases administrator can change the modes of servers using following steps:

  1. Access HyWorks Controller Management Console of one of the HyWorks Controller

  2. Log in with admin credentials

  3. Go to Host Management > Server > HyWorks Controller

  4. Select Controller whose entry has to be modified, click Change Mode

  5. Configure appropriate modes for both the servers and click Save

Removing HyWorks Controller from a Cluster

When both the Controllers are reachable

It is highly recommended to remove HyWorks Controllers from cluster when both servers are reachable for maintaining the environment on Primary server. Follow the below steps to remove HyWorks Controller from cluster when both controllers are reachable.

  1. Access HyWorks Controller Management Console of any of the HyWorks Controller (recommended Primary Controller)

  2. Go to Host Management > Server > HyWorks Controller

  3. HyWorks Controller section will list both the servers with displaying Delete button against the second HyWorks Controller

  4. Click Delete and confirm. Selected controller will be removed from the cluster and both the controllers will start functioning independently as Primary server.

    1. Second controller will have exactly same data as first controller and this can create conflict in the environment. It is not advisable to have two controllers in same environment running independently and thus the second server should be kept down.

    2. No data synchronization will happen once controllers are out of cluster

    3. Devices already registered with controller, will communicate with last accessed primary server and in the next communication with server, update their controller entries, so that next time they will not go to secondary server.

    4. First HyWorks Controller which was used to activate the license will continue to have the same license as before

    5. Second HyWorks Controller on which cluster license was activated will go into grace period.

When one HyWorks Controller is down

Though it's not recommended to remove HyWorks Controller from cluster when it's not reachable, but still this can be done using below steps:

  1. Access HyWorks Controller Management Console of HyWorks Controller currently reachable

  2. Go to Host Management > Server > HyWorks Controller

  3. HyWorks Controller section will list both the servers with displaying Delete button against the second HyWorks Controller (currently not reachable)

  4. Select secondary server and click Delete and confirm.

  5. It will check the HyWorks Controller unavailability and will display error in Confirm Action dialog

  6. Click Force Delete to continue. Server2 will get deleted from Server1 and Server1 will start functioning as an independent primary server

As Server2 is down and not having any information of removal from cluster, so when it will come up again, it will continue to work as secondary. To avoid any further invalid synchronization of data between two servers, the entry of first server must be deleted from this (server2).

  1. Access Management Console of second HyWorks Controller

  2. Go to Host Management > Server > HyWorks Controller

  3. Click Delete button displayed against the Server1 which it considers to be primary server and confirm

Server1 will get deleted from Server2 and now Server2 will also start functioning as independent primary server. License of second server will get reset to grace period, as it was using the cluster license.

Advance Configurations

Advance configurations available on HyWorks Controller Management Console - Host Management > Server > Advance Config

  • Clustering: All High Availability related configurations are available in Clustering Group.