Bug ID 722893: The TMM - host interface may stall when the kernel memory is fragmented

Last Modified: Mar 20, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1

Fixed In:
14.1.0, 14.0.0, 13.1.1.2

Opened: Jun 04, 2018
Severity: 2-Critical
Related AskF5 Article:
K30764018

Symptoms

MCP logs 'Removed publication with publisher id TMMx' and the affected TMM restarts.

Impact

Degraded performance and unexpected failover when tmm restarts. Traffic disrupted while tmm restarts. Note: If this issue is encountered during early startup, instead of restarting, TMM may continuously log 'MCP connection expired early in startup; retrying'. In this case it may be necessary to manually restart TMM.

Conditions

This occurs when the following conditions are met: -- Linux kernel memory fragmentation exists. -- Another operation is occurring, including (among others): + Config-sync with full reload is initiated. + Running tcpdump.

Workaround

None.

Fix Information

The internal driver has been improved, allowing it to work in low- and/or fragmented-memory conditions.

Behavior Change