Upgrade to CUCM 8.6 and upgrade to cucm 10.6

[aalejo]

When doing upgrade to 8.6 it is not possible to rollback, explanation was that base OS was different (different version)  and need a clean install.

When doing upgrade to 10.5 (from 8.6 for example), there is also another OS (different version and even 64 bits) but is possible to roll back.

Any ideas why?

Thanks

Alex

[Wilson Samuel]

Not sure if it does address your issue exactly but I was wondering that, If you are on UCS with Virtualized environment, then rolling back is easy. Just create a new VM, with the existing 8.6 server, do a DR Restore and upgrade that to 10.5, if something goes wrong, you have the existing 8.6 in another VM

HTH

[aalejo]

Hi Wilson

Yes, I know that path is possible and is usually the one I take.

My question is more like:  why is refresh to CUCM 8.6 can not be rolled back because of OS change (as Cisco said) and refresh to CUCM 10.6 from 8.6 CAN be rolled back when also OS was change (version and bits).

- Alex

[Wilson Samuel]

The only reason I believe is because of the Dynamic Disk allocation COP file, that most likely re-writes the Partition-B (and increases the disk size) effectively making Roll Back impossible.

http://www.cisco.com/web/software/282204704/18582/ciscocm.vmware_disk_size_reallocation_v1.0.pdf

But, let me check it, if that is indeed the case, I will install an 8.5.0 and upgrade to 8.5.1 n then upgrade it to 8.6.0 to test my theory :-)

Will confirm it once I have the test results..

The VM Dynamic Disc allocation COP file is not required for 10.x hence you can always roll back :-)

Again, this is my theory, I will confirm it, however if anyone else knows it before hand, please englighten us all :-)

HTH

[aalejo]

Hi Wilson

 You don't need to install that file (ciscocm.vmware-disk-size-reallocation-1.0.cop.sgn) to upgrade to 8.6. That cop is specifically to address space changes requirements an is also needed on CUCM 9.1.

The cop that you need to install is ciscocm.refresh_upgrade_v1.0.cop.sgn to upgrade to 8.6.

Reading again the release notes for ciscocm.refresh_upgrade_v1.0.cop.sgn I found the answer:  On CUCM 8.6, Cisco changed the installation procedure of CUCM allowing installing of two version with mismatching  OS on the same server.

- Alex