Created on
01-31-2023
08:30 AM
Edited on
12-19-2024
09:26 PM
By
Anthony_E
Description | This article describes the differences between 'debugzone' and 'checksum' in an HA cluster. |
Scope | FortiGate HA cluster. |
Solution |
The checksum of cluster units can be viewed with the following command:
diag sys ha checksum cluster
================== FGT1 ================= debugzone global: : 79 24 76 8a a8 03 9a 81 dc c4 3c f8 96 72 59 11 checksum global: : 79 24 76 8a a8 03 9a 81 dc c4 3c f8 96 72 59 11
================== FGT2 ================== is_manage_master()=1, is_root_master()=1 debugzone global: : 79 24 76 8a a8 03 9a 81 dc c4 3c f8 96 72 59 11 checksum global: : 79 24 76 8a a8 03 9a 81 dc c4 3c f8 96 72 59 11
Sometimes, the debug zone on each device does not match. For example:
diag sys ha checksum show
================== FGT1 ================= debugzone global: : 79 24 76 8a a8 03 9a 81 dc c4 3c f8 96 72 59 11 checksum global: : 79 24 76 8a a8 03 9a 81 dc c4 3c f8 96 72 59 11
If there is a difference between both, it means changes have been made to the device but not yet written into the actual configuration.
Usually, this state should only be seen for a very short duration. If the state persists for a longer time, use the command 'diagnose sys ha checksum recalculate'.
Additionally, it is possible to recalculate only 'root' or 'global' using the following commands:
diag sys ha checksum recalculate global diag sys ha checksum recalculate root
If the correct results still do not appear, it may be necessary to reboot the device, as the CMDB server may not be working correctly. |
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 2025 Fortinet, Inc. All Rights Reserved.