Hi there,
today I have a customer that wanted to upgrade from CUCM 9.1.2 to 10.5 – which sounds pretty easy… think again, so this is a BE6K deployment where CUCM instance was configured with the recommended OVA from CCO.
When starting the upgrade I found that the upgrade didn’t wanted to proceed as expected. and I was getting the following error:
Installation of UCSInstall_UCOS_10.5.1.10000-7.sgn.iso failed
An error has occured but no messages are available. This can happen when another administrator is working on the system at the same time and triggers an error.
So just curiosity I was looking for the error but no clue, so I decided to save the logs and found the following:
08/28/2014 23:09:13 refresh_upgrade|File:/common/download/10.5.1.10000-7/refresh_upgrade:641, Function: validate_free_space(), Not enough space on partition to proceed|
after looking for possible solutions I found a COP file called Free space, this COP file helps you clear all the information from the Common folder and the inactive partition where you might have an old version installed from previous upgrades (be careful if you use this you wont be able to go back to that version…IMO who would want to go back to that version in the first place??).
So that didn’t fix my issue… why would it? – Then I found another tool called:
UCM VM Dynamic Disk Size Reallocation COP File
http://software.cisco.com/download/release.html?mdfid=285963825&flowid=50402&softwareid=282204704&release=LCU&relind=AVAILABLE&rellifecycle=&reltype=latest
Which its name explains it all, use the Readme file if you want to know how to use it. to save you the trip to the ReadMe file here are the steps that you need to take:
1. (UCM 9.1 and earlier only) Install the “ciscocm.vmware-disk-size-reallocation-1.0.cop.sgn” COP file.
2. Shutdown guest VM
3. Open VMware Infrastructure (VI) Client and connect to VirtualCenter or the ESX host.
4. Right-click the virtual machine.
5. Click Edit Settings.
6. Select Virtual Disk.
7. Increase the size of the disk.
8. Power on guest VM.
The system will restart twice after you first turn it on (Very scary if you ask me!), because it need to recognize the new space and expand the system.
After this the upgrade proceeded very nicely.
I hope this information helps someone having the same issues!
Thank you!
About the Author:
Andres Sarmiento, CCIE # 53520 (Collaboration)
With more than 13 years of experience, Andres is specialized in the Unified Communications and Collaboration technologies. Consulted for several companies in South Florida, also Financial Institutions on behalf of Cisco Systems. Andres has been involved in high-profile implementations including Cisco technologies; such as Data Center, UC & Collaboration, Contact Center Express, Routing & Switching, Security and Hosted IPT Service provider infrastructures.
Looks like with v10.5, they removed that cop file. You can find the cop under v10.0. In the Upgrade Guide for 10.0 it talks about using the file if you don’t have 25GB free (pg31 Step 4).
That is correct, thank you for your input!
I’m curious to know what your disk expanded from and to? Looking at VM requirements, v9 and v10.X have the same value for vHDD space. Nowhere in the readme does it discuss what exactly it’s doing other than “Expanding the disk”.
I went from 80GB to 120GB
—
So the disk doesn’t expand by itself, what it does is that once you run the COP, and turn off the VM, you will edit the Disk on the VM under Edit Settings menu when you right click the VM instance.
Thank you!
Ahhh. The whole disk cleanup process seems a bit odd. They want 25GB free and want you to increase the disk size before running the disk cleanup (free common and manual tftp cleanup). I’d think doing opposite would make the most sense seeing that my install is about 350 phones and they recommend 80GB for 1000 phones.
You are right that would be the right thing to do.
I don’t want to say that they didn’t think it thru but definitely was something that looks like they missed.
I followed the process carefully, and ended up with a larger hard disk (went from 80Gb to 160Gb) but the partitions stayed the same (active/inactive/logging). What good is a larger hard disk if the partitions are not increased too? It’s not clear from the ReadMe exactly what the COP file does, but I believe it was supposed to expand the size of the partitions to fill the increased disk space, but in my case at least, it did not work.
Did you also ran the COP to clear space in the /Common folder? – if you are still having the issue post the upgrade log to see if the issue is different.
Hi Andres
I want to do the upgrade process from version 9.1 to 10.5, but from cisco site I did not found a manual procedure to it…
The documentation says that, we need install the Cisco Prime Collaboration Deployment to upgrade.
On the above post you do not says about it, so the Cisco Prime Collaboration Deployment is required to make the upgrade?
If not, could please share the procedure that you used for?
Hi there, I created a new post with information on how to do it the traditional way, http://collabengineer.com/2014/09/27/upgrade-cucm-9-1-to-10-5-procedure-no-prime-collaboration-deployment/
I hope it helps.
Thank you
for me it is not working i was trying to upgrade from 9.1.2 to 10.5 every time it was failing during “installation of database component” (showing 6 hr to install and failed in 3% )
then revert back to 9.1.2 version and if try to check the status by “utils system upgrade status ” is showed
“An error has occured but no messages are available. This can happen when another administrator is working on the system at the same time and triggers an error.”
for me it is not working i was trying to upgrade from 9.1.2 to 10.5 every time it was failing during “installation of database component” (showing 6 hr to install and failed in 3% )
then revert back to 9.1.2 version and if try to check the status by “utils system upgrade status ” is showed
“An error has occured but no messages are available. This can happen when another administrator is working on the system at the same time and triggers an error.”