About The Heartbeat And Synchronization - Fortinet fortivoice Administrator's Manual

About the heartbeat and synchronization

Heartbeat and synchronization traffic consists of TCP packets transmitted between the
FortiVoice units in the HA group through the primary and secondary heartbeat interfaces.
Service monitoring traffic can also, for short periods, be used as a heartbeat. For details, see
"Remote services as heartbeat" on page
Heartbeat and synchronization traffic has three primary functions:
• to monitor the responsiveness of the HA group members
• to synchronize configuration changes from the primary unit to the secondary units
For exceptions to synchronized configuration items, see
synchronized" on page
• to synchronize system and user data from the primary unit to the secondary unit
Call data consists of the FortiVoice call detailed records, recorded calls, voicemail, call
directories, fax, and voice prompts.
When the primary unit's configuration changes, it immediately synchronizes the change to the
secondary unit through the primary heartbeat interface. If this fails, or if you have inadvertently
de-synchronized the secondary unit's configuration, you can manually initiate synchronization.
For details, see
the CLI command diagnose system ha sync on either the primary unit or the secondary
unit to manually synchronize the configuration. For details, see the
During normal operation, the secondary unit expects to constantly receive heartbeat traffic from
the primary unit. Loss of the heartbeat signal interrupts the HA group and generally triggers a
failover. For details, see
Exceptions include system restarts and the execute reload CLI command. In case of a
system reboot or reload of the primary unit, the primary unit signals the secondary unit to wait
for the primary unit to complete the restart or reload. For details, see
System reboot or reload of the primary unit" on page
Periodically, the secondary unit checks with the primary unit to see if there are any configuration
changes on the primary unit. If there are configuration changes, the secondary unit will pull the
configuration changes from the primary unit, generate a new configuration, and reload the new
configuration. In this case, both the primary and secondary units can be configured to send
alert email. For details, see
on page 70
Configuration settings that are not synchronized
All configuration settings on the primary unit are synchronized to the secondary unit, except the
following:
Table 6: HA settings not synchronized
Host name
Static route
Fortinet Technologies Inc.
55.
"click HERE to start a configuration/data sync" on page
"Failover scenario 1: Temporary failure of the primary unit" on page
"Failover scenario 3: System reboot or reload of the secondary unit"
and "Configuring alert email" on page
The host name distinguishes members of the cluster. For details, see
"Host name" on page
Static routes are not synchronized because the HA units may be in
different networks (see
Page 55
63.
"Configuration settings that are not
69.
254.
349.
"Configuring static routes" on page
FortiVoice Enterprise Phone System 4.0.0 Administration Guide
59. You can also use
FortiVoice CLI Reference.
"Failover scenario 2:
45).
68.