Bug ID 620658: Existence of /mprov_firstboot with vcmp can set improper tmmcount

Last Modified: Nov 07, 2022

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

Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9

Opened: Oct 05, 2016

Severity: 3-Major


During start-up, tmm may go into a restart loop and never come up fully.


Traffic disrupted while tmm restarts. tmm on the host goes into a restart loop due to lack of memory. Signature in the log files is similar to "notice Too small memsize (90) -- need at least 136 MB" tmm on the guests core with tmm log entries: notice panic: vdag failed to attach notice ** SIGFPE **


This can occur on both the vCMP host and guest, usually during the first or second boot of the upgraded software. The existence of /mprov_firstboot and a provision.tmmcountactual set to an incorrect value is an indication that this is occurring.



Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips