The only way you are going to be able to apply new ova templates is to basically build new VM servers and then perform backups of your old applications and restore them to your newly built servers. There currently isn't a way to apply new ova templates to existing servers. I also do not see any reason to change the ova for a 9.x to 10.5 upgrade.
Hope this helps
Please rate helpful posts
I think you are wrong.
I need to change amount fo RAM, OS type and network adapter type. I can do it manualy, no problem. But I don't know when I need to do id.
Upgrade guide does cover that you need to change the OS and vNIC, AFTER the upgrade, I recommend you to review the upgrade guides, RNs, and new and changed docs prior to any upgrade. All particular considerations like those are contained within them.
The upgrade guide says that I nedd to change vm before upgrade :
|Change the configuration of the virtual machine as needed: |
For more information about making configuration changes using vSphere Client, refer to the user manual for the product.
|Step 4|| Modify the Network Adapter to use the VMXNET 3 Adapter type.|
For information about modifying the Network Adapter to meet the requirements of this release, see the Readme file for the OVA template.
|Step 5||Upgrade the software to the latest version.|
|Step 6||Shut down the virtual machine.|
|Step 7||Power on the virtual machine.|
But I think that there is mistake in that guide. I cannot change any parameter until I shutdown the vm.
That's interesting, 9.x does say it has to be AFTER
|Step 1||Upgrade Unified Communications Manager on the virtual machine to the latest release.|
For information about installing or upgrading Unified Communications Manager on virtual servers, see Cisco Unified Communications Manager on Virtualized Servers here: http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_installation_guides_list.html.
|Step 2||After you finish the upgrade, shut down the virtual machine.|
|Step 3||Change the Guest Operating System to Red Hat Enterprise Linux 5 (32-bit).|
|Step 4||Check the RAM on the virtual machine and make sure that it meets the minimum RAM requirements for this release.|
See the readme file that accompanied the OVA file for this release for minimum RAM requirements at: Products\Voice and Unified Communications\IP Telephony\Call Control\Cisco Unified Communications Manager (CallManager)\Cisco Unified Communications Manager Version [Release]\Unified Communications Manager Virtual Machine Templates.
|Step 5||Save changes.|
|Step 6||Restart the virtual machine.|
I change the VM specs (RAM/CPU) BEFORE, to avoid troubles during the HW validation.
The guest OS always AFTER, as well as the new settings for the vNIC
You're probably already done, but for what it's worth to anyone else who finds this post:
I only followed the CUCM v10 upgrade guide and changed ALL the settings (in our specific case Guest OS version, disk size and vNIC) up-front, going direct from v8.6.2 to v10. I had no issues. For our Unity Connection cluster, those docs listed all the changes to be made after upgrade. I did them all (Guest OS, and vNIC) after the Unity (same v8.6.2 to v10) upgrade completed and it also went fine.
My fault I read that completely wrong, I was under the assumption that you wanted to apply brand new ova templates and not modify the existing. Apologies.
No, that's wrong.
You can resize your VMs as long as the specs are the same of a supported OVA
The CPU/RAM requirements of the VMs sometimes do differ between versions and you need to adjust that, it has to be BEFORE, otherwise, the upgrade will fail HW validation.