| Step 1
| Configure the values of the TLC Throttling CPU Goal and TLC
Throttling IOWait Goal service parameters (Cisco RIS Data Collector service) by performing one of these steps:Cisco Unified Communications Manager Administration and Cisco Unified IM and Presense: Select and configure the
values of the TLC Throttling CPU Goal and TLC Throttling IOWait Goal service
parameters (Cisco RIS Data Collector service).
Cisco Unity Connection only: Select
in
Cisco Unity Connection Administration and configure the values of the TLC
Throttling CPU Goal and TLC Throttling IOWait Goal service parameters (Cisco
RIS Data Collector service).
|
| Step 2
| Configure the trace setting for the service for which you want to
collect traces. If you have clusters, you can configure trace for the service on one server
or on all servers in the cluster.
To configure trace settings, choose what information you
want to include in the trace log by choosing the debug level and trace fields.
If you want to run predetermined traces on services, set
troubleshooting trace for those services.
|
| Step 3
| Install the
Cisco Unified Real-Time Monitoring Tool on a local PC.
|
| Step 4
| If you want to generate an alarm when the specified search string
exists in a monitored trace file, enable the LogFileSearchStringFound alert in Unified
RTMT.
You can find the LogFileSearchStringFound alarm in the
LpmTctCatalog. (Select.
In the Find alarms where drop-down list box, choose the
System Alarm Catalog; in the Equals
drop-down list box, choose
LpmTctCatalog).
|
| Step 5
| If you want to automatically capture traces for alerts such as
CriticalServiceDownand CodeYellow, check the
Enable Trace Download check box in the Set
Alert/Properties dialog box for the specific alert in Unified RTMT; configure how often
that you want the download to occur.
|
| Step 6
| Collect the traces.
|
| Step 7
| View the log file in the appropriate viewer. |
| Step 8
| If you enabled troubleshooting trace, reset the trace settings
services, so the original settings are restored.
| Note
|
Leaving troubleshooting trace enabled for a long time increases
the size of the trace files and may affect the performance of the services.
|
|