<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Unexpected CPU spikes and average on vSZ-H in SmartZone and Virtual SmartZone</title>
    <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/Unexpected-CPU-spikes-and-average-on-vSZ-H/m-p/35967#M2972</link>
    <description>After applying the 3.4.1 patch (coming from 3.2), the CPU has gone down averaging around 50%. The question still stands. There are 18 APs connected, 17 of which have been added to a zone and configured. This should still not raise the CPU from 11-16% to about 50% or higher on a 2 CPU with 14 GB machine.&lt;BR /&gt;&lt;BR /&gt;Any guesses what this is or any idea how to get into linux core so I can take a look at the underlying processes?</description>
    <pubDate>Fri, 17 Feb 2017 11:26:56 GMT</pubDate>
    <dc:creator>axel_robbe</dc:creator>
    <dc:date>2017-02-17T11:26:56Z</dc:date>
    <item>
      <title>Unexpected CPU spikes and average on vSZ-H</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/Unexpected-CPU-spikes-and-average-on-vSZ-H/m-p/35966#M2971</link>
      <description>Dear all,&lt;BR /&gt;Problem: Since yesterday afternoon, we've been getting a lot of monitoring alerts because of the CPU util of our vSZ. It's been peaking a lot around 100%, but also the average is way up whereas it used to be between 11 and 17%. The screenshots below are by the vSZ itself, then CPU SNMP stats in our monitoring system and the third one of our VmWare SNMP, which shows that the vSZ utilizes extra CPU cycles (over 100%) available to the vm.&lt;BR /&gt;&lt;BLOCKQUOTE&gt;&lt;B&gt;show cpuinfo&amp;nbsp;&lt;BR /&gt;&lt;/B&gt;&lt;B&gt;





p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Menlo; color: #000000; background-color: #ffffff}
span.s1 {font-variant-ligatures: no-common-ligatures}
span.Apple-tab-span {white-space:pre}&lt;BR /&gt;
&lt;/B&gt;&lt;B&gt;processor	: 0&lt;BR /&gt;&lt;/B&gt;&lt;B&gt;model name	: Intel(R) Xeon(R) CPU &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; X3430&amp;nbsp; @ 2.40GHz&lt;BR /&gt;&lt;/B&gt;&lt;B&gt;processor	: 1&lt;BR /&gt;&lt;/B&gt;&lt;B&gt;model name	: Intel(R) Xeon(R) CPU &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; X3430&amp;nbsp; @ 2.40GHz&lt;BR /&gt;&lt;/B&gt;&lt;B&gt;Cpu(s):&amp;nbsp; 7.8%us,&amp;nbsp; 3.6%sy,&amp;nbsp; 0.0%ni, 88.4%id,&amp;nbsp; 0.1%wa,&amp;nbsp; 0.0%hi,&amp;nbsp; 0.1%si,&amp;nbsp; 0.0%st&lt;/B&gt;&lt;/BLOCKQUOTE&gt;&lt;B&gt;
&lt;/B&gt;&lt;B&gt;
&lt;/B&gt;&lt;B&gt;
&lt;/B&gt;&lt;B&gt;
&lt;/B&gt;&lt;BR /&gt;Impact: slower response and a lot of alerting. Haven't noticed major performance hits in terms of managed wireless networks.&lt;BR /&gt;&lt;BR /&gt;What changed?: We've added two R500's for our lab set-up to do some testing with roaming over several different WAN connections.&lt;BR /&gt;AP's have all been provisioned and received the config. So I don't understand what the vSZ is still doing.&lt;BR /&gt;&lt;BR /&gt;Anyone got any idea where to start looking?&lt;BR /&gt;&lt;BR /&gt;Kind regards.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Image_ images_messages_5f91c3e7135b77e2478d78d2_ebc0882e1ce492fa846daad4f9b23737_RackMultipart201702151218242nm-b42c927f-b5ea-4c95-a4e3-b581a63cf8d6-1602936596.png1487164302"&gt;&lt;img src="https://community.ruckuswireless.com/t5/image/serverpage/image-id/853iE2BD852A2FAE482F/image-size/large?v=v2&amp;amp;px=999" role="button" title="Image_ images_messages_5f91c3e7135b77e2478d78d2_ebc0882e1ce492fa846daad4f9b23737_RackMultipart201702151218242nm-b42c927f-b5ea-4c95-a4e3-b581a63cf8d6-1602936596.png1487164302" alt="Image_ images_messages_5f91c3e7135b77e2478d78d2_ebc0882e1ce492fa846daad4f9b23737_RackMultipart201702151218242nm-b42c927f-b5ea-4c95-a4e3-b581a63cf8d6-1602936596.png1487164302" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Image_ images_messages_5f91c3e7135b77e2478d78d2_7b57134f61a306f6ecd3070302fc8e7e_RackMultipart20170215482708mo6-552faa51-8100-4576-bb10-1449cce6fddf-1463037882.png1487164320"&gt;&lt;img src="https://community.ruckuswireless.com/t5/image/serverpage/image-id/854i853C65F67E6E298D/image-size/large?v=v2&amp;amp;px=999" role="button" title="Image_ images_messages_5f91c3e7135b77e2478d78d2_7b57134f61a306f6ecd3070302fc8e7e_RackMultipart20170215482708mo6-552faa51-8100-4576-bb10-1449cce6fddf-1463037882.png1487164320" alt="Image_ images_messages_5f91c3e7135b77e2478d78d2_7b57134f61a306f6ecd3070302fc8e7e_RackMultipart20170215482708mo6-552faa51-8100-4576-bb10-1449cce6fddf-1463037882.png1487164320" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Image_ images_messages_5f91c3e7135b77e2478d78d2_7b5fdeeeaa07d0197792cc8c180615e8_RackMultipart2017021513112opv7-127f6d67-440a-43ff-b120-e6a64577ae94-435758221.png1487164340"&gt;&lt;img src="https://community.ruckuswireless.com/t5/image/serverpage/image-id/855i8FC45CDAFEC88A49/image-size/large?v=v2&amp;amp;px=999" role="button" title="Image_ images_messages_5f91c3e7135b77e2478d78d2_7b5fdeeeaa07d0197792cc8c180615e8_RackMultipart2017021513112opv7-127f6d67-440a-43ff-b120-e6a64577ae94-435758221.png1487164340" alt="Image_ images_messages_5f91c3e7135b77e2478d78d2_7b5fdeeeaa07d0197792cc8c180615e8_RackMultipart2017021513112opv7-127f6d67-440a-43ff-b120-e6a64577ae94-435758221.png1487164340" /&gt;&lt;/span&gt;</description>
      <pubDate>Wed, 15 Feb 2017 13:12:54 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/Unexpected-CPU-spikes-and-average-on-vSZ-H/m-p/35966#M2971</guid>
      <dc:creator>axel_robbe</dc:creator>
      <dc:date>2017-02-15T13:12:54Z</dc:date>
    </item>
    <item>
      <title>Re: Unexpected CPU spikes and average on vSZ-H</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/Unexpected-CPU-spikes-and-average-on-vSZ-H/m-p/35967#M2972</link>
      <description>After applying the 3.4.1 patch (coming from 3.2), the CPU has gone down averaging around 50%. The question still stands. There are 18 APs connected, 17 of which have been added to a zone and configured. This should still not raise the CPU from 11-16% to about 50% or higher on a 2 CPU with 14 GB machine.&lt;BR /&gt;&lt;BR /&gt;Any guesses what this is or any idea how to get into linux core so I can take a look at the underlying processes?</description>
      <pubDate>Fri, 17 Feb 2017 11:26:56 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/Unexpected-CPU-spikes-and-average-on-vSZ-H/m-p/35967#M2972</guid>
      <dc:creator>axel_robbe</dc:creator>
      <dc:date>2017-02-17T11:26:56Z</dc:date>
    </item>
  </channel>
</rss>

