cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
236
Views
10
Helpful
8
Replies
Highlighted
Beginner

Adding a Subscriber- software version mismatch

Hello all,

 

I'm currently running a single server environment that has been upgraded to 11.5.1.17900-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?

 

Many thanks,

Rich A.

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

I would recommend to install the subscriber with the upgrade deployed during installation.
Please rate all useful posts

View solution in original post

8 REPLIES 8
Highlighted

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. 

https://www.youtube.com/watch?v=pfH1HzVYowE

++Please rate all useful posts and mark as answer if it solves your issue++
Make a bootable CUC image from a non bootable iso file , convert non-bootable iso image to bootable iso file . Download cisco cucm bootable iso file Download...
Highlighted

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:

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/install/11_5_1/cucm_b_installation-guide-cucm-imp-1151/cucm_b_installation-guide-cucm-imp-1151_chapter_0101.html#CUCM_TK_A063311C_00

 

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.

Highlighted

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. 

 

 

++Please rate all useful posts and mark as answer if it solves your issue++
Highlighted

I would recommend to install the subscriber with the upgrade deployed during installation.
Please rate all useful posts

View solution in original post

Highlighted

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.

Highlighted

Its better  ignore my reply. 

++Please rate all useful posts and mark as answer if it solves your issue++
Highlighted
Hall of Fame Cisco Employee

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.

HTH

java

if this helps, please rate
Highlighted

Thanks for the info regarding actions that void support. I'm glad we didn't go that route.