3-13
Cisco Unified Communications Manager Managed Services Guide
OL-22523-01
Chapter 3 Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
RTMT Monitoring of Cisco Unified CM System Health
The RTMT backend, AMC service, which is up and running as soon as the Cisco Unified CM server is
up and running, collects and processes all the information needed, and notifies you according to how you
configured the notification.
RTMT CPU and memory page reports CPU usage in terms of the following:
• %System—CPU utilization percentage that occurred while executing at the system level (kernel)
• %User—CPU utilization percentage that occurred while executing at the user level (application).
• %IOWait—CPU percentage of time of idle waiting for outstanding disk I/O request.
• %SoftIrq—Percentage of time that the processor is executing deferred IRQ processing (for example,
processing of network packets).
• %Irq—Percentage of time that the processor is executing the interrupt request which is assigned to
devices for interrupt or sending a signal to the computer when it is finished processing.
CPU Usage
High CPU utilization can impact the call processing by creating delays or interruptions in the service. It
could affect the end user service. Sometimes high CPU utilization is indicative of a memory leak. RIS
DataCollector PerfMonLog when enabled tracks CPU usage.
Note Cisco recommends that RIS DataCollector PerfMonLog be enabled.
Table 3-2 shows CPU usage guidelines.
You can also monitor CPU usage by using APIs. Using the SOAP API, you can monitor the following
perfmon counters:
• Under Processor object—% CPU Time, System Percentage, User Percentage, IOwait Percentage,
Softirq Percentage, Irq Percentage
• Under Process object—% CPU Time
Using the SNMP interface, you can monitor the following perfmon counters:
• Host Resource MIB—hrProcessorLoad, hrSWRunPerfCPU
• CPQHOST-MIB—cpqHoCpuUtilMin, cpqHoCpuUtilFiveMin
Table 3-2 CPU Usage Guidelines
Usage MCS-7835 MCS-7845
Total CPU usage—Processor (_Total) \ %
CPU Time
< 68% is good
68–70% triggers a warning
> 80% is bad
< 68% is good
68–70% triggers a warning
> 80% is bad
Process ccm CPU < 44% < 22%
IOWAIT—Processor (_Total) \IOwait
Percentage
< 10% is good < 10% is good
CallManager Service Virtual Memory size < 2.1 GB < 2.1 GB
To Next Page
Loading...
Need help?
General