Last Modified: Oct 01, 2018
See more info
Known Affected Versions:
11.5.0, 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.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4
12.0.0, 11.6.0 HF5, 11.5.4
Opened: Mar 31, 2015
Related AskF5 Article: K93258439
When iRules direct the teardown of a TCP connection after some delay, another event might tear down the connection during the delay. When the iRule-directed abort finally arrives, the system crashes.
Traffic disrupted while tmm restarts.
(1) An iRule or other cross-layer message can trigger a ABORT after teardown. (2) The TCP profile has settings that invoke the correct TCP implementation: (a) 11.5.x: mptcp is enabled (b) 11.6.x: mptcp, rate-pace, or tail-loss-probe are enabled, OR TCP uses Vegas, Illinois, Woodside, CHD, CDG, Cubic, or Westwood congestion control.
Suspend iRules with this behavior.
When receiving ABORT commands, TCP catches cases where the connection is already closed.