I'm currently running a single server environment that has been upgraded to 184.108.40.20600-52 (SU 7).
I'd like to add a Subscriber but .17900-52 is a non-bootable .iso meant only for upgrades. When we add the Subscriber using the latest bootable .iso (.12900) we get a version mismatch error and seem to be at an impasse. We cannot update the Subscriber to 17900-52 to get it on the same version as the Publisher.
What's the workaround for this?
Solved! Go to Solution.
Publisher and subscriber should be on same version.
if you have latest version of CUCM ISO, move the publisher to the version which you can and install the subscriber on same version .
if you have only non bootable version of the publisher version, you can make the non bootable to bootable. Video link mentioned below.
Note:- But this image will not be support on PCD as the HASH values get effected.
This is a very small environment and we don't use Prime Collaboration Deployment so hopefully the hashing wouldn't be an issue.
Doing a little more digging, there seems to be an option to upgrade the node during installation:
We'll try this first. If it doesn't work, we'll just upgrade the Publisher to a version with a bootable ISO first, then create the Subscriber, I guess.
You can upgrade the publisher to available bootable version and install the subscriber. or you can convert the non bootable to bootable on same version.
That's what we ended up doing. I should have read a little further in depth before posting my question.
Simply follow the installation guide. When the Wizard asks if you'd like to perform and upgrade during the installation process, answer "yes" and use the .iso file of the upgrade file.
You can reach out to your SE and ask for the bootable media, if you don't have a SE, you may also try TAC if the upgrade while install fails and ask for the bootable media.
FYI, the trick to turn a non-bootable to bootable media is NOT supported by Cisco, we can tell when you do that, and that voids support on the cluster.