Fortinet Technologies Inc. Page 71 FortiVoice Enterprise Phone System 4.0.0 Administration Guide
secondary unit (S2) changes to operating as a primary unit, and both FortiVoice units are acting
as primary units.
Two primary units connected to the same network may cause address conflicts on your
network. Additionally, because the heartbeat link is interrupted, the FortiVoice units in the HA
group cannot synchronize configuration changes or voice data changes.
Even after reconnecting the heartbeat link, both units will continue operating as primary units.
To return the HA group to normal operation, you must connect to the web-based manager of S2
to restore its effective HA operating mode to slave (secondary unit).
1. The FortiVoice HA group is operating normally.
2. The heartbeat link Ethernet cable is accidently disconnected.
3. S2’s HA heartbeat test detects that the primary unit has failed.
How soon this happens depends on the HA daemon configuration of S2.
4. The effective HA operating mode of S2 changes to master.
5. S2 sends an alert email similar to the following, indicating that S2 has determined that P1
has failed and that S2 is switching its effective HA operating mode to master.
This is the HA machine at 172.16.5.11.
The following event has occurred
‘MASTER heartbeat disappeared’
The state changed from ‘SLAVE’ to ‘MASTER’
6. S2 records event log messages (among others) indicating that S2 has determined that P1
has failed and that S2 is switching its effective HA operating mode to master.
Recovering from a heartbeat link failure
Because the hardware failure is not permanent (that is, the failure of the heartbeat link was
caused by a disconnected cable, not a failed port on one of the FortiVoice units), you may want
to return both FortiVoice units to operating in their configured modes when rejoining the failed
primary unit to the HA group.
To return to normal operation after the heartbeat link fails
1. Reconnect the primary heartbeat interface by reconnecting the heartbeat link Ethernet
cable.
Even though the effective HA operating mode of S2 is master, S2 continues to attempt to
find the other primary unit. When the heartbeat link is reconnected, S2 finds P1 and
determines that P1 is also operating as a primary unit. So S2 sends a heartbeat signal to
notify P1 to stop operating as a primary unit. The effective HA operating mode of P1
changes to off.
2. P1 sends an alert email similar to the following, indicating that P1 has stopped operating as
the primary unit.
This is the HA machine at 172.16.5.10
The following event has occurred
'SLAVE asks us to switch roles (user requested takeover)'
The state changed from 'MASTER' to 'OFF'
3. P1 records event log messages (among others) indicating that P1 is switching to off mode.
The configured HA mode of operation of P1 is master and the effective HA operating mode
of P1 is off.
The configured HA mode of operation of S2 is slave and the effective HA operating mode of
S2 is master.
4. Connect to the web-based manager of P1, go to System > High Availability > Status.
To Next Page
Loading...
