Bug ID 1060057: Enable or Disable APM dynamically with Bados generates APM error

Last Modified: May 02, 2024

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

Known Affected Versions:
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, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 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, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5

Fixed In:
17.1.0, 16.1.4, 15.1.9

Opened: Nov 07, 2021

Severity: 3-Major

Symptoms

When APM & Bados are configured together while APM is being enabled or disabled externally (i.e. via an iRule), an APM error occurs.

Impact

Unable to apply Application DoS profile to an existing APM Network Access setup.

Conditions

APM & Bados configured together while APM is being enabled/disabled externally (which is an iRule)

Workaround

No workaround. Do not enable or disable APM with iRules if Bados configured.

Fix Information

No APM errors when PM & Bados configured together and APM is being enabled or disabled externally (which is an IRule).

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips