[cisco-voip] DMA 4.2 to 6.x staging !!!

Thu Apr 17 11:13:48 EDT 2008

OK, here is the email I got from TAC when it happened... no bug ID either:

This is [dome dude] with Cisco Systems and I will be handling your service
request # [tac case], I am sending this e-mail out as per our phone
conversation to give you information on how to contact me.

Unfortunately the CallManager hostname cannot be changed, and since the
Underscore is not a DNS supported character, it is needed to make a clean
installation and build up the configuration, next are two links that will
address your question, besides you will find a lot of information in regards
to underscore issues at the internet:

Cisco CallManager System Issues:
<http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/trouble/4_1_3/tb413ch4.h
tml>
Domain Name System (DNS)-supported characters include all letters (A-Z,
a-z), numbers (0-9), and hyphen (-), and any special characters are not
allowed.

Changing the IP Address for Cisco Unified CallManager / Unified
Communications Manager:
<http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/trouble/4_1_3/tb413ch4.h
tml>
Note: It is not supported to change the hostname on the Cisco CallManager
server because the Structured Query Language (SQL) database does not support
the hostname change. This is because SQL uses the server name for many of
the tables related to Cisco CallManager and exchanges this information as
such with the operating system. When SQL server is installed, it binds the
database to both the machine and Cisco CallManager server names. If this is
changed, the database does not replicate properly since the new Cisco
CallManager or machine name is not updated correctly by SQL. If a hostname
change is inevitable, then the entire Cisco CallManager must be rebuilt.

Please let me know any other question you may have or if the case can be
closed.

Great help, really.

Jonathan

On Thu, Apr 17, 2008 at 9:35 AM, Jonathan Charles <jonvoip at gmail.com> wrote:
> I would argue since the DMA is migrating from a Windows NETBIOS naming
>  convention to a Linux DNS convention, the DMA should have a function
>  to allow you to remove the evil underscore...
>
>
>
>  jonathan
>
>
>
>  On Thu, Apr 17, 2008 at 9:27 AM, Jonathan Charles <jonvoip at gmail.com> wrote:
>  > Gee, at least they weren't dicks about it...
>  >
>  >
>  >
>  >  Jonathan
>  >
>  >  On Thu, Apr 17, 2008 at 9:30 AM, Jason Aarons (US)
>  >
>  > <jason.aarons at us.didata.com> wrote:
>  >  >
>  >  >
>  >  >
>  >  >
>  >
>  >
>  > > I opened a tac case and was told it was by-design (my hostname started with
>  >  > a number which failed)  thus they wouldn't file a bug id even though the
>  >  > Help says any alphanumeric character is acceptable. They sent me a link to
>  >  > the original dns rfc.
>  >  >
>  >  >
>  >  >
>  >  >  ________________________________
>  >  >
>  >  >
>  >  > From: cisco-voip-bounces at puck.nether.net
>  >  > [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Voice Noob
>  >  >
>  >  >  Sent: Thursday, April 17, 2008 9:52 AM
>  >  >  To: Jonathan Charles
>  >  >
>  >  > Cc: cisco-voip at puck.nether.net
>  >  >  Subject: Re: [cisco-voip] DMA 4.2 to 6.x staging !!!
>  >  >
>  >  >
>  >  >
>  >  >
>  >  >
>  >  > Is this _ problem documented somewhere on Cisco.com? I find it hard to
>  >  > accept that you could not use an _ for the DMA export.
>  >  >
>  >  >
>  >  > On Thu, Apr 17, 2008 at 8:34 AM, Jonathan Charles <jonvoip at gmail.com> wrote:
>  >  >
>  >  > Please do not say that you had an underscore in your old hostname...
>  >  >
>  >  >  Because if you do, you cannot run DMA.
>  >  >
>  >  >  We ran into this a few months ago on a 4.1 - 6.0 upgrade and we ended
>  >  >  up having to export everything via BAT and reimporting... TAC said an
>  >  >  underscore means DMA cannot be used.
>  >  >
>  >  >
>  >  >
>  >  >  Jonathan
>  >  >
>  >  >
>  >  >
>  >  >
>  >  >
>  >  >
>  >  >  On Thu, Apr 17, 2008 at 7:51 AM, Djokic Sinisa <sdjokic at mds.rs> wrote:
>  >  >  >
>  >  >  >
>  >  >  >
>  >  >  >
>  >  >  > hi crew..
>  >  >  >
>  >  >  >
>  >  >  >
>  >  >  > i'm staging for migration from CCM 4.2 to UCCM 6.x cluster and i did DMA
>  >  >  > export..
>  >  >  >
>  >  >  > so during UCCM 6.0 install when it asked me for a hostname i tried to
>  >  > enter
>  >  >  > the old one but it didn't excepted it obviously the old hostname has
>  >  >  > underscores in it..
>  >  >  >
>  >  >  > it's like COMPANY_CCM_X..
>  >  >  >
>  >  >  > so i entered new one..
>  >  >  >
>  >  >  > is that going to cause problems?..beacuse of the DMA export fiule
>  >  > containg
>  >  >  > old hostname..IP address remained the same..
>  >  >  >
>  >  >  > i'm in the middle of it so i don't have any results yet..
>  >  >  >
>  >  >  > if it would cause problems what's the soluton..
>  >  >  >
>  >  >  > i do sincerely hope it;s not the fresh install..
>  >  >  >
>  >  >  >
>  >  >  >
>  >  >  >
>  >  >  >
>  >  >  > thanx..
>  >  >  >
>  >  >  >
>  >  >  >
>  >  >  > regards..
>  >  >  >
>  >  >  >
>  >  >  >
>  >  >  >
>  >  >  >
>  >  >  > Sinisa Djokic
>  >  >  >
>  >  >  > System Engineer
>  >  >  >  CCNP,CCDA,CQS-CWLDS,CS-CIPTDS,CS-CIPCCES Cisco Certified
>  >  >  >
>  >  >  >
>  >  >  >
>  >  >  >
>  >  >  >
>  >  >  >
>  >  >  >
>  >  >  >
>  >  >  > MDS Informaticki inzenjering
>  >  >  >  Bul. Arsenija Carnojevica 170
>  >  >  >  11070 Novi Beograd, Serbia
>  >  >  >  Tel: +381 11 2015 200, 2015 273
>  >  >  >  Fax: +381 11 3194 954
>  >  >  >  www.mds.rs
>  >  >  >  sdjokic at mds.rs
>  >  >  >
>  >  >  >
>  >  >
>  >  >
>  >  >
>  >  > > _______________________________________________
>  >  >  >  cisco-voip mailing list
>  >  >  >  cisco-voip at puck.nether.net
>  >  >  >  https://puck.nether.net/mailman/listinfo/cisco-voip
>  >  >  >
>  >  >  >
>  >  >  _______________________________________________
>  >  >  cisco-voip mailing list
>  >  >  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.
>  >
>