<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>So these are in Service Parameters for CCM? Exactly where do you change these? CLI?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>It is VMWare ESXi 4.1Update2 with direct disks/storage. No NAS.SAN<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Divin John [mailto:dijohn@cisco.com] <br><b>Sent:</b> Monday, June 11, 2012 5:45 AM<br><b>To:</b> Jason Aarons (AM); cisco-voip (cisco-voip@puck.nether.net)<br><b>Subject:</b> Re: [cisco-voip] FW: [RTMT-ALERT-StandAloneCluster] CallProcessingNodeCpuPegging<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'>Try this.<o:p></o:p></span></p></div><div><pre style='white-space:-moz-pre-wrap;white-space:pre-wrap;white-space:-pre-wrap;white-space:-o-pre-wrap;word-wrap:break-word'><span style='font-size:9.0pt;color:black'>In order to flatten the midnight maintenance spike, we would like to change the default service parameters for DB throttling, specifically: Maintenance Throttling for Tables: change from 0 to 500ms Maintenance Throttling for Stored Procedures: change from 0 to 1000ms. These should be changed only on VMware-based systems on fresh installs. <o:p></o:p></span></pre><pre style='white-space:-moz-pre-wrap;white-space:pre-wrap;white-space:-pre-wrap;white-space:-o-pre-wrap;word-wrap:break-word'><span style='font-size:9.0pt;color:black'>This should help the spikes at midnight.<o:p></o:p></span></pre><pre style='white-space:-moz-pre-wrap;white-space:pre-wrap;white-space:-pre-wrap;white-space:-o-pre-wrap;word-wrap:break-word'><span style='font-size:9.0pt;color:black'><o:p> </o:p></span></pre><pre style='white-space:-moz-pre-wrap;white-space:pre-wrap;white-space:-pre-wrap;white-space:-o-pre-wrap;word-wrap:break-word'><span style='color:black'>Maintenance Throttling for Tables: <o:p></o:p></span></pre><pre><span style='color:black'><o:p> </o:p></span></pre><pre><span style='color:black'>This parameter determines the number of milliseconds of delay to insert in the daily Unified CM database maintenance job when Unified CM is performing maintenance on the table and index portion of the database.<o:p></o:p></span></pre><pre><span style='color:black'>Another service parameter, Maintenance Throttling for Stored Procedures, inserts a similar delay during the daily maintenance job. Use these throttling service parameters to decrease the I/O caused by daily database maintenance. Especially in VMware environments, the frequency of unthrottled database maintenance I/O operations can cause performance issues or problems accessing the attached network storage. For traditional Unified CM deployments, the default value is usually sufficient. In a VMware environment with 15,000 phones (for example), a<o:p></o:p></span></pre><pre><span style='color:black'>500 millisecond delay may help if you are experiencing spikes in I/O. A value greater than zero in this parameter will also slow L2 upgrades. <o:p></o:p></span></pre><pre><span style='color:black'><o:p> </o:p></span></pre><pre><span style='color:black'> This is a required field. <o:p></o:p></span></pre><pre><span style='color:black'> Default: 0 <o:p></o:p></span></pre><pre><span style='color:black'> Minimum: 0 <o:p></o:p></span></pre><pre><span style='color:black'> Maximum: 3000 <o:p></o:p></span></pre><pre><span style='color:black'> Unit: ms <o:p></o:p></span></pre><pre><span style='color:black'><o:p> </o:p></span></pre><pre><span style='color:black'>Maintenance Throttling for Stored Procedures: <o:p></o:p></span></pre><pre><span style='color:black'><o:p> </o:p></span></pre><pre><span style='color:black'>This parameter determines the number of milliseconds of delay to insert in the daily Unified CM database maintenance job when Unified CM is performing maintenance on the stored procedures portion of the database.<o:p></o:p></span></pre><pre><span style='color:black'>Another service parameter, Maintenance Throttling for Tables, inserts a similar delay during the daily maintenance job. Use these throttling service parameters to decrease the I/O caused by daily database maintenance. Especially in VMware environments, the frequency of unthrottled database maintenance I/O operations can cause performance issues or problems accessing the attached network storage. For traditional Unified CM deployments, the default value is usually sufficient. In a VMware environment with 15,000 phones (for example), a<o:p></o:p></span></pre><pre><span style='color:black'>1000 millisecond delay may help if you are experiencing spikes in I/O. A value greater than zero in this parameter will also slow L2 upgrades. <o:p></o:p></span></pre><pre><span style='color:black'><o:p> </o:p></span></pre><pre><span style='color:black'> This is a required field. <o:p></o:p></span></pre><pre><span style='color:black'> Default: 0 <o:p></o:p></span></pre><pre><span style='color:black'> Minimum: 0 <o:p></o:p></span></pre><pre><span style='color:black'> Maximum: 3000 <o:p></o:p></span></pre><pre><span style='color:black'> Unit: ms<o:p></o:p></span></pre><pre><span style='color:black'><o:p> </o:p></span></pre><pre><span style='color:black'>To verify this, change the database timer from 00:00 to something else, you would see a spike 1 or 2 minutes after that time.<o:p></o:p></span></pre><pre><span style='color:black'><o:p> </o:p></span></pre><pre><span style='color:black'>--Divin<o:p></o:p></span></pre><pre><span style='color:black'><o:p> </o:p></span></pre></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'>From: </span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'>"Jason Aarons (AM)" <<a href="mailto:jason.aarons@dimensiondata.com">jason.aarons@dimensiondata.com</a>><br><b>Date: </b>Monday 11 June 2012 2:56 PM<br><b>To: </b>"cisco-voip (<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>)" <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br><b>Subject: </b>[cisco-voip] FW: [RTMT-ALERT-StandAloneCluster] CallProcessingNodeCpuPegging<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div><div><div><p class=MsoNormal style='margin-bottom:12.0pt'><span style='color:#1F497D'>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.</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span style='color:#1F497D'>Any ideas?</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span style='color:black'><br><b>Subject:</b> <b>[RTMT-ALERT-StandAloneCluster] CallProcessingNodeCpuPegging</b><o:p></o:p></span></p><div><p class=MsoNormal><span style='color:black'>Server CPU is Pegging over 90% Processor load over configured threshold for configured duration of time . Configured high threshold is 90 % <br>cmoninit (7 percent) uses most of the CPU. <br><br>Processor_Info: <br><br>For processor instance _Total: %CPU= 99, %User= 13, %System= 6, %Nice= 0, %Idle= 0, %IOWait= 81, %softirq= 0, %irq= 0. <br><br>For processor instance 0: %CPU= 99, %User= 13, %System= 6, %Nice= 0, %Idle= 0, %IOWait= 81, %softirq= 0, %irq= 0. <br><br>The alert is generated on Mon Jun 11 00:02:46 EDT 2012 on node </span><span style='color:#1F497D'>10.69.68.32</span><span style='color:black'><br><br>Memory_Info: %Mem Used= 66, %VM Used= 35. <br><br>Partition_Info: <br>Swap: %Disk Used=1. <br>Active: %Disk Used=81. <br>Common: %Disk Used=16. <br><br>Process_Info: processes with D-State: kjournald#1 cmoninit#6<o:p></o:p></span></p></div><p class=MsoNormal><span style='color:black'><br><br></span><span style='color:white'>itevomcid</span><span style='color:black'> <o:p></o:p></span></p></div></div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'>_______________________________________________ cisco-voip mailing list <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a> <o:p></o:p></span></p></div></body></html>