[cisco-voip] Subscriber hardware replacement

[Ryan Ratliff]

You have to install the subscriber to the same version as the  
publisher, with IP connectivity to the subscriber.  Since you already  
have the media for 4.1(3) just upgrade everything normally except the  
one sub you are replacing.  Then build the new one using the same  
hostname as the old one, and install CM once the pub is done with the  
upgrade.

If you wish to add it with a new hostname, then your plan will work  
just fine.  If you re-use the original sub hostname then no config  
changes will be necessary.

-Ryan

On Jun 12, 2007, at 4:27 PM, keli at carocomp.ro wrote:

Yes, you can definitely do it, as long as you don't put the two
servers in the same network at the same time, both powered on :)

I'd have the subscriber installed with the new stuff already, then
simply replace the old server once the publisher is upgraded. Maybe
some forced synchronization of the DB will be needed, but I don't see
any major problems.

regards,
    Zoltan

Quoting Kris Seraphine <baryonyx5 at gmail.com>:

> I'm doing 4.02a to 4.13 upgrade tonight on a two-server cluster.   
> We will
> also be replacing the Subscriber with a new 7835.  My initial plan  
> was to:
>
> Upgrade the cluster normally
> Add the new server as a new subscriber
> Make the necessary changes in ccmadmin (modify the callmanager groups
> etc)
> Remove the old subscriber
>
> I'm wondering if there's a way to cut a few steps from the process.
>
> I'm looking at the 'Replacing Servers During the Upgrde' section of
> the 4.13upgrade document but it doesn't explain the procedure very
> well.
> It sounds like I might be able to give the new server the same  
> hostname/IP
> and install it into the cluster as a replacement.
>
> http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_1/ 
> install/upgrade/upg413/replace.htm#wp1040049
>
> Am I understanding this correctly?
>
> thanks
> -- 
> kris seraphine



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip