Last Modified: Mar 17, 2021
See more info
Known Affected Versions:
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, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 11.6.4, 11.6.5, 18.104.22.168, 22.214.171.124, 126.96.36.199
Opened: Feb 19, 2015
Related AskF5 Article: K52630023
TMM crashes with an assertion 'flow not in use' log message. This issue is more prominent when traffic selector narrowing occurs during IPsec/IKE negotiations.
TMM does not removes a flow properly. TMM crashes. The tmm log contains a message similar to the following: notice panic: ../base/flow_table.c:598: Assertion 'flow not in use' failed. Traffic disrupted while tmm restarts.
During traffic selector narrowing, the narrowed selector policies are added and deleted multiple times for the same parent ipsec policy. During this process, improper release of flows by TMM causes this issue.
There is no workaround at this time.
TMM now releases the flow properly and TMM does not crash.