The event viewer logs are comma separated values (csv) files that contain a collection of alarms and events that CUCM generates about the system and endpoints.
What is it helpful for?
These are helpful to troubleshoot a variety of issues on the system, like phones that un-registers, DB out of sync, phones on preservation mode, and many others.
RTMT Basic knowledge.
Linux Based CUCM
Collect the files
Step 1. Open RTMT and double click on Trace & Log Central
Step 2. Double click on Collect Files
Step 3. A window with multiple services opens, do not click on any, (unless something else was required by the TAC engineer), and click on the Next button.
Step 4. Once you are on the second set of services, scroll down until you see Event Viewer Application Log and Event Viewer System Log you usually want to enable the first checkbox to get the logs from all servers, then click the Next button.
Step 5. Click the Next button so you get the Collect File Options window, (you can see another set of services if you have IM&P servers on this cluster), on which you can select an specific time-range and date you want to collect the logs from, or you may select Relative Range and pick the last few minutes, hours, days, weeks or months.
If the TAC engineer was specific about the date and time-range, select that, if the TAC engineer was not specific about this, then get the last X number of days from which this start to happen or think on when you first notice the issue.
As a best practice click on the Browse button and select an easy-to-get destination, like your desktop, once you select this, create a folder to store the files in there, use a name that makes sense and reflects the type of data and date you are collecting the files for, like TAC-eventviewer-12-12-16, if you end up collecting multiple files it will be helpful and will also help the TAC engineer to get an idea of what is in that folder.
You want to get the files from the Active Partition unless you are investigating an issue on a previous CUCM version on your system.
Once you are done, click on Finish.
Step 6. When the RTMT finishes to collect the files on all servers you selected you should see a window like the following image.
Step 7. Zip the entire folder that you created to compress all the logs in a single file.
This tool asks you to log in with your cisco.com credentials and your case number, you can find your case number on the subject of the emails your TAC engineer has been sending you about your case.
Tip: Avoid using the file description field on the Case File Uploader tool, as there are limitations on that, as a best practice, send an email to your TAC engineer to let him/her know that the file has been uploaded, and include any relevant information on the email body like MACs and IPs of involved devices, time-range and date of the event, what the end-users are experiencing, etc.
We were in the process of upgrading PCCE from 11.6 to 12.0 and what we found during CUIC upgrade that it fails and when we checked in the replication , it says replication_not_setup on both cuic publisher and subscriber nodes.Please advice if anyone has o...
Hi thereI wrote a Webservice for my customer and a simple Webinterface. I added now a custom tab for it and it works fine internaly (and VPN). But over MRA it is not working: Jabber:Page failed to load.URL: http://xxx.contoso.int/index.htmlError...
When agents make manual outbound calls , the skill group is displayed as CUCM_PG_1.Cisco_Voice.defa in Livedata.Is there a way to change / mask the skill group to some other name so that supervisors can view in CUIC as manual outbound.
i receive the below message every days ,what is the meaning : Microphone Overloaded Error::State=unacknowledged;Component=........ ................ .......... ..........;Description=Microphone(s) overloaded. More Information: OverloadedMicrophone=2