Last Modified: Nov 07, 2022
Affected Product:
See more info
BIG-IP vCMP
Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1
Fixed In:
14.1.0
Opened: Apr 13, 2018
Severity: 2-Critical
TMM on a vCMP guest may crash and produce a core file when the guest is being shut down from the host system.
Because the vCMP guest is in the process of being shut down, there is no impact to application traffic. However, the core file may take up disk space on the vCMP guest.
The vCMP guest is being shut down by an Administrator from the host system.
To mitigate the disk space problem, manually delete the core file from the /var/core directory once the vCMP guest is brought back on-line.
TMM no longer crashes and produces a core file under these conditions. Note: If you plan to upgrade to resolve this issue, both the vCMP host and the vCMP guests must be upgraded to a suitable version.
