Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP ASM, FPS
Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0
Fixed In:
13.0.0, 12.1.1
Opened: Mar 19, 2016 Severity: 3-Major
The datasync-global-dg device-group may become out-of-sync unexpectedly without any user changes. When this happens, you can manually sync the device-group, but after about an hour, the device-group becomes out-of-sync again.
GUI/shell shows config-sync 'possible change conflict' or 'changes pending' in regards to the datasync-global-dg device-group.
-- This happens only in certain timezones, depending on the timezone configured on the BIG-IP system. (This issue has been seen only in relation to the Europe/London timezone.) -- The problem starts happening about three days after the first installation of an ASM Signature Update (ASU) or FPS Engine/Signature Update.
There is no workaround other than manually syncing the device-group approximately every hour.
The datasync-global-dg device-group no longer becomes out-of-sync unexpectedly and repeatedly every hour.