Description
This article describes that after upgrading the firmware, the VM device shows no information after the secondary checksum serial number, and the High Availability (HA) page fails to load in the GUI.
Scope
FortiGate.
Solution
After upgrading the firmware, the System -> HA page fails to load in the GUI on both primary and secondary devices. The behavior does not impact failover operations or lead to a split-brain scenario
Upon checking HA status through the CLI, one device appears to be out of synchronization.
FGTVM # get sys ha status
Configuration Status:
FGVMXXXXXXXX276(updated 1 seconds ago): in-sync
FGVMXXXXXXXX276 chksum dump: 6c c0 35 e2 69 6e 55 51 fd 62 e1 3c 44 80 76 6d
FGVMXXXXXXXX398(updated 1 seconds ago): out-of-sync
FGVMXXXXXXXX398 chksum dump: 06 af 74 ca e3 42 67 a2 24 c4 c2 c2 aa b1 ac 6b
When reviewing the HA checksum cluster on both devices, the secondary unit is not appearing in the HA cluster, and checksum verification may show the unit as missing or displaying incomplete output, and the issue is mirrored vice versa.
This behaviour occurs when HA-Sync fails to establish effective communication between the two devices. Ensure both units are running the same firmware version by using the get system status command.
Use the 'diagnose sys top list | grep hasync' command to confirm that the HA-Sync process is running.
If the HA-Sync process is not running, restart it by executing 'fnsysctl killall hasync', then manually initiate the HA sync process on both FortiGate units with the help of the commands below:
execute ha synchronize start
diagnose sys ha checksum recalculate
The secondary FortiGate can be accessed through the console port or via the dedicated HA management interface (if enabled). It can also be accessed from the primary FortiGate CLI using the command execute ha manage 0 admin: Technical Tip: Managing individual cluster units with the CLI command 'execute ha manage'
Note:
Super Admin privilege is required to run the 'fnsysctl' command.
After manually restarting the HA-Sync process, HA synchronization was successfully restored.
