Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP vCMP
Known Affected Versions:
11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 13.0.0
Fixed In:
13.1.0, 13.0.0 HF1, 12.1.2 HF1, 11.5.4 HF3
Opened: Oct 05, 2016 Severity: 3-Major
After the first boot, the system runs provisioning and boots successfully, but there is a file left on the system /mprov_firstboot. This will appear in /var/log/ltm: info mprov:4614:: \'\'provision.initialized\' indicates force TMOS only provisioning - forcing.\' During a subsequent boot, provisioning will run again, potentially unnecessarily, due to the existence of this file. The following will appear in /var/log/ltm during the second boot: info mprov:4609:: \'Existence of file \'/mprov_firstboot\' indicates force TMOS only provisioning - forcing.\'
On a vCMP host, the second provisioning may not complete properly and guest systems will not pass traffic. The vCMP host will continually try to start more than one tmm and fail when there should only be one tmm running. The /var/log/tmm logfile on the vCMP host will contain: <13> Sep 25 01:33:28 vcmphost1 notice Too small memsize (60) -- need at least 136 MB The /var/log/tmm logfile on the vCMP guest will contain: <13> Sep 25 01:38:21 bigip1 notice Failed to write /var/run/libdag.so_2, err: -30 <13> Sep 25 01:38:21 bigip1 notice panic: vdag failed to attach <13> Sep 25 01:38:21 bigip1 notice ** SIGFPE **
The memory size of the host changes and there is some other need for reprovisioning (for example a new configuration load).
If the vCMP host is in a tmm restart loop due to this issue, reboot the vCMP host to allow the system to come up properly.
The BIG-IP software now always removes the /mprov_firstboot file when the system is reprovisioned.