For root cause on a high CPU event that already happened, TAC asks for traces covering the period from before the problem began until after it went away.
Checked 2026-10-02
- Vendor
- Cisco
- Product
- Cisco Unified Communications Manager
- Subsystem
- TAC data collection
- Deployment
- on-premises
- Region
- not restricted
- Release range
- not stated; technote dated 2018
- Checked
- 2026-10-02
Sources
- Logs to be Collected for TAC when High CPU or Memory Issue is Noticed on CUCM — Cisco Systems (TAC) · tier 2 current vendor documentation · For RCA of an Event That Has Already Occurred
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting high CPU and service crashes in Unified CM: source note cucm-high-cpu-troubleshooting-tac-rca-time-window. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-high-cpu-troubleshooting-tac-rca-time-window
BibTeX
@misc{warmtransfer-claim-cucm-high-cpu-troubleshooting-tac-rca-time-window,
title = {Troubleshooting high CPU and service crashes in Unified CM: source note cucm-high-cpu-troubleshooting-tac-rca-time-window},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-high-cpu-troubleshooting-tac-rca-time-window},
note = {Source note cucm-high-cpu-troubleshooting-tac-rca-time-window, checked 2026-10-02}
}