CUCM Checking Replication Status

William Bell
Vice President, Solutions and Products

Back in my day …

The folks who worked with CUCM database replication issues remember the days when we were able to use SQL enterprise manager or the dblhelper application with its silly little smiley faces. I hated dblhelper but I missed it when trying to check database replication on 5.0 and 5.1 builds.

{readmore}On these builds, the only option was to do the following:

1. At the console or SSH terminal execute “utils dbreplication status” and let it run for a few minutes. Then use “file view activelog cm/trace/dbl/” and scroll through a ton of output to make sure all table counts across all CUCM nodes lined up. Yeah, fun.

2. Use RTMT (or a very long command on the console) to look at the Replicate_state performance counter to make sure the replicate state was a “2” for all devices. Not as bad but still tedious because you have to check each server (if using the SSH or console session) or load counters into RTMT from each server. From a time perspective, you might as well do both steps 1 and 2.

I found out recently from checking an image I have in the lab that CUCM 6.0 has the same “issues” as 5.0 and 5.1(2).

With 5.1(3), 6.1(x), and 7.x  we now have some better methods to get at this information by using Cisco Unified Reporting Tool. Since it is Unified it must be great. Anyway, I checked out the tool mainly because I wanted to see if my customer was hit by a cosmetic defect in the reporting tool (hmmm, not so great). The tool was not affected by the defect (Yay!) and I found that it provides detailed information quickly.

For those interested:

  1. Go to https://<yourpublishernode>/ccmadmin and logon
  2. From the Navigation drop down list, choose “Cisco Unified Reporting”
  3. You are sent to a new page, on the left click on “System Reports” to drop down the menu
  4. Select “Unified Database Status”
  5. If someone has ran a report in the past, you will see a link to the report in the main page. If you choose this link you will see an “older” report.  To generate a new report you must click on the bar graph icon in the top right of your screen. 
  6. When generating a new report, the main screen will show a progress bar
  7. After the report is completed you can view the following to get an idea on replication health:
    1. Unified CM Database Access
    2. Unified CM Database Status


For the folks who prefer to use RTMT, there is a Database summary tool that pretty much provides a single view of replication status.


Posted Jul 30, 2008, 10:36 PM by wjb

Leave a Reply