Bug ID 1976105: Sync failure between primary and secondary

Last Modified: Dec 19, 2025

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

Known Affected Versions:
16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 16.1.6, 16.1.6.1

Opened: Jul 04, 2025

Severity: 3-Major

Symptoms

When syncing configurations between a Primary (Active) and Secondary (Standby) device, the Secondary device performs validation before applying the new configuration. If the old stale configuration on the Secondary device is invalid (e.g., Virtual Server (VS) has a DoS profile but lacks a required HTTP profile), the pre-application validation fails, causing the sync to abort.

Impact

Sync between primary and secondary device fails.

Conditions

DoS profile with HTTP profile enabled.

Workaround

On the Secondary device, detach the DoS profile from all associated Virtual Servers. Then delete DoS Profile. Login to the primary device and push the configuration from Primary to Secondary. The config sync should now complete successfully.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips