Awesome thanks Justin, I never saw that. We'll probably do a test run-through in the lab just to be on the safe side.<br><br><div><span class="gmail_quote">On 5/10/07, <b class="gmail_sendername">Justin Steinberg</b> <
<a href="mailto:jsteinberg@gmail.com">jsteinberg@gmail.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;">I haven't tested this but I think it might work.
<br><br>The link below indicates that changing the hostname as part of the DMA<br>upgrade process from CM 4.x to CM 5.x is supported. If you don't want<br>to read the link, here is the important sentence.<br><br>"This feature allows you to import your
4.x data to a 5.1(1) server<br>without having to preserve the IP Address or Host Name. The IP Address<br>and/or Host name of the 5.1(1) server can differ from the 4.x<br>servername."<br><br><a href="http://www.cisco.com/en/US/partner/products/sw/voicesw/ps556/products_upgrade_guides09186a0080792e84.html#wp46919">
http://www.cisco.com/en/US/partner/products/sw/voicesw/ps556/products_upgrade_guides09186a0080792e84.html#wp46919</a><br><br>You would then use TFTP settings to control which callmanager phones<br>registered with.<br><br>
I'd open a TAC case to have them confirm this but this seems like a sane idea.<br><br>Justin<br><br>On 5/10/07, Matthew Saskin <<a href="mailto:matt@saskin.net">matt@saskin.net</a>> wrote:<br>> Ahh, I misunderstood and thought you were planning on upgrading the pub
<br>> from the existing cluster. I can't even guess how the name change idea<br>> would work out. Do you have a spare (off-network) server to test with?<br>> VM perhaps?<br>><br>> As for the multiple servers with the same hostname, that shouldn't cause
<br>> issues provided you're relying on local name resolution instead of DNS,<br>> but this is just a semi-educated guess :)<br>><br>> -matt<br>><br>> Ed Leatherman wrote:<br>> > My thought was to do an install on a new server for the
5.1 publisher<br>> > node w/new IP Address and restore the DMA data file onto that, thereby<br>> > not even touching the 4.1 publisher (other than running DMA). Would<br>> > also leave 1 subscriber node from the
4.1 cluster alone, and upgrade<br>> > the others and point them to the new 5.1 pub. Just not sure what would<br>> > happen having two clusters with publishers having the same host name<br>> > (maybe no problem?)
<br>> ><br>> > On 5/10/07, *Matthew Saskin* <<a href="mailto:matt@saskin.net">matt@saskin.net</a><br>> > <mailto:<a href="mailto:matt@saskin.net">matt@saskin.net</a>>> wrote:<br>> ><br>
> > How do you intend to create a publisher in the "old" cluster once you<br>> > split them?<br>> ><br>> > In theory the subscribers will keep chugging along with some end-user
<br>> > loss of features...well, and the lack of ability to make<br>> > configuration<br>> > changes.<br>> ><br>> > -matt<br>> ><br>> > Ed Leatherman wrote:<br>
> > > Related question, and I think the answer is also probably no but<br>> > want<br>> > > to verify...<br>> > ><br>> > > When upgrading from ccm 4.1 to 5, would it be possible to change
<br>> > the<br>> > > host name of the primary node in the 5.0 cluster after loading<br>> > the DMA<br>> > > data but prior to adding any subscriber nodes?<br>> > >
<br>> > > Trying to come up with a way to upgrade our system to 5 but leave 2<br>> > > nodes in the old cluster active to operate the call center users and<br>> > > IPCCX - or at least determine if its feasible. so basically to split
<br>> > > the cluster up.<br>> > ><br>> > > On 5/10/07, *Ahmed Elnagar* < <a href="mailto:aelnagar@act-eg.com">aelnagar@act-eg.com</a><br>> > <mailto:<a href="mailto:aelnagar@act-eg.com">
aelnagar@act-eg.com</a>><br>> > > <mailto:<a href="mailto:aelnagar@act-eg.com">aelnagar@act-eg.com</a> <mailto:<a href="mailto:aelnagar@act-eg.com">aelnagar@act-eg.com</a>>>> wrote:<br>> > >
<br>> > > dont even try it you will break your CM replication and will go<br>> > > through alot of very strange problems.<br>> > ><br>> > > Thanks and Best Regards
<br>> > > *<br>> > > Ahmed A. Elnagar<br>> > > *Network Field Engineer<br>> > ><br>> > > Advanced Computer Technology (ACT)<br>> > > 16 Fawzy Ramah
St.Off Shehab St.Mohandessin, Giza, Egypt<br>> > > Postal Code:12411 Cairo Egypt<br>> > ><br>> > > *Mob** :* +2010-2833868<br>> > > *Website**: * <a href="http://www.act-eg.com">
www.act-eg.com</a> <<a href="http://www.act-eg.com">http://www.act-eg.com</a>><br>> > <<a href="http://www.act-eg.com">http://www.act-eg.com</a>><br>> > > *E-mail**: * <a href="mailto:aelnagar@act-eg.com">
aelnagar@act-eg.com</a><br>> > <mailto:<a href="mailto:aelnagar@act-eg.com">aelnagar@act-eg.com</a>> <mailto:<a href="mailto:aelnagar@act-eg.com">aelnagar@act-eg.com</a><br>> > <mailto:<a href="mailto:aelnagar@act-eg.com">
aelnagar@act-eg.com</a>>><br>> > ><br>> > ><br>> > ------------------------------------------------------------------------<br>> > > *From:* <a href="mailto:cisco-voip-bounces@puck.nether.net">
cisco-voip-bounces@puck.nether.net</a><br>> > <mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>><br>> > > <mailto: <a href="mailto:cisco-voip-bounces@puck.nether.net">
cisco-voip-bounces@puck.nether.net</a><br>> > <mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>>> on behalf of Matt<br>> > > Slaga (US)<br>
> > > *Sent:* Wed 09-May-07 11:05 PM<br>> > > *To:* Ryan Ratliff; Jason Aarons (US)<br>> > ><br>> > > *Cc:* <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net
</a><br>> > <mailto:<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>> > <mailto:<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> > <mailto:
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>>><br>> > > *Subject:* Re: [cisco-voip] Changing 4.1(3) hostname article<br>> > on CCO?<br>> > ><br>> > > If the customer really pushes you, create a DNS C-name record.
<br>> > ><br>> > > -----Original Message-----<br>> > > From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>> > <mailto:
<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>><br>> > > <mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>
<br>> > <mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>>><br>> > > [mailto: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net
</a><br>> > <mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>>] On Behalf Of Ryan Ratliff<br>> > > Sent: Wednesday, May 09, 2007 3:58 PM<br>
> > > To: Jason Aarons (US)<br>> > > Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> > <mailto:<a href="mailto:cisco-voip@puck.nether.net">
cisco-voip@puck.nether.net</a>><br>> > <mailto:<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> > <mailto:<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net
</a>>><br>> > > Subject: Re: [cisco-voip] Changing 4.1(3) hostname article<br>> > on CCO?<br>> > ><br>> > > No way, no how.<br>> > ><br>> > > The only time you can change the hostname of a CM server is
<br>> > before<br>> > > you install CallManager on it.<br>> > ><br>> > > -Ryan<br>> > ><br>> > > On May 9, 2007, at 3:51 PM, Jason Aarons ((US)) wrote:
<br>> > ><br>> > > I'm trying to find a reference about server hostname changes for<br>> > > production CallManager 4.1, I recall it's not advised but<br>> > can't find
<br>> > > a article on <a href="http://cisco.com">cisco.com</a> <<a href="http://cisco.com">http://cisco.com</a>> <<a href="http://cisco.com">http://cisco.com</a>><br>> > stating this -jason
<br>> > ><br>> > ><br>> > ><br>> > ><br>> > ><br>> > > Jason Aarons<br>> > ><br>> > > Consultant<br>> > >
<br>> > > <a href="http://www.dimensiondata.com/na">http://www.dimensiondata.com/na</a><br>> > <<a href="http://www.dimensiondata.com/na">http://www.dimensiondata.com/na</a>><br>> > >
<br>> > > 904-338-3245 cell<br>> > ><br>> > ><br>> > ><br>> > > For urgent issues notify your Project Manager, for 24x7 support<br>> > > contact the Dimension Data NOC at 800-974-6584.
<br>> > ><br>> > ><br>> > ><br>> > ><br>> > ><br>> > > Disclaimer: This e-mail communication and any attachments may<br>> > > contain
<br>> > > confidential and privileged information and is for use by the<br>> > > designated addressee(s) named above only. If you are not the<br>> > intended<br>> > > addressee, you are hereby notified that you have received this
<br>> > > communication in error and that any use or reproduction of this<br>> > > email<br>> > > or its contents is strictly prohibited and may be unlawful.<br>> > If you
<br>> > > have received this communication in error, please notify us<br>> > > immediately by replying to this message and deleting it from<br>> > your<br>> > > computer. Thank you.
<br>> > ><br>> > > _______________________________________________<br>> > > cisco-voip mailing list<br>> > > <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net
</a><br>> > <mailto:<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>> > <mailto:<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> > <mailto:
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>>><br>> > > <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip
</a><br>> > ><br>> > > _______________________________________________<br>> > > cisco-voip mailing list<br>> > > <a href="mailto:cisco-voip@puck.nether.net">
cisco-voip@puck.nether.net</a><br>> > <mailto:<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>> <mailto:<br>> > <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net
</a> <mailto:<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>>><br>> > > <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip
</a><br>> > > -----------------------------------------<br>> > > Disclaimer:<br>> > ><br>> > > This e-mail communication and any attachments may contain<br>> > > confidential and privileged information and is for use by the
<br>> > > designated addressee(s) named above only. If you are not the<br>> > > intended addressee, you are hereby notified that you have<br>> > received<br>> > > this communication in error and that any use or reproduction of
<br>> > > this email or its contents is strictly prohibited and may be<br>> > > unlawful. If you have received this communication in error,<br>> > please<br>> > > notify us immediately by replying to this message and
<br>> > deleting it<br>> > > from your computer. Thank you.<br>> > ><br>> > > _______________________________________________<br>> > > cisco-voip mailing list
<br>> > > <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> > <mailto:<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>> > <mailto:
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> > <mailto:<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>>><br>> > > <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">
https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>> > ><br>> > ><br>> > > _______________________________________________<br>> > > cisco-voip mailing list
<br>> > > <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> > <mailto:<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>> > <mailto:
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> > <mailto:<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>>><br>> > > <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">
https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>> > ><br>> > ><br>> > ><br>> > ><br>> > > --<br>> > > Ed Leatherman<br>> > > Senior Voice Engineer
<br>> > > West Virginia University<br>> > > Telecommunications and Network Operations<br>> > ><br>> > ------------------------------------------------------------------------
<br>> > ><br>> > > _______________________________________________<br>> > > cisco-voip mailing list<br>> > > <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net
</a> <mailto:<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>> > > <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip
</a><br>> > ><br>> ><br>> ><br>> > _______________________________________________<br>> > cisco-voip mailing list<br>> > <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net
</a> <mailto:<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>> > <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip
</a><br>> > <<a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>><br>> ><br>> ><br>> ><br>> ><br>> > --<br>> > Ed Leatherman
<br>> > Senior Voice Engineer<br>> > West Virginia University<br>> > Telecommunications and Network Operations<br>><br>><br>> _______________________________________________<br>> cisco-voip mailing list
<br>> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>><br>
</blockquote></div><br><br clear="all"><br>-- <br>Ed Leatherman<br>Senior Voice Engineer<br>West Virginia University<br>Telecommunications and Network Operations