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
In some cases, the debug zone on each device already 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
The debug zone most likely displays configuration changes pending being written into the checksum.
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'.
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 2024 Fortinet, Inc. All Rights Reserved.