Bug ID 953425: Hardware syncookie mode not cleared when changing dos-device-vector enforcement

Last Modified: Oct 21, 2020

Bug Tracker

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

Known Affected Versions:
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.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 16.0.0, 16.0.0.1

Opened: Oct 08, 2020
Severity: 3-Major

Symptoms

Changing DOS vector enforcement configuration can cause BIG-IP to get stuck in hardware syncookie mode.

Impact

Device is stuck in hardware syncookie mode and generates syncookies.

Conditions

- Changing DOS vector enforcement configuration when device is in global syncookie mode. For a list of platforms that support hardware syncookie protection, see https://support.f5.com/csp/article/K14779

Workaround

Run the following command: tmsh restart sys service tmm Impact of workaround: restarting tmm disrupts traffic.

Fix Information

None

Behavior Change