Bug ID 595313: "vcmp.vdisk.new_image_size" BigDB variable ignored when using virtual disk templates

Last Modified: Jul 22, 2021

Bug Tracker

Affected Product:  See more info
BIG-IP vCMP(all modules)

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.4,, 12.1.5,,,, 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.1,,,,, 13.1.3,,,,,,, 13.1.4,, 14.0.0,,,,,, 14.0.1,

Opened: May 23, 2016
Severity: 4-Minor


The "vcmp.vdisk.new_image_size" BigDB variable controls the size of newly create virtual disk images for vCMP guests. However, when vCMP Fast Provisioning is used (i.e., virtual disk templates), new virtual disk images created from a virtual disk template will have the same size as the template.


The virtual disk image(s) created for a vCMP guest may have an unexpected and/or undesirable size.


You may experience this issue if: * The vCMP host BIG-IP system is configured to use virtual disk templates, which is the case by default. * The "vcmp.vdisk.new_image_size" BigDB variable has been changed from its default value. * A new virtual disk image is created for a vCMP guest using a virtual disk template that was created before the "vcmp.vdisk.new_image_size" BigDB var was modified.


To force the system to create a new virtual disk template using the size specified in the "vcmp.vdisk.new_image_size" BigDB variable, set the "vcmp.installer.use_vdisk_templates" to "disabled" using the following TMSH command: # tmsh modify sys db vcmp.installer.use_vdisk_templates value disabled Then set the vCMP guest to the provisioned or deployed state to initiate a new virtual disk image install for the guest. If a virtual disk image of the undesired size has already been created, it should be deleted first.

Fix Information


Behavior Change