Troubleshooting Tip: FortiADC HA Debugs when the Config is not in Sync

[gsharma]

Description	This article describes how to debug when HA is not in Sync.
Scope	FortiADC, FortiADC VM.
Solution	Once the HA peer setup is peering, the config-sync will begin. Some requirements must be met between HA pairs: Hardware/Platform should match. The software version should match. HA is only supported for  IPV4 configuration and is not supported for IPV6. The slave device will always sync the data from the master device, such as configuration changes, layer4 session/persistence table, layer7 persistence, and health-check status. There are sometimes some reasons why the Config Sync or Incremental Config Sync does not work as expected. As a result, the below output will appear: There are different debugs and check what could likely be the issue. The commands to debug HA are: get system ha-status diagnose debug ha basic diagnose debug ha errors diagnose debug ha message diagnose system ha sync-stat diagnose deb module hasyncd 31 diagnose deb module ha 31 diagnose deb time enable diagnose deb enable Generate a new System debug file by navigating to System -> Debug -> Select Save Debug File and download. Related document: HA troubleshooting