Bug ID 653017: Bot signatures cannot be created after upgrade with DoS profile in non-Common partition

Last Modified: Sep 13, 2023

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

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 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, 12.1.4, 12.1.4.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0, 12.1.5

Opened: Mar 23, 2017

Severity: 3-Major

Symptoms

Bot signatures cannot be created after roll-forward upgrade of configuration with only a DoS profile in non-Common partition.

Impact

Bot signatures are not created.

Conditions

A DoS profile in non-Common partition has Proactive Bot Defense enabled

Workaround

Delete DoS Profile before upgrade, and re-create after upgrade is successful. Alternatively, another DoS Profile can be created in /Common, even if unused.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips