Technical Tip: How to identify FortiADC HA out-of-sync issue due to GEOIP DB library and steps to resolve

[kmak]

Description	This article describes the troubleshooting of the FortiADC HA out-of-sync issue due to the GEOIP DB library.
Scope	FortiADC.
Solution	Scenario: FortiADC setup in HA Active-Passive. FortiADC HA status is shown as 'Not Sync'. Troubleshooting: Log into the FortiADC GUI access and check on the HA status. The HA status panel is showing the message 'Not Sync'. Select the 'Details' option to view the config details that are not in-sync. The FortiADC HA configuration comparison shows the config parts that are not in-sync between the Master and Slave units. In the scenario the configuration differences are shown to be the GEOIP DB library version. Workaround: Run the command to manually sync the config from Master to Slave FortiADC. execute ha force sync-config all The HA config sync takes a few minutes to complete, and the Slave/Secondary FortiADC will be triggered to reload after the manual sync. The access to the Slave/Secondary unit will be interrupted during the system reload process which takes about 5~10 minutes. Check the HA sync status afterward and it should be showing 'In Sync' now. Resolution: The GEOIP DB library synchronization issue will be resolved in the release version below later. v7.8.0. v7.6.2. v7.4.7. Related documents: execute ha force sync-config HA troubleshooting