| Description | This article describes an issue where a 'system.federated-upgrade' checksum causes an HA desync. |
| Scope | FortiGate. |
| Solution |
This error is triggered when the fabric upgrade is enabled on the HA devices and after targeted firmware upgrade is finished, but the the cluster still goes out-of-sync.
While hovering over the HA device, it will show 'system.federated-upgrade' has a mismatch in checksum values.
If HA reservation management is enabled, log in to the secondary device via the GUI and disable the Fabric upgrade.
The following is what the configuration looks like:
FortiGate-60F # config global FortiGate-60F (global) # config system federated-upgrade FortiGate-60F (federated-upgrade) # sh
But while deleting from CLI, it returns the error:
FortiGate-60F # config global FortiGate-60F (global) # config system federated-upgrade FortiGate-60F (federated-upgrade) # config node-list FortiGate-60F (node-list) # delete FGT60FTK20006777
FortiGate-60F (global) # execute federated-upgrade cancel
Once the command is executed the status will be changed to disabled, wait for a while and HA status will show in-sync.
For more information on Fabric-upgrades, refer to Upgrading all devices - FortiGate 7.6.3 administration guide To sync HA manually, refer to Technical Tip: Procedure for HA manual synchronization |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2026 Fortinet, Inc. All Rights Reserved.