Troubleshooting Tip: FortiGate HA Synchronization Issues due to dynamic-capability parameter Mismatch

[ataha]

Description	This article describes the steps to resolve FortiGate High Availability (HA) synchronization issues caused by a dynamic-capability parameter mismatch between the primary and secondary FortiGate. The article provides a solution to identify and resolve the mismatch, ensuring HA synchronization and stability.
Scope	FortiGate, FortiSwitch.
Solution	Dynamic capability values are by default, and they cannot be changed; it is a non-configurable value. This article has a solution where this value does not match in HA pair. As the 'dynamic-capability' parameter is non-configurable and its behavior can vary across different FortiSwitch models, it is recommended to review the following Fortinet article for detailed guidance before attempting to unset or set this parameter to bring HA into sync: Technical Tip: Dynamic capability flag on managed FortiSwitch. To resolve the HA synchronization issue due to a dynamic-capability parameter mismatch, follow these steps: Run the command get system status on both FortiGates to verify the system status. Check the FortiSwitch configuration and ensure that the dynamic-capability parameters match both FortiGates. In this case, the Dynamic capability parameters are mismatched between the two firewalls. Recalculate the checksum. If the parameters do not match even after recalculating, try rebooting the secondary FortiGate or switching over to the secondary FortiGate as the primary to synchronize the HA cluster. Monitor the HA cluster for stability after making the changes. Additionally, try running the 'diagnose debug report' command on both switches to gather more information about the issue. In this example, the checksum does not match: Use this command to get the differences in checksum from both the primary and secondary devices: diagnose system ha checksum show root switch-controller.managed-switch Dynamic-capability value mismatch: