Specifications

3-16
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
Chapter 3 Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
RTMT Monitoring of Cisco Unified CM System Health
• Buffers—amount of memory used for buffering purpose
• Cached—amount of cached memory
• Used—calculated as Total – Free – Buffers – Cached + Shared
• Total Swap—total amount of swap space
• Used Swap—the amount of swap space in use on the system.
• Free Swap—the amount of free swap space available on the system
Note Using SOAP APIs, you can query memory information for the following perfmon counters:
• Under Memory object—% Mem Used, % VM Used, Total Kbytes, Total Swap Kbytes, Total VM
Kbytes, Used Kbytes, Used Swap Kbytes, Used VM Kbytes
• Under Process object—VmSize, VmData, VmRSS, % Memory Usage
Using SNMP, you can query the following perfmon counters:
• Host Resource MIB—hrStorageSize, hrStorageUsed, hrStorageAllocationUnits, hrStorageDescr,
hrStorageType, hrMemorySize
Note You can download some historical information by using RTMT Trace Log Central. The Cisco AMC
Service PerfMonLog is enabled by default. Deprecated in Cisco Unified CM Release 6.0 because Cisco
RIS Data Collector PerfMonLog was introduced. The Cisco RIS Data Collector PerfMonLog disabled
by default in Cisco Unified CM Release 5.x and enabled by default in Cisco Unified CM Release 6.0.
Note Perfmon Virtual Memory refers to Total (Physical + Swap) memory whereas Host Resource MIB
Virtual Memory refers to Swap memory only.
The RTMT Process window displays process level memory usage information as follows:
• VmSize—Total virtual memory used by the process
• VmRSS—Resident Set currently in physical memory used by the process including Code, Data and
Stack
• VmData—Virtual memory usage of heap by the process
• Page Fault Count—Represents the number of major page faults that a process encountered that
required the data to be loaded into physical memory
Figure 3-5 shows RTMT Process window. You can sort VmSize by clicking on VmSize tab. Then you
can identify which process consumes more memory.