[cisco-voip] FW: [RTMT-ALERT-StandAloneCluster] CallProcessingNodeCpuPegging
Jason Aarons (AM)
jason.aarons at dimensiondata.com
Mon Jun 11 05:26:39 EDT 2012
After upgrading to CallManager 8.5.1SU3, every night I get a RTMT alert regarding high cpu with %IOWait being the culprit. Never happens during day, just between midnight and 4am.
Any ideas?
Subject: [RTMT-ALERT-StandAloneCluster] CallProcessingNodeCpuPegging
Server CPU is Pegging over 90% Processor load over configured threshold for configured duration of time . Configured high threshold is 90 %
cmoninit (7 percent) uses most of the CPU.
Processor_Info:
For processor instance _Total: %CPU= 99, %User= 13, %System= 6, %Nice= 0, %Idle= 0, %IOWait= 81, %softirq= 0, %irq= 0.
For processor instance 0: %CPU= 99, %User= 13, %System= 6, %Nice= 0, %Idle= 0, %IOWait= 81, %softirq= 0, %irq= 0.
The alert is generated on Mon Jun 11 00:02:46 EDT 2012 on node 10.69.68.32
Memory_Info: %Mem Used= 66, %VM Used= 35.
Partition_Info:
Swap: %Disk Used=1.
Active: %Disk Used=81.
Common: %Disk Used=16.
Process_Info: processes with D-State: kjournald#1 cmoninit#6
itevomcid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120611/4917ed06/attachment.html>
More information about the cisco-voip
mailing list