Cisco's 6.0 high-CPU technote advises that when IOWait is high and the CallManager service trace is set to Detailed, the trace level be changed to Error.
Checked 2026-10-02
- Vendor
- Cisco
- Product
- Cisco Unified Communications Manager
- Subsystem
- trace configuration
- Deployment
- on-premises
- Region
- not restricted
- Release range
- 6.0 per source
- Checked
- 2026-10-02
Sources
- Monitoring and Troubleshooting Cisco Unified Communications Manager 6.0 High CPU, using Real Time Monitoring Tool (RTMT) — Cisco Systems (TAC) · tier 2 current vendor documentation · High IOWait troubleshooting steps
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting high CPU and service crashes in Unified CM: source note cucm-high-cpu-troubleshooting-v6-detailed-trace-to-error. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-high-cpu-troubleshooting-v6-detailed-trace-to-error
BibTeX
@misc{warmtransfer-claim-cucm-high-cpu-troubleshooting-v6-detailed-trace-to-error,
title = {Troubleshooting high CPU and service crashes in Unified CM: source note cucm-high-cpu-troubleshooting-v6-detailed-trace-to-error},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-high-cpu-troubleshooting-v6-detailed-trace-to-error},
note = {Source note cucm-high-cpu-troubleshooting-v6-detailed-trace-to-error, checked 2026-10-02}
}