To enable the HA activity logging before configuring the HA mode and group:
- Go to Log & Report > Log Setting > Local
- Under Logging Policy Configuration, expand System and enable HA.
- Click Apply.
To enable and configure HA:
- Go to System > High Availability > Configuration.
- Under HA Configuration, if the FortiVoice unit is the primary unit, set Mode of operation to Master. If the FortiVoice unit is the secondary unit, set Mode of operation to Slave.
- Set On failure to the appropriate action, determining what happens to the unit in the event of a failover.
- Enter a Shared password. This password must be the same for both the primary and secondary units.
- Under Advanced Options, set an HA base port value (20000 by default). This will be used for the heartbeat signal, and synchronization control, including data and configuration synchronization.
- Set the Heartbeat lost threshold to the duration of time in seconds that the FortiVoice unit can remain unresponsive before it triggers a failover. For example, if the heartbeat checks for availability once per second, and the primary unit is experiencing heavier traffic than usual, a premature failover may occur. In this case, a higher threshold of three seconds or more can allow the secondary unit enough time to confirm unresponsiveness. Keep in mind that if the threshold time is instead too long, the primary unit could fail and a delay in detecting the failure could mean that a call is delayed or lost.
- Enable Remote services as heartbeat to use remote service monitoring as a secondary HA heartbeat. If enabled, and both the primary and secondary heartbeat links fail or become disconnected, the remote service monitoring can still detect whether the primary unit is available, avoiding a false-positive result.
- Under Interface, double-click each port you want to monitor in case of failover and click Enable port monitor.
- Click Apply.
For more information on service monitor options, see Configuring service-based failover.