Cisco Cisco Unified IP Interactive Voice Response (IVR) 8.0(1) Administrator's Guide

Page of 448
 
8-37
Cisco Customer Response Solutions Administration Guide, Release 6.0(1)
 
Chapter 8      Managing the Cisco CRS System
CRS Services Trace File Configuration
Step 3
Click Update.
The system notifies all nodes in the cluster about the changes. 
Note
If Node Manager is not in Shutdown state during this operation, then the changes 
just made are synchronized on that node when Node manager is started again.
CRS Services Trace File Configuration
You can configure trace options for each CRS component. Tracing enables you to 
monitor CRS and subsystem activities across the cluster.
Note
If you activate tracing, monitor the CPU usage and available disk space on the 
server. CPU usage near 100% or a full disk can cause your system to shut down 
unexpectedly.
Access tracing configuration by choosing System > Tracing from the 
CRS Administration menu. 
The table below describes the Trace File Configuration fields.
Related Topics 
1.
RMI and RTP Port changes require restart of Cisco CRS Engine on all nodes in the cluster. A SQL TCP Port change requires 
restart of all Cisco CRS SQL services, on all nodes in the cluster.
Field Name
Description
File Name Prefix 
A prefix to be added to each trace file name.
File Extension
The extension to be added to the trace file name.
Number of Trace Files
The number of trace files to be retained by the system.
Trace File Size
The maximum file size for each trace file retained by the system.