You'll learn to describe how a FortiManager cluster is built, configure the HA settings, and explain what happens at failover.
Protect the database that holds everything
FortiManager holds the only central copy of your policies, objects, revisions and templates. If its disk fails, rebuilding fifty devices' worth of structure from memory is a bad day. HA keeps a second unit with a copy.
FortiManager HA: one primary, backups keep a copy
On small screens, swipe sideways or focus the diagram and use the arrow keys.
HA protects the manager, not the FortiGates. Failover of the FortiManager roles needs a clear process, and managed devices need to be able to reach the new primary.
How the cluster works
How a FortiManager HA cluster is arranged
On small screens, swipe sideways or focus the diagram and use the arrow keys.
HA protects the database that holds every configuration. It does not remove the need for backups, and failover is not instant: plan the step that repoints the FortiGates.
One unit is the primary. FortiGates connect to it and administrators work on it.
One or more backup units receive a synchronised copy of the database.
Units in the cluster share a cluster ID and a password.
If the primary fails, a backup can be promoted and FortiGates are pointed at it.
config system ha
set mode master
set clusterid 1
set password "Example-Only-Key"
config peer
edit 1
set ip 10.0.1.32
set serial-number "FMG-VM-SERIAL-EXAMPLE"
next
end
end
FMG1. FMG2 uses the backup role and lists FMG1 as its peer. Role names differ between releases (master and slave in older ones, primary and backup in newer wording), so use ? to see yours. The password and serial number here are examples.
Release differences
Clustering options, role names and failover behaviour have changed across FortiManager releases. Treat this as the concept and follow the guide for your exact version when you build it.
What HA does not do
It does not replace backups. A bad change replicates to the backup too.
It does not keep FortiGates working. They already work without FortiManager.
It does not make a failover free: devices must be able to reach the new primary.
Check your understanding
Predict · scenario 1
An administrator deletes a policy package by mistake. Does HA protect against that?
Predict · scenario 2
FortiManager fails. What happens to traffic through the FortiGates?
Predict · scenario 3
Which two values must match across a cluster?
Further reading in Fortinet's documentation
Links open the named page in Fortinet's documentation (checked 19 October 2026). RouteLearn is an independent educational resource, not affiliated with or endorsed by Fortinet. Fortinet, FortiGate, FortiOS, FortiManager and FortiGuard are trademarks of Fortinet, Inc. Example output on this page is illustrative.
FAQ
Does FortiManager HA work like FortiGate FGCP?
No. FortiManager HA keeps a backup unit's database synchronised with the primary. It is about not losing the management database, not about forwarding traffic. Promotion of a backup is a management event.
Is failover automatic?
That depends on the release and the configuration, including whether a monitoring or arbitration mechanism is in place. Read the documentation for your version, and rehearse the process before you rely on it.
If FortiManager is down, do FortiGates stop?
No. They keep enforcing. HA protects your ability to manage and your configuration database, not the traffic.