Bug ID 556262: tmm may time out and be killed by sod in case of Nitrox lockup

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,

Opened: Nov 04, 2015

Severity: 3-Major


tmm may time out and be killed by sod in case of Nitrox lockup. The system issues a SIGABRT from sod, at which point the tmm leaves a core file and the BIG-IP system fails over to the standby unit, if applicable.


The primary impact of this behavior is a short delay (one or two seconds) before a failover is triggered. Failover is initiated only after sod determines that tmm has failed to respond to a heartbeat.


BIG-IP platforms with a Cavium Nitrox card. The device stops responding to communication from the host at a time that coincides with another process, such as the driver attempting to process completed requests. Note: This issue does not affect the BIG-IP 1000, 2400, 51x0, 2000s, 2200s, 4000s, and 4200v platforms. All other current BIG-IP platform models are equipped with Cavium Nitrox SSL or hardware compression hardware.



Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips