Is it supported to change the vDisk size of a new CUCM 12.5 2500 users ova?

[Elter]

Is it supported by Cisco TAC to change the vDisk size of a new CUCM 12.5 for 2500 users ova from the default 80GB to 110GB on a new (green field) installation?

It is not to resize an already installed machine, it is a new deployment, increasing the default ova disk size.

The idea is to have more space and be prepared for future possible increase in size requirements or to avoid to run the ciscocm.free_common_space scripts or manually remove files to have enough space on upgradings.

Thanks

[TONY SMITH]

Doesn't that leave BE6K deployments goosed, as they aren't permitted to use any OVA profile bigger than 1000 user, 80GB

Workaround:
The only supported, documented way of increasing the size of the disk without risking partition alignment or performance problems is rebuilding the node using a larger OVA file.

[Roger Kallberg]

For this second disk resize it’s still listed as an option in public documents, see this for example. https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/10_0_1/CUCM_BK_U4214F9D_00_upgrade-guide-cucm-100/CUCM_BK_U4214F9D_00_upgrade-guide-cucm-100_chapter_011.html#CUCM_TK_C9AFC8CC_00

[pavelherc]

I have a simillar problem. 

Customer has a BE6H-M5 with CUCM14SU2 -> SU3 and we have run to that Bug CsCvt97709. 3 of 4 nodes were cleared with the script but the Publisher node still stays at 96%. 

I have tried all possible but the value dont change. 

I have seen that the workaround is to use bigger ova (110 GB ) template but it is valid also for the B6H-M5 hardware?

Has anyone tried the workaround on such HW configuration?

Thanks in advance, 

Pavel 

[Roger Kallberg]

To use a bigger sized disk with a one disk installation you’d need to build a new VM by using the OVA and selecting a 110 GB sized installation option. Once you’ve installed the same version as you have now you need to restore a DRS backup.

[pavelherc]

Hi Roger, 

 Thank you for the Answer, 

that is how we plan it to do, (re-deploy the VMs in another VLan with the same hostnames etc, restore from backup and then update to SU3) 

My question was more regarding that HW - BE6H-M5 ( as mantioned from Tony Smith in his Reply 2 steps above from 09-21-2020 06:20PM)...-  are there any limitations for that HW or we can take the 110GB size template?

[Roger Kallberg]

From what I know the hardware you ask about have no real relevance to how the VMs are built. In fact the same applies to any other hardware. It does not have relevance to the disc size used on the VM, as long as there are enough actual space available for the allocation to the VM as such.

[pavelherc]

HI Roger, 

thank you for the answer. then we will proceed as you mentioned before. 

[TONY SMITH]

Some BE6K variants had a CPU that only meets Cisco's requirements for the 1000 user OVA.

[Joe Price]

Resizing the VM hardware is 100% doable.  I know, Im working on a system now.

My version is 11.5.1.15900-18 and Im going to 14(SU3)

Current Hardware settings are 1 vcpu 4gig memory and 80g HD

Hardware settings after the cange 2vcpu 8gig memory and 110g HD

Here are the steps:

Make sure vmware tools is updated and current

Upgrading VMtools:

1. End any existing VMtools install: Right Click > Guest > End VMWare Tools install

2. Console/SSH to device and run:  utils os secure permissive

3. Start VMTools install: Right Click > Guest > Install/Upgrade Vmware tools

4. Run utils vmtools refresh

5. Server will reboot, possibly twice

6. Console/SSH back to server and run: utils os secure enforce

Upgrading Hardware:

1.  Run the ciscom.free_common_space-v1.8k4.cop.sha512

2.  Shutdown CUCM

3.  Change the hardware settings for CPU / Mem / Disk

They must be the same as the OVA you are mimicking.  2vcpu / 8gig mem / 110 HD

4.  Power on the server

5.  Monitor the console of the server and you will see that it automatically resizes and reboots itself because it detects hardware changes.

Is this official?  Thats a grey area.  If you get the right TAC engineer they will do the same steps I've written above. 

[Roger Kallberg]

Good information, however at some point in time you’d want to get your system rebuilt by either data export/import or DRS restore due to the changes in file system type newer versions are using. For example it would not work to upgrade to version 15 if you came from an installation that was built back when ext3 file system was used as it requires ext4. The latest pre-upgrade COP file would tell you if this is the case.