| Description | This article will describe the troubleshooting steps if the HA is out of synchronize for the checksum mismatch of the object 'web.proxy.global'. |
| Scope | FortiGate |
| Solution |
If the HA cluster shows that the secondary unit is out of sync and while checking the checksum after hovering over the 'Not Synchronize' status it shows the object 'web.proxy.global' checksum is not matching like following way, it is suggested always to check the specific part configuration.
From CLI :
Run the command below on both the Cluster unit and compare the checksum value:
diagnose sys ha checksum show root web.proxy.global
If the part configuration does not match, it has to be reconfigured manually to match, and it will synchronize after that. But in case, the configuration can be the same in both units, while the object checksum is still mismatching.
FGT1(primary)# config web-proxy global
FGT2(secondary)# config web-proxy global
In this situation, the workaround is to change the default 'proxy-fqdn' configuration under web-proxy from global.
FGT1(primary)# config web-proxy global
Once it has been changed only in the primary, recalculate the checksum with the 'diagnose sys ha checksum recalculate' CLI command. After the cluster is synced again.
|
