Choose Action > New log settings and enter a name for the counter log.
Click Performance Object.
In Select Counters from List and Select Instances from List, choose the following counters and
% Processor Time/_Total
% Processor Time/ccm
% Processor Time/AudioTranslator
% Processor Time/Aupair
% Processor Time/CiscoMessagingI
% Processor Time/ctftp
% Processor Time/CTIManager
% Processor Time/DLLHOST
% Processor Time/sqlservr
% Processor Time/TcdSrv
% Processor Time/RisDC
% Processor Time/snmp
% Processor Time/CallBackService
% Processor Time/LogoutService
% Processor Time/InsertCDR
Click the General tab.
Enter the collection interval of 60 and for Units choose seconds, so the data is averaged and
collected over 60-second intervals.
Click the Schedule tab.
Choose the At option for Start log and enter the current time and date to enable the logging to continue after a reboot.
Click Save to save your settings, such as the objects that you chose.
This allows you to load the same data again, if necessary.
Note : The log files will expand in size. Manually purge the log files to maintain optimal disk
Performance Monitor can simultaneously collect data from multiple installed systems and store the information in a single log file. You can export the log file into a Tab Separated Value (TSV) file or a Comma Separated Value (CSV) file. View the TSV file or CSV file in a spreadsheet application. Note : You must enable Statistics in Cisco CallManager Administration for the Performance Monitor to collect data.
Cisco CallManager directly updates Microsoft Performance Monitor counters. The call perfmon counters as call-processing-related counters contain simple, useful counts such as number of registered phones, number of active calls, and number of available conference bridge resources. The following list identifies the Cisco CallManager performance counters:
Cisco MGCP Gateways
Cisco MOH Device
Cisco Analog Access
Cisco MGCP FXS Device
Cisco MGCP FXO Device
Cisco MGCP T1CAS Device
Cisco MGCP PRI Device
Customize Performance Monitor to view the Cisco CallManager-related parameters that you want to monitor by choosing the object, counter, and the instance.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...