Bug ID 520280: Perl Core After Apply Policy Action

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP ASM(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.5.2 HF1, 11.5.3 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 HF6, 11.5.3 HF2

Opened: Apr 28, 2015

Severity: 2-Critical

Symptoms

Apply policy causes a perl core Further apply policy do not work

Impact

Apply policy causes a perl core and ASM config event dispatcher crash. ASM config event dispatcher then is not restarted and remains down. Further apply policy do not work.

Conditions

ASM provisioned. LTM provisioned. An ASM policy exists that is referenced by an LTM (L7) policy which is not assigned to any LTM virtual server.

Workaround

Make sure that if an ASM policy exists that is referenced by an LTM (L7) policy then such LTM (L7) policy is assigned to some LTM virtual server. one can create a dummy LTM virtual server for that purpose.

Fix Information

Perl no longer cores and crashes ASM config event dispatcher in the case of an apply policy to an ASM policy that is referenced by an LTM (L7) policy which is not assigned to any LTM virtual server.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips