System Ha On-Failure - Fortinet FortiMail 3.0 MR4 Cli Reference Manual

system ha on-failure

system ha on-failure
Use this command to control the behavior of a FortiMail unit in an active-passive HA group when
remote service monitoring detects a failure. In most cases you should set On Failure to wait for
recovery and then assume slave role. In this mode when service monitoring detects a failure the
FortiMail unit effective operating mode changes to FAILED. In FAILED mode the FortiMail unit and can
automatically recover, switch to the SLAVE effective operating mode and synchronize MTA spool
directories with the other FortiMail unit which should be operating in the MASTER effective operating
mode.
Syntax
set system ha on-failure {off | restore | slave}
Keywords/Variables
off
restore
slave
Example
Enter the following command to configure a FortiMail unit to switch to FAILED effective operating
mode and when restored, to change the effective operating mode to SLAVE.
set system ha on-failure slave
History
FortiMail v3.0 MR2
Related topics
• set system ha config
• set system ha {cpeer | interface | peer |
secondary-interface | secondary-peer}
• set system ha data
• set system ha datadir
• set system ha lservice
• set system ha mode
324
Description
After a failure the FortiMail unit effective operating mode changes to
OFF. The FortiMail unit will not process mail or join the HA group until
you manually change the FortiMail unit effective operating mode to
MASTER (primary) or SLAVE (backup).
Similar to slave the FortiMail unit effective operating mode changes to
FAILED when remote service monitoring detects a failure. However, in
this case on recovery the failed FortiMail unit effective operating mode
switches back to its configured operating mode. This behavior may be
useful in some scenarios but may cause problems in others.
The FortiMail unit effective operating mode changes to FAILED when
remote service or local network interface service monitoring detects a
failure. In FAILED mode the FortiMail unit uses remote service
monitoring to attempt to connect to the other FortiMail unit in the HA
group (which should be operating as the primary unit with effective
operating mode of MASTER). If you fix the problem that caused the
failure the failed FortiMail unit recovers by changing its effective
operating mode to SLAVE. The failed FortiMail unit then synchronizes
the content of its MTA spool directories to the FortiMail unit operating as
the primary unit. The primary unit can then deliver this email.
New.
FortiMail™ Secure Messaging Platform Version 3.0 MR4 CLI Reference
• set system ha monitor
• set system ha passwd
• set system ha remote-as-heartbeat
• set system ha {restart | restore | resync}
• set system ha rservice
• set system ha takeover
set
Default
06-30004-0420-20080814