CUCM DBReplication reset

When you reset dbreplication  you could check the status using 'utils dbreplication runtimestate'. you would be able to see number of of tables checked aganist the total of 706

Cluster Replication State: Replication status command started at: 2019-11-28-21-14

     Replication status command in PROGRESS. Checked 54 tables out of 706

     Last Completed Table: scratch

     No Errors or Mismatches found.

Cluster Replication State: Replication status command started at: 2019-11-28-21-14

     Replication status command in PROGRESS. Checked 118 tables out of 706

     Last Completed Table: functionrole

     No Errors or Mismatches found.

UC Data center movement

We had to shift our datacenter to another location. We had following components to shift from existing DC to new DC and business wanted to do it without any downtime and no additional cost apart from shipping the hardware.

UCS Servers
CUCM
CUC
UCCX
CUEAC
Expressway C and Expressway E
PLM

Following are the UCS and applications running on each UCS

ESXi01 C240 M4SX	ESXi02 C220-M3S	ESXi03 C220-M3S
EXPRESSWAYC01	EXPRESSWAYC02	UNITY CONNECTION 02
EXPRESSWAYE01	CUCMTFTP01	UCCX 02
CUCM01	EXPRESSWAYE02	CUCMSUB02
PLM01	CUCMSUB01
UNITY CONNECTION01	EXPRESSWAYC02
ATTENDANT CONSOLE1
UCCX01

We had multiple remote sites in the US region, so I have proposed to split it in two different DC's for geographical redundancy. We decided to ship ESXi01 initially and change the network to the new network. All the primary applications were running on ESXi01



Prerequisite


1- Update new IPs in DNS Records,

2- New TFTP IP address need to be updated on AD

3- You can clone Publishers and can use it in case any emergency. However Cisco does not support Cloning and Vmotion



This is what I did pre and post shipment of ESXI01


1- Communicated to local team that During the esxi01 movement activity, VOIP cluster would in READ ONLY mode and cannot make any changes

2- Mannual back up and total registered phone count taken. " Show Risdb query phone " would give you the total registered and unregistered details. Including firmware, phone type, IP address etc.

3- few screen shots from RTMT and CIMC console to make sure there are no major alarms

4- Before shipping changed the ESXi IP address

5-Shipped UCS device via overnight courier service

6-Connected UCS and changed CIMC ( CIMC only for UCS management, this won't impact anything)

7-started with CUCM Publiser IP change followed by Subs

8- CUCM DB didn't sync automatically so I did 'utils dbreplication reset all' then cluster REPLICATION SETUP changed to  (2) Setup Completed. Before it was showing  (3)DB Active-Dropped

9- Then CUC and PLM, CUEAC IP's changed with out issues

10- UCCX we could not change due to bug CSCve59850, I had to open a TAC case to fix this issue, TAC made changes in the root. however later changing IP address UCCX system -> server were showing as 'UNKNOWN", TAC again made changes in the intraclustercomm.ips

11- Expressway we didn't face any issues. Created a new DMZ setup and assigned new IPs and NAT IP. 

12- CUEAC  You need to change IP from Regedit and update it in TSP as well


License


We didn't changed the hostname and Domain name of servers. 


We had procured new license only for UCCX. 


CUC and CUCM license were on PLM and you don't require new license when you make network changes for CUC and CUCM


CUEAC -  Since this is running on windows license will not be void after changing IP


Major issue faced


1- Home office user's phone got unregistered, it was trying to communicate only Primary CUCM. I had created a new Device pool for home office phone and then added only active CUCM 

CCX Historical Datastore Replicate status shows UNKNOWN

I have changed UCCX IP Address to new IP, later when I tried to generate CCX reports I couldn't get any data in the report.  We have redundant UCCX nodes and the secondary node was not shown in HR Datastore. Following are the steps I followed to fix the issue

1

-

Go to 'Cisco Unified CCX Serviceability' -> Tools -> Datastore Control Center -> Replication Servers -> Related Links -> Click Go  -> from Data Datastore select "Cisco Unified CCX Historical Datastore"

I didn't see my secondary node and Replicate Status was showing as ' UNKNOWN'

2-  Click on Synchronize Data -> Now the data will be start sync, you could check the progress -> move your cursor towards Info and click on specs Icon

Once the data sync Job status would be shown as 'Completed'

If this didn't fix the issue, check utils uccx dbreplication status from CCX CLI and perform utils uccx dbreplication reset