Fortinet Technologies Inc. Page 72 FortiVoice Enterprise Phone System 4.0.0 Administration Guide
5. Check for synchronization messages.
Do not proceed to the next step until P1 has synchronized with S2.
6. Connect to the web-based manager of S2, go to System > High Availability > Status and
select click HERE to restore configured operating mode.
The HA group should return to normal operation. P1 records the event log message (among
others) indicating that S2 asked P1 to return to operating as the primary unit.
P1 and S2 synchronize again. P1 processes phone calls normally.
Failover scenario 6: Network connection between primary and secondary units
fails (remote service monitoring detects a failure)
Depending on your network configuration, the network connection between the primary and
secondary units can fail for a number of reasons. In the network configuration shown in
Figure 23 on page 68, the connection between port1 of primary unit (P1) and port1 of the
secondary unit (S2) can fail if a network cable is disconnected or if the switch between P1 and
S2 fails.
A more complex network configuration could include a number of network devices between the
primary and secondary unit’s non-heartbeat network interfaces. In any configuration, remote
service monitoring can only detect a communication failure. Remote service monitoring cannot
determine where the failure occurred or the reason for the failure.
In this scenario, remote service monitoring has been configured to make sure that S2 can
connect to P1. The On failure setting located in the HA main configuration section is wait for
recovery then restore slave role. For information on the On failure setting, see “On failure” on
page 62. For information about remote service monitoring, see “Configuring service-based
failover” on page 66.
The failure occurs when power to the switch that connects the P1 and S2 port1 interfaces is
disconnected. Remote service monitoring detects the failure of the network connection
between the primary and secondary units. Because of the On failure setting, P1 changes its
effective HA operating mode to failed.
When the failure is corrected, P1 detects the correction because while operating in failed mode
P1 has been attempting to connect to S2 using the port1 interface. When P1 can connect to S2,
the effective HA operating mode of P1 changes to slave and the voice data on P1 will be
synchronized to S2. S2 can now deliver the calls. The HA group continues to operate in this
manner until an administrator resets the effective HA modes of operation of the FortiVoice units.
1. The FortiVoice HA group is operating normally.
2. The power cable for the switch between P1 and S2 is accidently disconnected.
3. S2’s remote service monitoring cannot connect to the primary unit.
How soon this happens depends on the remote service monitoring configuration of S2.
4. Through the HA heartbeat link, S2 signals P1 to stop operating as the primary unit.
5. The effective HA operating mode of P1 changes to failed.
6. The effective HA operating mode of S2 changes to master.
7. 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 remote service disappeared’
The state changed from ‘SLAVE’ to ‘MASTER’
8. S2 logs the event (among others) indicating that S2 has determined that P1 has failed and
that S2 is switching its effective HA operating mode to master.
To Next Page
Loading...
