Bug ID 679221: APMD may generate core file or appears locked up after APM configuration changed

Last Modified: Oct 10, 2018

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5

Fixed In:
14.0.0, 13.1.0.6, 12.1.3.4

Opened: Aug 18, 2017
Severity: 1-Blocking

Symptoms

Right after clicking the 'Apply Access Policy' link, APMD may generate a core file and restart; or appears to be locked up.

Impact

If APMD restarts, then AAA service will be interrupted for a brief period of time. If APMD appears to be locked up, then AAA service will be stopped until manually restarted.

Conditions

-- Changing APM configuration, especially Per-Session and Per-Request Policy. -- Configured for AD or LDAP Auth Agent.

Workaround

None.

Fix Information

APMD now processes the configuration changes correctly during 'modify apm profile access <profile name> generation-action increment' (TMSH) or 'Apply Access Policy' (GUI), and no service interruption occurs.

Behavior Change