The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Using Traces
Cisco Unity Connection Serviceability traces help troubleshoot problems in the following ways:
You can specify the log file parameters for each Unity Connection component, including the maximum number of log files and the maximum file size that can be created when you run traces for a component.
You can enable micro traces and the level of micro-trace information that you want.
You can enable macro traces (preselected groups of micro traces) and the level of macro-trace information that you want.
After you have configured the log files and enabled the traces, you collect trace log files in one of the following ways:
Using the trace and log central option in the Real-Time Monitoring Tool (RTMT). For information, see the “Working with Trace and Log Central” chapter (in the “Tools for Traces, Logs, and Plug-Ins” part) of the Cisco Unified Real-Time Monitoring Tool Administration Guide at http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
Using the command line interface (CLI). For information, see the Command Line Interface Reference Guide for Cisco Unified Communications Solutions at http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
Note | Enabling macro or micro traces decreases system performance. Enable traces only for troubleshooting purposes. |
Note | Before trace information can be written to the log files, you must enable micro traces or macro traces that provide the troubleshooting information in the areas that you select. |
In Cisco Unity Connection Serviceability, select . The Trace Configuration page appears.
In the Server drop-down box, select the applicable Unity Connection or Cisco Business Edition server, and select Go.
From the Component drop-down box, select the component for which you want to configure trace log files, and select Go.
The drop-down box displays all components (active and inactive).
In the Maximum No. of Files field, enter the maximum number of trace log files that is created for this component.
In the Maximum File Size field, enter the size limit (in megabytes) for the trace log files that is created for this component.
If you want to return to the default settlings, select Set Default. Otherwise, skip to the next step.
If you want the new trace log files to replace the old trace log files for this component, select Restart Log Files.
Enable micro traces when you are troubleshooting problems with specific Cisco Unity Connection components. For example, if the Alert Central tool in Real-Time Monitoring Tool (RTMT) has notification errors, enable the Notifier trace. However, keep in mind that running traces can affect system performance and hard-disk space.
Note | Enabling micro traces decreases system performance. Enable traces only for troubleshooting purposes. |
Step 1 | In Cisco Unity Connection Serviceability, select . | ||
Step 2 | In the Server drop-down box, select the applicable Unity Connection or Cisco Business Edition server, and select Go. | ||
Step 3 | From the Micro Trace drop-down box, select the micro trace that you want to enable, and select Go. | ||
Step 4 | Under Micro-Trace Levels, check the check boxes for the micro-trace levels that you want to enable. | ||
Step 5 | Select
Save.
|
The Table 3-1 lists each micro trace that is available, a description of what it analyzes, and the filename of the trace log that it generates.
Enable macro traces, which are preselected sets of micro traces, when you are troubleshooting general areas of Unity Connection functionality. For example, if there are MWI problems, enable the Traces for MWI Problems macro trace. However, keep in mind that running traces can affect system performance and hard-disk space.
Caution | Enabling macro traces decreases system performance. Enable traces only for troubleshooting purposes. |
Step 1 | In Cisco Unity Connection Serviceability, select . | ||
Step 2 | In the Server drop-down box, select the applicable Unity Connection or Cisco Business Edition server, and select Go. | ||
Step 3 | Check the check box of the macro trace that you want to enable. | ||
Step 4 | Expand the macro trace, and check the check boxes for the levels that you want to enable. | ||
Step 5 | Select
Save.
|
Table 2 lists each macro trace that is available, a description of what it analyzes, and the filename of the trace log that it generates.
Message handing; the objects that handle messages from delivery to deletion |
diag_MTA_*.uc diag_CuCsMgr_*.uc diag_CuImapSvr_*.uc diag_Tomcat_*.uc |
|
diag_CuNotifier_*.uc |
||
diag_CuNotifier_*.uc |
||
diag_CuNotifier_*.uc |
||
diag_CuMixer_*.uc |
||
The Text to Speech (TTS) feature; also can log traces on other Cisco Unity Connection components that interact with TTS |
||
The activity of Cisco Unity Connection ViewMail for Microsoft Outlook clients |
diag_CuImapSvr_*.uc diag_MTA_*.uc diag_Tomcat_*.uc |
|
<date in the format yyyy_mm_dd>.stderrout. log.* diag_CuMbxSync_*.uc |