Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP MA-VE, vCMP
Known Affected Versions:
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, 12.1.2 HF1, 12.1.2 HF2
Fixed In:
12.1.0
Opened: Sep 11, 2015 Severity: 3-Major
When increasing the size of the disk image for a vCMP guest BIG-IP or VE BIG-IP, the system will fail to boot the next time it is deployed. Specifically, the system will not be reachable via SSH, and logging in via the serial console is rendered impossible due to the faulty boot.
The BIG-IP system remains inoperative until the workaround steps are executed.
This only happens to vCMP guest BIG-IPs and VE BIG-IPs whose disk image size has been increased.
To work around this issue, first allow the BIG-IP system to finish its failed boot. Then un-deploy and re-deploy the BIG-IP from its hypervisor. The BIG-IP system's second boot attempt will work, and the system comes up fully operational and with the additional disk space accounted for.
The underlying issue has been fixed such that the vCMP guest BIG-IP or VE BIG-IP system boots up correctly the first time after its disk size has been increased.