Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP ASM
Known Affected Versions:
11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 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.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, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1
Fixed In:
13.1.0
Opened: Jun 22, 2017 Severity: 3-Major Related Article:
K85074430
Policies are either not (fully) created or not (fully) deleted on the peer device
Policies are either not created/deleted, or not fully created/deleted. Note: Fully created and fully deleted meaning that the following commands agree with each other: # tmsh list asm policy one-line all-properties # tmsh list asm policy one-line
-- Device Service Clustering configured. -- High availability (HA) configuration with Sync-Only (no failover) device group (Auto, incremental) with ASM sync enabled. -- Create/delete active/inactive ASM policies via TMSH/GUI.
Issue a forced full sync from the originating device to the device group.
We have fixed the process of create/delete active/inactive ASM policies so that the actions would be correctly synced over to the peer device in a HA pair with Sync-Only (no fail-over) device group (Auto, incremental) with ASM sync enabled