Last Modified: Mar 20, 2019
See more info
Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 13.1.1, 126.96.36.199
14.1.0, 14.0.0, 188.8.131.52
Opened: Jun 04, 2018
Related AskF5 Article: K30764018
MCP logs 'Removed publication with publisher id TMMx' and the affected TMM restarts.
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.
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.
The internal driver has been improved, allowing it to work in low- and/or fragmented-memory conditions.