Adding a Subscriber to a CCM 4.1(3) cluster

[mmelbourne]

We have a cluster of CCM 4.1(3)sr2 nodes (Publisher and single Subscriber). These were installed from CCM 4.1(2) media and were upgraded to 4.1(3), and then to 4.1(3)sr2. If I wish to add a subscriber I understand I need to install from 4.1(3) media directly, but is this sufficient, as the media will not be 4.1(3)sr2. Can an update to sr2 be done after the installation of the new subscriber given that the new server has been built using 4.1(3) media?

[gogasca]

I dont think that would work.

Youmay to uninstall SR2 in PUB and SUB, then join the new SUB.

After that upgrade the cluster starting iwth the Publisher.

[thisisshanky]

Matt,

Gonz is absolutely right. You cannot install 4.1.3 on your subscriber because the DB versions are different on the Publisher. Thanks to Cisco, SRs are uninstallable. You can

a. revert the Publisher back to 4.13,

b. install Subscriber with 4.13 and

c. then apply the SR on both servers.

HTH

Sankar.

[mmelbourne]

Thanks for that guys.

Are the database versions definitely not compatible between, say 4.1(3) and 4.1(3)sr2? I can see that they may not be compatible between 4.1(2) and 4.1(3).

How can the cluster be reverted to 4.1(3) if the SRs cannot be uninstalled?

[mmelbourne]

I've just look in Add/Remove Programs and it shows an 4.1(3)sr2 uninstall option, so this would suggest SRs are uninstallable?

[mchandak]

I'm sorry, but I have to completely disagree with all the above posts. When you install a CallManager, it would only look for the base CM version and not the ES/SR. Even with SR2 installed on the box you will be able to install/add another subscriber as during the install, the subscriber would check for the CallManager version and when you are using th Media for 4.1(3), it would need the Publisher to be running 4.1(3) and not the SR/ES on it. You dont have to un-install the SR.

Also, yea all ES/SR can be un-installed.

[ecstillman]

I agree with the post above; however, as a way to settle the debate, perhaps mmelbourne can run dbhelper.exe after installing the new subscriber on 4.1(3) - if replication is created successfully with the new box then I see no problem with an upgrade to sr2. Of course, do not place the new subscriber into the CCM group until after the upgrade.

-Erik

[johnnylingo]

As luck would have it, I had a subscriber that failed to upgrade from 4.1(3)sr3a to sr4b last week, and have decided to completely rebuild it with the Publisher remaining at 4.1(3)sr4b.

If I encounter any problems I will post them here.

[johnnylingo]

Here is the installation guide chapter for bringing up a new sub:

http://www.cisco.com/en/US/customer/products/sw/voicesw/ps556/prod_installation_guide09186a00803f5c57.html#wp534948

[ecstillman]

Steps 4 and 5 are pretty clear in answering this post. Have you completed the re-build, johnnylingo, and how did it go?

-Erik

[miket]

I just added a new subscriber to a cluster that was installed at 4.1.3 then the sr added later.

I loaded the 4.13 base code then the sr and all is fine.

It does complain when the sub is at 4.1.3 untill you get the sr on then all is okay.

You will be fine.

[Ahmed Elnagar]

But what if you want to install sub with a Pub 4.1(3) while you have the media of 4.1(2)

I am facing the same problem but with 4.3, my Pub was 4.3(1) and I downloaded updates for it and now it is 4.3(2); I need to add a subscriber to the cluster but the media I have is 4.3(1) and when I try to install I get

The Cisco CallManager version that you are installing on this subscriber does not match the version running on the publisher database server.

Ensure the publisher is upgraded to this Cisco CallManager version before you continue.

Any ideas or workarounds!!!