System ha on-failure, Syntax, Example – Fortinet FortiMail 3.0 MR4 User Manual
Page 324: History, Related topics, Set system ha on-failure
FortiMail™ Secure Messaging Platform Version 3.0 MR4 CLI Reference
324
06-30004-0420-20080814
system ha on-failure
set
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}
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
Related topics
Keywords/Variables
Description
Default
off
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).
restore
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.
slave
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.
FortiMail v3.0 MR2
New.
•
•
set system ha {cpeer | interface | peer |
secondary-interface | secondary-peer}
•
•
•
•
•
•
•
set system ha remote-as-heartbeat
•
set system ha {restart | restore | resync}
•
•