Bug ID 750353: Manual Device Group Put in Pending State With No Indication

Last Modified: Jan 20, 2023

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.4,, 12.1.5,,,, 12.1.6, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,

Fixed In:

Opened: Nov 18, 2018
Severity: 5-Cosmetic


When Session Tracking is enabled on devices in a Manual Sync ASM-enabled device group, the device group can be put into 'Pending' state with no indication as to what changed in the system. This is because Audit Log Messages are not written for changes due to Session Tracking.


It is unclear why the device group is in Pending State and what the impact is if the configuration is pushed to a peer.


-- ASM Sync is enabled on a Manual Sync Device Group. -- Session Tracking is enabled on an ASM Security Policy.



Fix Information

When in a high availability (HA) environment, changes to Session Tracking are now written to the Audit log as batched events, similar to the following example: x Sessions were set to 'Block All'

Behavior Change