[cisco-voip] FW: [RTMT-ALERT-StandAloneCluster] CallProcessingNodeCpuPegging

[Joe Pollere (AM)]

I ran into this when using the 2500 user 1CPU ova Template. It is related to the bug  CSCtn43135<http://cdets.cisco.com/apps/dumpcr?&content=summary&format=html&identifier=CSCtn43135>.

Below is the workaround that is associated with the bug:



Manually update service parameters:


Maintenance Throttling for Tables: change from 0 to 500ms


Maintenance Throttling for Stored Procedures: change from 0 to 1000ms


Regards,

Joe

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jason Aarons (AM)
Sent: Monday, June 11, 2012 5:27 AM
To: cisco-voip (cisco-voip at puck.nether.net)
Subject: [cisco-voip] FW: [RTMT-ALERT-StandAloneCluster] CallProcessingNodeCpuPegging

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/98e18e59/attachment.html>