Last Modified: Nov 07, 2022
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 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.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1
Fixed In:
12.0.0, 11.6.1 HF2
Opened: Aug 15, 2014 Severity: 3-Major Related Article:
K05101350
When an LTM policy action that takes place during an HTTP request or response fails (which is very rare), the affected connection hangs until a timeout occurs.
When an LTM policy action fails, affected connections hang until they time out.
This issue occurs when you attach an LTM policy to a virtual with a rule that has an action that fails. Now send a request that matches that rule. The command 'tmsh show ltm policy' will show the action failed, but the connection 'hangs' until timeout.
This issue has no workaround at this time.
When an LTM policy action fails, the affected connection no longer hangs until timeout, but rather gets reset immediately.
