Forum Discussion
TMM Restarting (OS Version 12.1.1)
If the unit is covered by a support contract and this is service impacting, your best bet is to open a support case to investigate the issue live.
Most common reason for a unit to behave like this is if you have a VLAN failover enabled, and unit has the monitored links down.
I haven't seen this specific evidence in your logs, but you do have a deamon heartbeat failure error. That means a system process is failing to respond to HA daemon heartbeat messages, which triggers the failover.
Again, I'd suggest you have support look into this.
- SatriajiMar 23, 2023Cirrus
The technical support for this OS device has been out of support (Technical EOS at 2021), so we cannot open TAC to support.
For now the log still appear :
[msi@JTLSF-DNS-PR-SOA-PREPROD:INOPERATIVE:Standalone] ~ # Mar 23 23:51:45 JTLSF-DNS-PR-SOA-PREPROD emerg logger: Re-starting tmm
This device is vCMP Guest, the other guest is normal. Just thist guest that having problem tmm restarting.
- DuncanJonesMar 24, 2023Nimbostratus
Satriaji wrote:The technical support for this OS device has been out of support (Technical EOS at 2021), so we cannot open TAC to support.
For now the log still appear : Tower Defense
[msi@JTLSF-DNS-PR-SOA-PREPROD:INOPERATIVE:Standalone] ~ # Mar 23 23:51:45 JTLSF-DNS-PR-SOA-PREPROD emerg logger: Re-starting tmm
This device is vCMP Guest, the other guest is normal. Just thist guest that having problem tmm restarting.
The Traffic Management Microkernel (tmm) process may restart without a stack trace or core file after becoming disconnected from the Master Control Program Daemon (mcpd) process.
This issue occurs when all of the following conditions are met:
- The Linux kernel memory becomes fragmented.
- Another memory-intensive operation occurs, which may include:
- You perform a configuration synchronization (ConfigSync) with full reload.
- You run a tcpdump session.
If tmm fails to start or restart properly as a result of this issue, you can try to recover the system temporarily by restarting the BIG-IP system.
- alayne786Nov 02, 2023Altostratus
Any resolution?? We have bigip LTM 14.1 and it's been doing this for 24 hours now, but it's this exact situation. How did you fix it?? We do have a vLan failover ..Been waiting for 24 hours from f5 support with no resolution in sight .
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com