Bug ID 462527: Config Sync does not work after Devices entered an inconsistent Initializing State.

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP ASM(all modules)

Known Affected Versions:
11.2.1, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:

Opened: May 15, 2014

Severity: 3-Major


Devices indicate they are in sync, but the ASM configurations are not in sync.


The primary cannot sync to the secondary since it believes it is in the Init state, and thus does not set the asm device-sync timestamp, while at the same time the secondary believes it is not in the Init state and is waiting for an updated asm device-sync timestamp.


Two devices in a manual failover group reach a state where the primary responds as if it is the Initializing State of joining a device group, but the secondary does not respond as if it is in the Initializing State of joining a device group.


In the primary GUI, turn off ASM sync for the device group, and then turn it back on. This gets both devices to refresh their sync state. Then a sync from the primary to the secondary should succeed.

Fix Information

The system now updates the local timestamp for changes when in a manual sync group, even if they appear to be in sync_init state.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips