If CPU spikes happen at random times, Cisco advises gathering detailed CUCM traces and RisDC perfmon logs, plus logs for whichever process is using the most CPU.
Checked 2026-10-02
- Vendor
- Cisco
- Product
- Cisco Unified Communications Manager
- Subsystem
- RTMT alerts
- Deployment
- on-premises
- Region
- not restricted
- Release range
- not stated; technote dated 2018
- Checked
- 2026-10-02
Sources
- Real-Time Monitoring Tool Alerts — Cisco Systems (TAC) · tier 2 current vendor documentation · CpuPegging section
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting high CPU and service crashes in Unified CM: source note cucm-high-cpu-troubleshooting-cpupegging-random-collect. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-high-cpu-troubleshooting-cpupegging-random-collect
BibTeX
@misc{warmtransfer-claim-cucm-high-cpu-troubleshooting-cpupegging-random-collect,
title = {Troubleshooting high CPU and service crashes in Unified CM: source note cucm-high-cpu-troubleshooting-cpupegging-random-collect},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-high-cpu-troubleshooting-cpupegging-random-collect},
note = {Source note cucm-high-cpu-troubleshooting-cpupegging-random-collect, checked 2026-10-02}
}