Upgrading the FortiManager firmware for an operating cluster
Mode | The role of the FortiManager unit in the cluster. The role can be: • Master for the primary (or master) unit. • Slave for the backup units. |
Cluster Status | The cluster status can be Up if this unit is received HA heartbeat packets from all of its configured peers. The cluster status will be Down if the cluster unit is not receiving HA heartbeat packets from one or more of its configured peers. |
Module Data Synchronized | The amount of data synchronized between this cluster unit and other cluster units. |
Pending Module Data | The amount of data waiting to be synchronized between this cluster unit and other cluster units. |
You can upgrade the FortiManager firmware of an operating FortiManager cluster in the same was a upgrading the firmware of a standalone FortiManager unit. During the firmware upgrade procedure, you connect to the primary unit Web‑based Manager or CLI to upgrade the firmware. Then install the firmware on the slave units.
Similar to upgrading the firmware of a standalone FortiManager unit, normal FortiManager operations are temporarily interrupted while the cluster firmware upgrades. As a result of this interruption, you should upgrade the firmware during a quiet period.
To upgrade FortiManager HA cluster firmware
1. Log into the primary unit Web‑based Manager.
2. Upgrade the primary unit firmware.
THe firmware is forwarded to all the slave units, and then all the devices (master and slaves) are rebooted.
Administrators may not be able to connect to the FortiManager Web‑based Manager until the upgrade synchronization process is complete. During the upgrade, using SSH or telnet to connect to the CLI may also be slow, however use the console to connect to the CLI.