cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2108
Views
5
Helpful
9
Replies

Replacing domain - Call manager cluster

Yanivaloosh
Level 1
Level 1

Hi 

anyone is familiar with procedure what us the procedure for replacing domain (from aaa.com to yyy.com)  for all ip telephony servers?

* Call Manager

* Unity Connection

* Cup

* Ccx 

* Edge

Thx. 

1 Accepted Solution

Accepted Solutions

Just to add to already excellent posts here, I had to do this recently in similar environment with many applications on version 11 and all (CUCM, IMP, UCXN, CER) worked well, however I ran into an issue with UCCX where the domain appeared to have changed, yet certificates were still reflecting old domain, attempting to delete and re-generate those would not work. After working with TAC for couple of days the case was escalated to developers and the culprit was that the platform.xml file on those servers did not get updated and required manual modification by TAC. I was told this should not be happening, and there is no bug created for this, so just something to watch out for.

View solution in original post

9 Replies 9

Rajan
VIP Alumni
VIP Alumni

You can refer the below procedure:

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/install/10_0_1/ipchange/CUCM_BK_C3782AAB_00_change-ipaddress-hostname-100/CUCM_BK_C3782AAB_00_change-ipaddress-hostname-100_chapter_0100.html#CUCM_CN_DBDE5307_00

HTH

Rajan

Hi,

you need to enter the command from CLI. the same requires reboot of server.

set network domain yyy.com

regds,

aman

Just to add to already excellent posts here, I had to do this recently in similar environment with many applications on version 11 and all (CUCM, IMP, UCXN, CER) worked well, however I ran into an issue with UCCX where the domain appeared to have changed, yet certificates were still reflecting old domain, attempting to delete and re-generate those would not work. After working with TAC for couple of days the case was escalated to developers and the culprit was that the platform.xml file on those servers did not get updated and required manual modification by TAC. I was told this should not be happening, and there is no bug created for this, so just something to watch out for.

Great info Chris!

Thanks a lot also because I will be involved in a similar change with same releases.

Thanks again

Cheers

Carlo

Please rate all helpful posts "The more you help the more you learn"

I'm running version  9.1.2.12031.

Servers full name will remain the same but will be connected to different global catalog.

In that case you are not changing domain on CUCM. Connecting to a different catalogue server is an AD integration. Just change the server your servers are pointing to from the web page and put in the correct port. The port for GC is 3268 while AD is 389

Please rate all useful posts

set network domain <Domain Name>

Example from lab:

admin:set network domain cisco.com
          ***   W A R N I N G   ***
Adding/deleting or changing domain name on this server will break
database replication. Once you have completed domain modification
on all systems that you intend to modify, please reboot all the
servers in the cluster. This will ensure that replication keeps
working correctly. After the servers have rebooted, please
confirm that there are no issues reported on the Cisco Unified
Reporting report for Database Replication.

The server will now be rebooted. Do you wish to continue.

Security Warning : This operation will regenerate
       all CUCM Certificates including any third party
       signed Certificates that have been uploaded.

Continue (y/n)?n
Command canceled

Note : This activity should strictly be done in maintenance window as it will restart the server automatically after executing the change. Also, the certificates will regenerate as the warning message states.

Regards

Deepak

Ayodeji Okanlawon
VIP Alumni
VIP Alumni

Please be aware that this is a massive change depending on what CUCM version you are running. If you are running CUCM 8.X and above then you need to carefully plan this as your cucm certificates will be regenerated once you change the host name on your cucm servers. This will happen when  you change the domain name.

You will need to plan this such that your phones can still trust the old TVS server that signed their ITL files. Please refer to the thread below for similar discussion..

https://supportforums.cisco.com/discussion/12734601/cluster-wide-tvs-regeneration

You will need to regenerate cucm certs (ie change the domain name on each server ) one by one. So just do one server first in the cucm group of the phones and then let the phones reboot. Ensure they all reboot.. Then once they are back. Do the rest 

Please rate all useful posts

Hi, 

+5 to my buddy Deji.

Also if you have a CUCM version 10.X and above and you have your cluster in mixed mode activate through new tokenless feature, remember that you have also to update CTL file on all server in your cluster through cli command  "utils ctl update CTLFile" so that phone can authenticate newly created Server certificates.

My 2 cents..

Carlo

Please rate all helpful posts "The more you help the more you learn"