Fortinet Technologies Inc. Page 69 FortiVoice Enterprise Phone System 4.0.0 Administration Guide
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 temporary failure of the primary unit
After P1 recovers from the hardware failure, what happens next to the HA group depends on
P1’s HA On failure settings under System > High Availability > Configuration.
Figure 24: HA On Failure settings
• switch off
P1 will not process calls or join the HA group until you manually select the effective HA
operating mode (see “click HERE to restore configured operating mode” on page 59).
• wait for recovery then restore original role
On recovery, P1’s effective HA operating mode resumes its configured master role. This also
means that S2 needs to give back the master role to P1. This behavior may be useful if the
cause of failure is temporary and rare, but may cause problems if the cause of failure is
permanent or persistent.
In the case, the S2 will send out another alert email similar to the following:
This is the HA machine at 172.16.5.11.
The following event has occurred
‘SLAVE asks us to switch roles (recovery after a restart)
The state changed from ‘MASTER’ to ‘SLAVE’
After recovery, P1 also sends out an alert email similar to the following:
This is the HA machine at 172.16.5.10.
The following critical event was detected
The system was shutdown!
• wait for recovery then restore slave role
On recovery, P1’s effective HA operating mode becomes slave, and S2 continues to assume
the master role. P1 then synchronizes with the current master unit, S2. For information on
manually restoring the FortiVoice unit to acting in its configured HA mode of operation, see
“click HERE to restore configured operating mode” on page 59.
Failover scenario 2: System reboot or reload of the primary unit
If you need to reboot or reload (not shut down) P1 for any reason, such as a firmware upgrade
or a process restart, by using the CLI commands execute reboot or execute reload, or
by clicking the Restart button under Status > Dashboard > System Command on the GUI:
• P1 will send a holdoff command to S2 so that S2 will not take over the master role during
P1’s reboot.
• P1 will also send out an alert email similar to the following:
This is the HA machine at 172.16.5.10.
To Next Page
Loading...
