Last Modified: Nov 25, 2025
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
17.1.3, 17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3
Opened: Nov 03, 2025 Severity: 3-Major
Mcpd crash or restart causes TMM to enter a restart loop. Log - notice TMM PU (7) >= number of PUs (4) Device becomes unreachable in the data plane.
System enters a TMM restart loop and remains offline. Traffic processing and configuration access are unavailable until manual correction.
BIG-IP VE with more vCPUs than licensed cores. Example: 8-core Azure instance with a 4-core VE license. Modules: AFM (nominal) and AVR (minimum) provisioned. Occurs after mcpd restart or crash.
Manually set the provision.tmmcount DB variable to match the licensed core count, then restart services or reboot. For example on an 8-core instance which is licensed for only 4-cores: tmsh modify sys db provision.tmmcount value 4
None