Cisco states that core dumps can be difficult to reproduce, so the associated log files should be collected when they occur and before they are overwritten.
Checked 2026-10-02
- Vendor
- Cisco
- Product
- Cisco Unified Communications Manager
- Subsystem
- core dumps
- Deployment
- on-premises
- Region
- not restricted
- Release range
- 15 and SUs as of 2026-10-02
- Checked
- 2026-10-02
Sources
- Cisco Unified Real-Time Monitoring Tool Administration Guide, Release 15 and SUs - Alerts — Cisco Systems · tier 2 current vendor documentation · Alerts chapter > Set up alerts for core dump and collect relevant logs (introduction)
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting high CPU and service crashes in Unified CM: source note cucm-high-cpu-troubleshooting-core-logs-overwrite-risk. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-high-cpu-troubleshooting-core-logs-overwrite-risk
BibTeX
@misc{warmtransfer-claim-cucm-high-cpu-troubleshooting-core-logs-overwrite-risk,
title = {Troubleshooting high CPU and service crashes in Unified CM: source note cucm-high-cpu-troubleshooting-core-logs-overwrite-risk},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-high-cpu-troubleshooting-core-logs-overwrite-risk},
note = {Source note cucm-high-cpu-troubleshooting-core-logs-overwrite-risk, checked 2026-10-02}
}