Last Modified: Feb 13, 2019
See more info
Known Affected Versions:
11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 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
12.0.0, 11.6.1, 11.5.1 HF6, 11.4.1 HF9
Opened: Dec 03, 2013
Related AskF5 Article: K16262
If an APM policy sync puts the new policy on a member of a sync-failover device group then the sync of the sync-failover group may fail.
Sync will fail, but full load sync will then succeed.
* At least three devices in trust. * Two devices in a sync-failover device group. * Two devices in a sync-only device group suitable for APM policy sync. * The policy is synchronized from a device that is not in the sync-failover device group.
Using a full load sync (the force option on the GUI sync page) will work.
If an APM policy sync puts the new policy on a member of a sync-failover device group then the sync of the sync-failover group used to fail. This now succeeds.