Bug ID 1223613: When there is ongoing dos attack, Attack session id is not being updated in the new DSSM primary on DSSM primary restart

Last Modified: Nov 29, 2025

Affected Product(s):
BIG_IP_NEXT(CNF) CNF(all modules)

Fixed In:
1.3.1, 1.3.1

Opened: Jan 11, 2023

Severity: 2-Critical

Symptoms

Attack count is incremented on multiple tmm pods when DSSM is restarted while there is single ongoing DOS attack.

Impact

Single ongoing dos attack is counted as attack by multiple tmm pods.

Conditions

- CNF running in multiple tmm pod scenario - Dos is enabled - Ongoing Dos attack - DSSM is restarted

Workaround

None

Fix Information

When there is ongoing dos attack, Attack session id is not being updated in the new DSSM primary on DSSM primary restart

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips