Last Modified: Mar 22, 2023
See more info
Known Affected Versions:
14.1.0, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 14.1.2, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 15.1.0, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 15.1.1, 15.1.2, 184.108.40.206, 15.1.3, 220.127.116.11, 15.1.4, 18.104.22.168, 15.1.5, 22.214.171.124, 15.1.6, 126.96.36.199, 15.1.7, 15.1.8, 188.8.131.52
Opened: Apr 12, 2019
A sync failure might happen in a sync-failover device group after manually editing the /config/bigip.conf file and removing the Bot Defense profiles, and then performing a config sync. The system reports a sync error message similar to this: FODG (Sync Failed): A validation error occurred while syncing to a remote device. - Sync error on device-b: Load failed from /Common/device-a 01020036:3: The requested profile (/Common/bot-defense-device-id-generate-before-access) was not found. - Recommended action: Review the error message and determine corrective action on the device.
Manually editing the /config/bigip.conf file and removing the Bot Defense profile, then loading the config, and performing a config sync. This sync failure may happen even without ASM provisioned, and in rare cases may happen even if you have not modified the base Bot Defense profile.
Reload the config from the receiving device, and then perform a force sync in the opposite direction, overriding the previous changes. This should bring the system back to in sync.
Sync failures no longer happen when removing Bot Defense profiles from the config file and loading config.