CUCM Common Problems on UCS Platform: Core, High CPU - I/O, Hung State

Publisher

Cisco Systems

URL

https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/118702-technote-cucm-00.html

Published

2015-01-06

Updated

unknown

Accessed

2026-10-02

HTTP status

200

License

Cisco copyrighted documentation; no-redistribution; short excerpts and locators only

Source notes citing this source

• In the technote's I/O-wait scenario, the CCM core backtrace showed CallManager unable to process signals, which Cisco describes as possibly due to CPU or a blocked function. in context
• For I/O-wait investigations the technote enables File I/O Reporting with utils fior start and utils fior enable and collects results with file get activelog platform/io-stats. in context
• In Cisco's UCS common-problems technote, high CPU from I/O wait that restarted the CCM and CTI services was attributed to the UCS platform and its storage, and isolating it needed UCS logs. in context

Cite this source record

APA

WarmTransfer. (2015, January 6). CUCM Common Problems on UCS Platform: Core, High CPU - I/O, Hung State. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-technote-118702-ucs-core-cpu-hung

BibTeX

@misc{warmtransfer-cisco-technote-118702-ucs-core-cpu-hung,
  title  = {CUCM Common Problems on UCS Platform: Core, High CPU - I/O, Hung State},
  author = {{WarmTransfer}},
  year   = {2015},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-technote-118702-ucs-core-cpu-hung},
  note   = {Cisco Systems, accessed 2026-10-02}
}