Bug ID 504182: Enforcer cores after upgrade upon the first request

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP ASM, Install/Upgrade(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.6.2 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, 11.5.2 HF1

Opened: Feb 02, 2015

Severity: 2-Critical

Symptoms

If an ASM security policy contains entities with an invalid configuration from a previous version, UCS load will fail and leave the device in an inconsistent state, leading to BD crash.

Impact

UCS load will fail and leave the device in an inconsistent state, leading to BD crash.

Conditions

-- An ASM security policy contains entities with an invalid configuration from a previous version. -- This can occur on an upgrade from 11.5.x to 11.6.0 prior to HF5.

Workaround

Correct ASM entity configuration before upgrade.

Fix Information

This release fixes an upgrade issue where the Enforcer crashed after the upgrade upon the first request.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips