Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP ASM
Known Affected Versions:
11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.6.2 HF1, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 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:
12.0.0, 11.6.0 HF5, 11.5.2 HF1
Opened: Feb 12, 2015 Severity: 3-Major
When a failover device group (without ASM enabled) is in a fully synchronized state, and then ASM and auto-sync are enabled on the device group through tmsh, the units sit waiting for an 'initial sync' event which never comes. All subsequent sync events are Incremental and never Full.
Infrequently, an initial sync event fails after ASM and auto-sync are enabled on a failover device group that does not have ASM enabled.
-- A failover device group (without ASM enabled) is in a fully synchronized state. -- ASM and auto-sync are enabled on the device group through tmsh.
You can use either of the following workarounds: -- Configure ASM device sync before the initial sync. -- Configure ASM device sync using the GUI instead of tmsh.
This release fixes an issue that occurred rarely when an initial sync event did not occur after ASM and auto-sync were enabled on a failover device group that did not have ASM enabled.