If you are managing the cluster via FortiManager, ensure that the cluster is set to before attempting the upgrade. FortiGate‑7000 clusters with uninterruptable‑upgrade enabled follow a similar but more granular multi‑step process.
When upgrading a FortiGate High Availability (HA) cluster, the firmware automatically orchestrates the process to keep downtime near zero: The upgrade command is delivered to the primary unit.
FortiGate firmware is more than just a firewall manager; it is a unified security platform that coordinates multiple protection layers.
After the original primary node recovers, the cluster re-evaluates roles based on your configured HA priority and override settings. fortigate firmware
Successful firmware upgrades are built on . By following the structured approach outlined in this guide — pre‑upgrade preparation, using the Upgrade Path Tool, safe rollback procedures, and systematic recovery techniques — you can confidently keep your FortiGate fleet secure and up‑to‑date, even in complex HA deployments.
Check for sections to identify potential conflicts. C. Determine the Supported Upgrade Path
If an upgrade introduces a critical issue, you can downgrade. However: If you are managing the cluster via FortiManager,
The primary unit pushes the firmware image to the secondary (subordinate) unit first. The secondary unit updates and reboots.
FortiGate firewalls operating in an Active-Passive or Active-Active HA cluster utilize a rolling upgrade mechanism to minimize network downtime.
Upgrading a High Availability (HA) cluster requires extra caution to avoid downtime. FortiGate firmware is more than just a firewall
Upgrade from the primary unit’s GUI. The system will handle the sequential upgrade of cluster members.
If you are currently on FortiOS 7.0, plan a migration to 7.2 or 7.4 before 7.0 reaches end-of-support. If you are on 6.x, plan an immediate, carefully tested upgrade path to 7.2 or 7.4. Your network’s security depends on it.
Log in to the FortiGate GUI and navigate to > Firmware .