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