Bug ID 486724: After upgrading from v10 to v11 in a FIPS HA setup, config-sync fails

Last Modified: Oct 25, 2026

Affected Product(s):
BIG-IP Install/Upgrade, LTM(all modules)

Known Affected Versions:
11.5.1, 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.0, 11.6.0 hf1, 11.6.0 hf2, 11.6.0 hf3, 11.6.0 hf4, 11.6.0 hf5, 11.6.0 hf6, 11.6.0 hf7, 11.6.0 hf8, 11.6.1, 11.6.1 hf1, 11.6.1 hf2, 11.6.2, 11.6.2 hf1, 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

Fixed In:
12.0.0, 11.5.2

Opened: Oct 24, 2014

Severity: 3-Major

Related Article: K16750

Symptoms

After upgrading from TMOS v10 to TMOS v11 in a FIPS HA setup, config-sync will fail.

Impact

HA devices will be in sync failed state

Conditions

In a FIPS HA setup, upgrade from v10 to v11. After upgrade, trigger config-sync.

Workaround

This issue has no workaround at this time.

Fix Information

Config-sync will now be successful after upgrading from v10

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips