Fortinet Technologies Inc. Page 70 FortiVoice Enterprise Phone System 4.0.0 Administration Guide
The following critical event was detected
The system is rebooting (or reloading)!
• S2 will hold off checking the services and heartbeat with P1. Note that S2 will only hold off
for about 5 minutes. In case P1 never boots up, S2 will take over the master role.
• S2 will send out an alert email, indicating that S2 received the holdoff command from P1.
This is the HA machine at 172.16.5.11.
The following event has occurred
‘peer rebooting (or reloading)’
The state changed from ‘SLAVE’ to ‘HOLD_OFF’
After P1 is up again:
• P1 will send another command to S2 and ask S2 to change its state from holdoff to slave
and resume monitoring P1’s services and heartbeat.
• S2 will send out an alert email, indicating that S2 received instruction commands from P1.
This is the HA machine at 172.16.5.11.
The following event has occurred
‘peer command appeared’
The state changed from ‘HOLD_OFF’ to ‘SLAVE’
• S2 logs the event in the HA logs.
Failover scenario 3: System reboot or reload of the secondary unit
If you need to reboot or reload (not shut down) S2 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 Monitor > System Status > Status on the GUI, the behavior
of P1 and S2 is as follows:
• P1 will send out an alert email similar to the following, informing the administrator of the
heartbeat loss with S2.
This is the HA machine at 172.16.5.10.
The following event has occurred
‘ha: SLAVE heartbeat disappeared’
• S2 will send out an alert email similar to the following:
This is the HA machine at 172.16.5.11.
The following critical event was detected
The system is rebooting (or reloading)!
• P1 will also log this event in the HA logs.
Failover scenario 4: System shutdown of the secondary unit
If you shut down S2:
• No alert email is sent out from either P1 or S2.
• P1 will log this event in the HA logs.
Failover scenario 5: Primary heartbeat link fails
If the primary heartbeat link fails, such as when the cable becomes accidentally disconnected,
and if you have not configured a secondary heartbeat link, the FortiVoice units in the HA group
cannot verify that other units are operating and assume that the other has failed. As a result, the
To Next Page
Loading...
