Bug ID 698757: Standby system saves config and changes status after sync from peer

Last Modified: May 14, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP ASM(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5

Fixed In:
14.0.0, 12.1.4

Opened: Dec 13, 2017
Severity: 3-Major
Related AskF5 Article:
K58143082

Symptoms

After running config sync from an Active to a Standby device, the sync status is in SYNC for a short period time. After a while, it automatically goes to Changes Pending status.

Impact

The high availability (HA) configuration goes out of SYNC.

Conditions

-- Manual sync device-group configuration. -- Modify existing policy encoding to uppercase (via tmsh). -- ASM configuration.

Workaround

Use either of the following workarounds: -- Push the sync back from the Standby device to the Active device, and then again from the Active to Standby. -- Put the device group into auto-sync state and push the config from the Active to the Standby. After the Sync state resolves and the ASM configuration is finished loading, the device group can be put back to Manual sync.

Fix Information

Change requested encoding to lowercase.

Behavior Change