Using the Cisco Unified Reporting Tool in CUCM 7.x to verify Replication Status
Posted by James on Thu 20 Aug 2009Categories: CCIE , Cisco , Cisco VOIP - [3] Comments
The Cisco Unified Reporting tool is a web application that can be accessed at the CUCM console and is a quick and convenient way to gather data about a CUCM cluster as well as information that may be helpful in troubleshooting.
The reporting tool can be accessed with an administrator account by doing any of the following:
1. In the Navigation menu of CUCM, Choose Cisco Unified Reporting.
2. From a browser, go to https://<ip address>/cucreports.
3. From the Real-Time Monitoring Tool (RTMT), choose File>Cisco Unified Reporting.
You are then sent to a new page, where on the left you can click “System Reports” to drop down a menu of several predefined reports.
To check the current status of database replication, do the following:
1. Select the report “Unified Database Status”.
2. If someone had previously run a report, you will see a link to the older report with a timestamp of when that report was generated. Click this link to view the older report, otherwise, select the Bar Graph icon in the top right of your screen to generate a new report. A progress bar will display while the new report is being generated.
3. Once the report has completed, review the following two sources to verify overall database health and ensure that replication is working:
a. Unified CM Database Access – For every server, shows if you can read from the local and publisher databases.
b. Unified CM Database Status – Shows if replication is good or bad.
The Cisco Unified Reporting Tool is a great tool that can be utilized to quickly gather important information about your CUCM cluster and I recommend checking it out.
James
August 26th, 2009 at 10:31 pm
Nice one…it would be a good idea to check replication via GUI at the very beginning of the lab!
thanks
August 28th, 2009 at 11:54 am
The Unified Database status can also be checked from the CUCM server command line with ‘show perf’ command below. You have to do it per server.
Replicate Count is not applicable. If the Replicate_State is 2, your replication is good.
This is the same info (see MAJOR disadvantage section below) as the Unified Reporting Database Status. Check the Database Status page and you’ll see a legend/explanation of the Replicate_State value.
admin: show perf query class “Number of Replicates Created and State of Replication”
==>query class :
– Perf class (Number of Replicates Created and State of Replication) has instances and values:
ReplicateCount -> Number of Replicates Created = 297
ReplicateCount -> Replicate_State = 2
There is a MAJOR disadvantage to the Unified Reporting Database Status page. The page does not automatically refresh every time you call up the page. You must manually upload the report if you want current information. Remember to upload the report every time you view a report, or you will be looking at the information from the last time you uploaded the report. And you may go months (years?) without uploading a report. I went a month trying to figure out what was wrong with a new subscriber because I didn’t upload a new repot & the report had old information in the Database Status report. New subscriber never showed as replicating.
September 7th, 2009 at 12:33 am
Can someone please confirm if “All servers have a replication count of 425″ means that the publisher and subscribers have got their database replicated 425 times?But I remember the field services team adding/deleting more than 1500 phones.Not all at once,but surely minor changes have been done more than 425 times.So during this time where did the changes got saved to before it got replicated?