Bug ID 544963: Upgrades of vCMP guests with the default-sized 100GB vdisk image and with SWG plus any of AFM, AM, APM, AVR, ASM, PEM, FPS provisioned will fail due to insufficient disk space

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP Install/Upgrade, vCMP(all modules)

Known Affected Versions:
11.5.0, 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, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3,,,,, 11.6.4, 11.6.5,,,, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4

Fixed In:

Opened: Sep 09, 2015
Severity: 3-Major
Related Article:


When a user provisions certain module combinations on a vCMP guest with the default-sized 100 GB virtual disk image, upgrading the guest to a second software volume and migrating the configuration forward may cause provisioning to fail due to insufficient disk space once the guest boots into the newly install software volume.


Module provisioning fails in the guest after it boots into the newly installed volume due to insufficient disk space. The guest remains inoperative until the issue has been resolved.


A vCMP guest has a certain module combination provisioned (one that includes the SWG module along with any one of the following: AFM, AAM, APM, AVR, ASM, PEM, or FPS), that requires a large amount of disk space, and the guest boots into a newly installed second software volume with the configuration migrated. The issue might also occur with other module combinations, for example, APM-ASM-AVR-LTM.


The workaround involves creating a new virtual disk image for the guest and installing onto it the desired upgrade version. Please follow these steps: 1) Create and back up a UCS from the guest. 2) Move the guest to the 'configured' state to stop the guest's VM. 3) Once the guest's VM has been stopped, specify a new name for the guest's virtual disk image in the guest's 'virtual-disk' property. 4) Set the guest's 'initial-image' property to the name of the ISO, for example, initial-image BIGIP- 5) Set the guest back to the 'deployed' state and wait for the guest VM to install and boot up. 6) Install the saved UCS onto the guest. Note: If you are installing TMOS v12.0.0, TMOS v11.6.1, TMOS v11.6.0, or any version of 11.5.x, you will encounter this same issue the next time you try to upgrade. So, ideally, you should upgrade to a version where this bug is fixed.

Fix Information

The default virtual disk image size has been increased to 150 GB. Furthermore, the 'vcmp.vdisk.new_image_size' DB var has been added to allow users to modify the size of newly created virtual disk images in the event that the new default value is not large enough.

Behavior Change