Bug ID 510499: System Crashes after Sync in an ASM-only Device Group.

Last Modified: Sep 13, 2023

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

Known Affected Versions:
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.5.2 HF1, 11.5.3 HF1, 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.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.0 HF5, 11.5.3 HF2

Opened: Mar 04, 2015

Severity: 3-Major

Related Article: K17544

Symptoms

System crashes after an ASM Sync in an ASM-only Device Group.

Impact

Peer Device is left in an inconsistent state and BD crashes.

Conditions

This occurs when the following conditions are met: 1) Two devices with both a full-sync device group, and a sync-only, ASM-enabled device group. Both manual sync groups. 2) Have a policy active on a virtual server on both devices. 3) Deactivate the policy on one device. 4) Push the ASM config from that device to another device.

Workaround

None.

Fix Information

ASM Configuration Sync now will gracefully handle being unable to deactivate when it conflicts with LTM config.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips