05-22-2011 03:14 PM - edited 03-16-2019 05:04 AM
I am trying to setup/test a CUCM upgrade from version 6.1(5) to version 8.5(1) in a VMWare lab environment and have not been successful. Version 8.5(1) works just fine if installed from scratch as opposed to an upgrade to 6.1(5).
The upgrade process fails with the error:
Error encountered: errors.upgrade.HardwareUnsupported
And the log file shows:
05/22/2011 12:52:13 upgrade_manager.sh|Validate hardware for the upgrade|<LVL::Info>
05/22/2011 12:52:28 upgrade_manager.sh|File::0, Function: (), This hardware is no longer supported. Validation error on HSSI mode:
VMware Validation Failure:
Unable to validate VMware based server disk settings. Please check SCSI disks are at least 72 GB in size and are located at 0:0 (and 0:1 in a two disk config) in machine settings..|<LVL::Error>
I am wondering if it's even possible to do this since the 6.1(5) loads onto VMWare as unsupported. This scenario will only be used to test the process and will not go into production so I'm wondering if there is some work around. Or if I'm missing something and that the upgrade really should work.
Thanks in advance,
Glen
05-22-2011 08:25 PM
looks like it doesn't like 72GB vmdisks, it wants at least 80GB
05-23-2011 05:15 AM
Roman,
I apologize, but I should have provided more detail.
I have tried this with the same result on two separate VMs. One was manually created with 146 GB of disk space allocated. The other VM was created using the Cisco provided .ova file, which did allocate 80 GB of disk space. So I'm still leaning towards an issue with installing the non-supported 6.1 version on the VM first that sets something that causes the 8.5 upgrade to fail the hardware check.
Any ideas?
Thanks.....Glen
09-14-2011 10:13 AM
Did you find a resolution to this? I am trying to do the same thing and getting the same error.
Thanks.
09-14-2011 10:15 AM
05-03-2012 11:49 AM
Hey Glen,
I have a demo system I want to upgrade from 6.1.5 to 8.6 but during the upgrade I get the same error message as you. I've tried 6.1.5 to 7.1.5 as you suggested but I still get the same message. What were the exact versions of 6.1.5 & 7.1.5 you used? Was there any other trick?
Cheers,
Brian Webster
(949) 276-1750
05-24-2012 02:29 AM
I have the same issue..Did you find any solution?
Thanks
06-06-2012 04:43 AM
Sorry for the delay. I found that upgrading to version 7.1.5 first and then to 8.5 worked.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide