Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP ASM
Known Affected Versions:
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.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 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.1 HF2
Opened: Mar 26, 2015 Severity: 2-Critical Related Article:
K52212526
Apply policy operation hangs. The system logs the following messages in /ts/log/asm_config_server.log: ---------------- F5::SetActive::Impl::send_update_core,,Still waiting for response from bd_agent (XXX seconds) ---------------- Where 'XXX' is ever growing... High CPU usage, by the 'asm_config_server' process, while the apply policy is stuck.
Apply policy operation hangs.
ASM provisioned. Apply policy is executed (manually or automatically, by Policy Builder for an example). bd/bd_agent are restarted (for any reason) during the apply policy operation.
Use one of the following commands: -- bigstart restart asm. -- pkill -f asm_config_server.
Apply policy operation now has a timeout threshold, which prevents the apply policy operation from hanging.