CCIE Voice | Started Real War

Time 2021-06-08 20:15:51

Web Name: CCIE Voice | Started Real War

WebSite: http://rsccievoice.wordpress.com

ID:182037

Keywords:

Voice,CCIE,Started,

Description:

I completed a project for replacing 7 servers in a cluster including publisher recently. When I got this project, I dug a lot on Cisco.com, technical blogs, Google, even raised a case with Cisco tech to find the proper steps for replacing a server in CUCM cluster.“Replacing a server in CUCM cluster” approach is well documented in Cisco docs; I tested the same approach and faced DB replication issue.  The most confusing step was how  and when to restore the database backup (do we add the servers under CUCM for new publisher or should we restore the same without adding)? I opened a tech case with Cisco to find the actual solution with which I will not face any DB replication issue. However, I got the web link for same document which I already found.So I decided to test various methods, which I found on Google, Cisco docs. I tested for almost six weekends to find the proper solution, which doesn t cause any DB replication issue.After all my testing, I understood that I would face DB replication issue, so started searching for solution to resolve DB replication issue.In this blog entry, I am specifying the exact steps, which I performed while replacing six servers (one publisher, two TFTP servers, and 4 subscribers) in 16 servers CUCM (7.1.5) cluster:Before actual steps, let me share some guidelines, which we need to follow:During the actual migration of server, no administrative changes should be allowed.While replacing publisher, subscribers have to be online. I tried to build publisher in lab and putting the same in production cluster, but faced lot of issue (DB replication failed, and were not able to resolve).New servers Hardware compatibility check.Record all the existing configuration parameters of servers which you need to replace in cluster. I have prepared pre implementation check and post implementation check template for the process.Get all the existing license associated with MAC address of new CUCM publisher.Replacing a Publisher serverTake the back of database from publisher and store on SFTP server.Shutdown the existing publisher and connect the new servers.Fresh install the CUCM publisher software with the same configuration setting (existing publisher).Once installation is finished, configure DRS device in CUCM publisher and restore the database. Note, I did not add any sever under CUCM configuration before restoring the database. No need to restart any service before restoring the database.Upload the new license.Once restore is complete, restart the publisher.Once publisher is restarted, restart TFTP servers, and then active subscribers and then backup subscribers.After this step I faced DB replication issue what I expected, DB replication status come to 3(pub) and 4( for all other servers)I issued the following DB replication command to resolve the issue    Utils db replication stop all    Utils dbreplication dropadmindb – This command is used to drop the syscdr database. This clears out configuration information   from the syscdr database, which forces the replicator to reread the configuration files. (/etc/hosts). I checked before issuing DB replication command, /etc/hosts were not showing all the servers details. After issuing this command, “/etc/hosts” file was showing all the servers.    Utils db replication reset all, I waited for few hours and all servers were showing DB replication 2

TAGS:Voice CCIE Started 

<<< Thank you for your visit >>>

Started Real War

Hot Websites