Great, <br><br>It sounds like I can simplify the process quite a bit by using the same hostname/IP on the new server.<br><br><br>Thanks for the quick replies.<br><br><br><div><span class="gmail_quote">On 6/12/07, <b class="gmail_sendername">
Ryan Ratliff</b> <<a href="mailto:rratliff@cisco.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">rratliff@cisco.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
You have to install the subscriber to the same version as the<br>publisher, with IP connectivity to the subscriber. Since you already<br>have the media for 4.1(3) just upgrade everything normally except the<br>one sub you are replacing. Then build the new one using the same
<br>hostname as the old one, and install CM once the pub is done with the<br>upgrade.<br><br>If you wish to add it with a new hostname, then your plan will work<br>just fine. If you re-use the original sub hostname then no config
<br>changes will be necessary.<br><br>-Ryan<br><br>On Jun 12, 2007, at 4:27 PM, <a href="mailto:keli@carocomp.ro" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">keli@carocomp.ro</a> wrote:<br><br>
Yes, you can definitely do it, as long as you don't put the two<br>servers in the same network at the same time, both powered on :)
<br><br>I'd have the subscriber installed with the new stuff already, then<br>simply replace the old server once the publisher is upgraded. Maybe<br>some forced synchronization of the DB will be needed, but I don't see
<br>any major problems.<br><br>regards,<br> Zoltan<br><br>Quoting Kris Seraphine <<a href="mailto:baryonyx5@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">baryonyx5@gmail.com</a>>:
<br><br>> I'm doing 4.02a to 4.13 upgrade tonight on a two-server cluster.
<br>> We will<br>> also be replacing the Subscriber with a new 7835. My initial plan<br>> was to:<br>><br>> Upgrade the cluster normally<br>> Add the new server as a new subscriber<br>> Make the necessary changes in ccmadmin (modify the callmanager groups
<br>> etc)<br>> Remove the old subscriber<br>><br>> I'm wondering if there's a way to cut a few steps from the process.<br>><br>> I'm looking at the 'Replacing Servers During the Upgrde' section of
<br>> the 4.13upgrade document but it doesn't explain the procedure very<br>> well.<br>> It sounds like I might be able to give the new server the same<br>> hostname/IP<br>> and install it into the cluster as a replacement.
<br>><br>> <a href="http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_1/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_1/
</a><br>> install/upgrade/upg413/replace.htm#wp1040049<br>
><br>> Am I understanding this correctly?<br>><br>> thanks<br>> --<br>> kris seraphine<br><br><br><br>----------------------------------------------------------------<br>This message was sent using IMP, the Internet Messaging Program.
<br><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">cisco-voip@puck.nether.net
</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
https://puck.nether.net/mailman/listinfo/cisco-voip</a><br></blockquote></div><br><br clear="all"><br>-- <br>kris seraphine