| HA Pulse Retry Interval |
In High Availability deployment, the HyWorks controller checks other controller health after HA Pulse Interval (secs), it will retry after this retry interval if Pulse fails (Minimum value is 2 seconds). |
2 |
Interval |
| Enable active-active cluster |
Cluster mode will decide where the controller will sync the database or SQL server, if True: SQL server, if False: Controller. |
False |
High Availability |
| HA Pulse Interval |
In High Availability deployment, the HyWorks controller checks other controller health after HA Pulse Interval (secs) (Minimum value is 2 seconds). |
30 |
Interval |
| HA Delete Entry Monitor Control |
In High Availability mode, if one Controller is unavailable then Active Controller will create HA tombstone entries. These entries are cleaned after the HA Delete Entry Monitor Interval. It is recommended to set the value as True. |
True |
Control |
| HA Pulse Path |
In high-availability deployment, the HyWorks controller checks the health of another controller through the given URL. The IP address <######> and the port number <$$$$$> are replaced at the runtime. |
https://###### :$$$$$/PulseController.Svc |
Path |
| HA Delete Entry Threshold |
In High Availability mode, if HA tombstone entries exceed the threshold, then the entries need to be cleaned periodically. |
10000 |
- |
| HA DB Sync Control |
In High Availability deployment, the Secondary Controller syncs DB with the Primary Controller DB after the HA DB Sync Interval. It is recommended to set the value as True. |
True |
Control |
| HA DB Sync Interval |
In High Availability deployment, the Secondary Controller syncs DB with the Primary Controller DB after this interval (seconds). |
60 |
Interval |
| Virtual IP address |
Provide virtual IP address for Controller cluster. The provided IP will be shared with endpoints and shared session hosts. |
300.300.300.300 |
VIP |
| NIC Card Name |
Provide the NIC Card name on which the virtual IP will be configured, e.g. ethernet2. |
Ethernet0 |
VIP |
| HA Delete Entry Monitor Interval |
In High Availability mode, if one of the Controller is not available then Active Controller will create HA tombstone entries. These entries are cleaned after the set HA Delete Entry Monitor Interval (secs). |
86400 |
Interval |
| Client VIP for cluster |
The virtual IP address for a client when the controller is in cluster mode. |
127.0.0.1 |
High Availability |
| Check Pulse |
In High Availability deployment, the HyWorks controller checks other controller health after HA Pulse Interval (secs). Recommended to set the value as True. |
True |
Control |
| Session host VIP for cluster |
The virtual IP address for the session host server when the controller is in cluster mode. |
127.0.0.1 |
High Availability |
| Enable Virtual IP Configuration |
Enable if the Controller is in the cluster and should be configured with the virtual IP address. |
False |
VIP |
| HA Pulse Retry |
In High availability deployment, the HyWorks controller checks the other controller’s health after HA Pulse Interval (secs), this defines no of attempts made before declaring that the other controller is unreachable. |
2 |
Retry |
| Client VIP for DC-DR |
The virtual IP address for the client when a controller is in DC-DR mode (Value should empty if DC-Dr mode is not enabled). |
- |
High Availability |
| HA Notification Exchange |
In HA, the Primary server notifies cluster status in this exchange. |
edc. dvm.heartbeat-queue |
- |
| HA Notify Control |
In HA, set the Primary server to notify the cluster status. |
False |
Control |
| Virtual SubNet |
Subnet for configured virtual IP address. |
255.255.0.0 |
VIP |
| HA Keep Deleted Entries For Days |
In High Availability mode, if one of the Controller is not available then Active Controller will create HA tombstone entries. These entries are cleaned after the set days. |
2 |
- |