CUCM 11.5.1 upgrade to 14.1SU3 preUpgrade Failed check 1.6

[Hermanus Janse van Vuuren]

Question to the community out there. (Anyone done this or came across this before?)

Running the preUpgrade cop file on my CUCM PUB still on 11.5 I get the following failure.

Question: It seems this is only if you go to version 15, a version 14SU3 should still be successful, HDD is 110GB already in size?

Best practice obviously would be to follow the suggestions below but just to get the system on a supported version again would a version 14SU3 upgrade work for now and then later plan a rebuild to accommodate a future version 15 upgrade? 

1.6 FAIL OS and Infrastructure Checks

FAIL: This server is using an older filesystem type (ext3).
To resolve the installation or upgrade failure, either
- backup-reinstall-restore your source release in a new virtual machine
with 110GB virtual hard disk, then direct upgrade to 15.
- Use a direct migration option to get to 15 (Refer the Upgrade and
Migration Guide for Cisco Unified Communications Manager and the IM and
Presence Service on Cisco.com).

FAIL: Source release only has swap space of 2 GB, which is not enough for
destination release 15.
To resolve the installation or upgrade failure, either
- backup-reinstall-restore your source release in a new virtual machine
with 110GB virtual hard disk, then direct upgrade to 15.
Note:Growing to 110GB in existing virtual machine will result in upgrade
failure to 15, use new virtual machine with 110GB.
- Use a direct migration option to get to 15 (Refer the Upgrade and
Migration Guide for Cisco Unified Communications Manager and the IM and
Presence Service on Cisco.com).

[Roger Kallberg · Accepted solution]

You can safely ignore these warnings as they are as you say for an upgrade to v15.

[Hermanus Janse van Vuuren]

will run an older pre-upgrade file today maybe and see what I get.

[Hermanus Janse van Vuuren]

same result on the pre-upgrade 0038 file as on the pre-upgrade 0043 file, all version 15 warnings.

[Jason@Logicalis]

I have a customer I need to upgrade from - 11.5(1) SU11 to v15 - and there is not a refresh/L2 path to get there. So the Data Migration or Data Export/Import method is the only method supported. I was like you, I thought as long as the Disk is 10GB it should be good. But more and more I am seeing the Data Export is really the sure fire way to upgrade to make sure everything is built / rebuilt correctly. The pre-check is still important to make sure everything else is ready for the Data Export.

[Roger Kallberg]

You’d need to go all the way back to a version of the pre check that predates any v15 checks if you don’t want to see warnings related to this. That said you can as I wrote safely disregard the warning as you’re updating to v14.

However at some point in time you’ll need to do a rebuild of your system to match the conditions of v15 so that you can upgrade to 15. We are currently in that process, although we’re currently on v14. Our plan is to create new VMs based on the v15 OVA, change the guest OS on the created VM to CentOS 7 (64-bit), then install the version of CM 14 we are currently using on the created VM and as a last step do a DRS restore of that one node and repeat the process again for all the other nodes. We know there are some other options at hand, although those are not something that we have used previously and are therefore not comfortable with.

[Hermanus Janse van Vuuren]

Just an FYI, I did a CUCM 11.5SU7 --> 14.0SU3 upgrade successfully in my lab even though I got the above fail message on the preUpgrade cop file. Then I went on and upgrade the same CUCM to the latest CM15SU successfully last night, no funnies no errors, only had to change the RAM from 8192Mb to 10Gb and change the VM OS from CentOS7 64bit to Linux other 4.x 64bit. Upgrade took a while but the switch version took like 5 - 8 minutes, granted the DB is basically empty only a couple of phones registered to it.