Configuring system settings : Using high availability (HA) : Configuring the HA mode and group : Configuring the advanced options
Configuring the advanced options
Go to System > High Availability > Configuration to configure the advanced options. For config-only groups, just the HA base port option appears.
 
Table 26: HA advanced options
GUI item
Description
HA base port
Enter the first of four TCP port numbers that will be used for:
the heartbeat signal
synchronization control
data synchronization
configuration synchronization
Note: For active-passive groups, in addition to configuring the heartbeat, you can configure service monitoring. For details, see “Configuring service-based failover”.
Note: In addition to automatic immediate and periodic configuration synchronization, you can also manually initiate synchronization. For details, see “click HERE to start a configuration/data sync”.
Heartbeat lost threshold
Enter the total span of time, in seconds, for which the primary unit can be unresponsive before it triggers a failover and the secondary unit assumes the role of the primary unit.
The heartbeat will continue to check for availability once per second. To prevent premature failover when the primary unit is simply experiencing very heavy load, configure a total threshold of three (3) seconds or more to allow the secondary unit enough time to confirm unresponsiveness by sending additional heartbeat signals.
Note: If the failure detection time is too short, the secondary unit may falsely detect a failure when during periods of high load.
Caution: If the failure detection time is too long the primary unit could fail and a delay in detecting the failure could mean that email is delayed or lost. Decrease the failure detection time if email is delayed or lost because of an HA failover.
Remote services as heartbeat
Enable to use remote service monitoring as a secondary HA heartbeat. If enabled and both the primary and secondary heartbeat links fail or become disconnected, if remote service monitoring still detects that the primary unit is available, a failover will not occur.
Note: The remote service check is only applicable for temporary heartbeat link fails. If the HA process restarts due to system reboot or HA daemon reboot, physical heartbeat connections will be checked first. If the physical connections are not found, the remote service monitoring does not take effect anymore.
Note: Using remote services as heartbeat provides HA heartbeat only, not synchronization. To avoid synchronization problems, you should not use remote service monitoring as a heartbeat for extended periods. This feature is intended only as a temporary heartbeat solution that operates until you reestablish a normal primary or secondary heartbeat link.