Trace Configuration

Cisco CallManager Serviceability provides a web-based trace tool to assist the system administrator and support personnel in troubleshooting Cisco CallManager problems. Cisco CallManager Serviceability Trace provides three main functions:

Types of Traces

Traces for Cisco CallManager services can be based on debug levels, specific trace fields, and Cisco CallManager devices, such as phones or gateways. Two types of traces are available, SDI trace and SDL trace.

SDI traces are also known as Cisco CallManager trace log files. Every Cisco CallManager service includes a default trace log file. The system traces SDI information from the services and logs run-time events and traces to a log file. Programmers typically use SDI traces for development purposes.

SDL traces contain call-processing information from Cisco CallManager and Cisco CTIManager services. The system traces the SDL of the call and logs state transitions in a log file. This log information helps administrators to troubleshoot problems on the Cisco CallManager system.

Tip

In most cases, extensive SDL traces will be gathered only when Cisco TAC requests it. SDL traces track communication between the CallManagers, whereas SDI traces track internal CallManager processing.

Caution

Enabling traces decreases system performance; therefore, enable higher-level trace only for troubleshooting.

 

Trace Configuration and Analysis Overview

Figure 32-5 provides an overview of trace configuration and analysis options:

Figure 32-5. Trace Configuration and Analysis Overview

 

Trace Configuration

Cisco CallManager provides many services for tracing. You can enable tracing for each service individually for each server within the Cisco CallManager cluster. Perform these tasks in the Cisco CallManager Serviceability Trace Configuration window to configure custom settings for a trace:

Step 1.

In Cisco CallManager Serviceability, choose Trace > Configuration and choose the server where you want to configure the trace settings.

 

   

Step 2.

From the Configured Services list, choose the service to change the trace settings, as shown in Figure 32-6. The Trace Configuration window opens. Figure 32-7 displays a sample output of that window.

 

Figure 32-6. Selecting a Service to Trace

 

Figure 32-7. Trace Configuration

 

Step 3.

To enable traces for the specified service, check the Trace On check box.

 

Step 4.

Choose the desired debug level from the Debug Trace Level drop-down menu.

 

Step 5.

Choose the trace fields to include in the trace files. This additional information is different for each service.

 

You can set the path and filename for the trace file. To allow creation of more than one file, Cisco CallManager uses the entered filename and adds an eight-digit string, starting with 00000000, that is incremented with each new file.

Enabling Clusterwide Trace Settings

The Troubleshooting Trace Settings menu item is misleading. This menu item allows you to enable or disable troubleshooting traces on different servers throughout the cluster, as shown in Figure 32-8. This window is usually used for troubleshooting when more than one server needs to be monitored. Each service can be selected or deselected individually for each server.

Figure 32-8. Enabling Traces Clusterwide

Note

Servers 172.30.2.67 and 172.30.2.68 shown in Figure 32-8 are currently offline, which is why the Troubleshooting Trace Setting window shows their services as N/A.

Table 32-2 describes the logging of each service that can be turned on or off in the Troubleshooting Trace Setting window.

Table 32-2. Trace Settings for Multiple Servers

Service

Logging

Cisco CallManager

Logs Cisco CallManager signaling information to trace files

Cisco Call Detail Records (CDRs) Insert

Logs information about writing of CDRs

Cisco Certificate Authority Proxy Function (CAPF)

Logs information about issues of Cisco CAPF

Cisco CTIManager

Logs information about issues on CTIManager of the Cisco CallManager

Cisco CallManager

Logs Cisco CallManager signaling information to trace files

Cisco Certificate Trust List (CTL) Provider

Logs information about issues of Cisco CTL Provider

Cisco Database Layer Monitor

Logs information about database usage of Cisco CallManager

Cisco Extended Functions

Logs information about issues referring to any of the Cisco CallManager extended functions, such as Quality Report Tool (QRT)

Cisco CallManager Extension Mobility

Logs information about issues of the Cisco CallManager Extension Mobility service and Extension Mobility application

Cisco IP Manager Assistant (IPMA)

Logs information about issues and usage of Cisco IPMA functionality on Cisco CallManager

Cisco IP Voice Media Streaming Application

Logs information about issues of the Cisco IP Voice Media Streaming Application in conjunction with every involved device

Cisco Messaging Interface

Logs information about issues of Cisco Messaging Interface

Cisco Music on Hold (MoH) Audio Translator

Logs information about issues with MoH on Cisco CallManager

Cisco Real-Time Information Server (RIS) Data Collector

Logs information about issues involving collecting real-time information on Cisco CallManager

Cisco Telephony Call Dispatcher (TCD)

Logs information about issues with attendant consoles and pilot points on Cisco CallManager

Cisco TFTP

Logs information about issues with the TFTP server service of Cisco CallManager

Cisco WebDialer

Logs information about issues with the click-to-dial functionality on Cisco CallManager systems

Trace Analysis

Категории