<?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: Cisco IPS 4255 Sensor High CPU Utilization in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/cisco-ips-4255-sensor-high-cpu-utilization/m-p/1482146#M67498</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Halijenn,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the response.&amp;nbsp; I have gone through this bugid but&amp;nbsp; think this is not related to high CPU Utilization and is related to some sensorApp SignatureDB refcount integrity problem.&lt;/P&gt;&lt;P&gt;Please correct me if I am wrong.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 04 May 2010 13:25:15 GMT</pubDate>
    <dc:creator>Manjunatha Jayaram</dc:creator>
    <dc:date>2010-05-04T13:25:15Z</dc:date>
    <item>
      <title>Cisco IPS 4255 Sensor High CPU Utilization</title>
      <link>https://community.cisco.com/t5/network-security/cisco-ips-4255-sensor-high-cpu-utilization/m-p/1482144#M67496</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are facing high cpu utilization issue in Cisco IPS 4255 running software&amp;nbsp; Version 7.0(1)E3. We have checked in show tech and found 80.4% CPU is consumed by sensorApp. Also we have found no packet drops on the IPS interfaces.&lt;/P&gt;&lt;P&gt;Does anyone having any idea about this issue, I am attaching Show Tech from the device for reference.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 11:58:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-ips-4255-sensor-high-cpu-utilization/m-p/1482144#M67496</guid>
      <dc:creator>Manjunatha Jayaram</dc:creator>
      <dc:date>2019-03-10T11:58:54Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco IPS 4255 Sensor High CPU Utilization</title>
      <link>https://community.cisco.com/t5/network-security/cisco-ips-4255-sensor-high-cpu-utilization/m-p/1482145#M67497</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Seems to match bugID: &lt;STRONG&gt;CSCta02342&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;amp;bugId=CSCta02342"&gt;http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;amp;bugId=CSCta02342&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 May 2010 09:40:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-ips-4255-sensor-high-cpu-utilization/m-p/1482145#M67497</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2010-05-04T09:40:28Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco IPS 4255 Sensor High CPU Utilization</title>
      <link>https://community.cisco.com/t5/network-security/cisco-ips-4255-sensor-high-cpu-utilization/m-p/1482146#M67498</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Halijenn,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the response.&amp;nbsp; I have gone through this bugid but&amp;nbsp; think this is not related to high CPU Utilization and is related to some sensorApp SignatureDB refcount integrity problem.&lt;/P&gt;&lt;P&gt;Please correct me if I am wrong.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 May 2010 13:25:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-ips-4255-sensor-high-cpu-utilization/m-p/1482146#M67498</guid>
      <dc:creator>Manjunatha Jayaram</dc:creator>
      <dc:date>2010-05-04T13:25:15Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco IPS 4255 Sensor High CPU Utilization</title>
      <link>https://community.cisco.com/t5/network-security/cisco-ips-4255-sensor-high-cpu-utilization/m-p/1482147#M67500</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Manohar;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &lt;SPAN style="font-size: 10pt;"&gt;The message you are seeing in the 'sh tech' output is likely releated to bug &lt;SPAN class="AppletStyleChild77"&gt;&lt;SPAN id="s_5_1_58_0"&gt;CSCta02342.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; In general, since the release of the E3 analysis engine, there is a different queue processing algorithm that is implemented to efficiently process packet queues on the sensor.&amp;nbsp; Simply monitoring CPU utilization is not effective since the sensor is now making more use of idle CPU time.&amp;nbsp; You should instead monitor the Inspection Load of the sensor to understand how busy the sensor is.&amp;nbsp; In your case, the load was:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Processing Load Percentage = 28&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; Also, as you are currently running IPS release 7.0(1)E3, you may want to consider upgrading to a release containing the E4 analysis engine as your sensor will no longer receive signature updates.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; For further investigation of any concerns, it would be a good idea to open a service request to receive direct TAC assistance.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Scott&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 May 2010 15:06:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-ips-4255-sensor-high-cpu-utilization/m-p/1482147#M67500</guid>
      <dc:creator>Scott Fringer</dc:creator>
      <dc:date>2010-05-04T15:06:14Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco IPS 4255 Sensor High CPU Utilization</title>
      <link>https://community.cisco.com/t5/network-security/cisco-ips-4255-sensor-high-cpu-utilization/m-p/1482148#M67503</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Scott,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for clarification.I have gone through this bugid and but found&amp;nbsp; no workaround for this bug. Also sensor load is varying between 30-50 .&lt;/P&gt;&lt;P&gt;Please find the attached snapshot taken from GUI of IPS and its showing 99% CPU load.&lt;/P&gt;&lt;P&gt;Please suggest a solution to overcome this issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 May 2010 06:09:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-ips-4255-sensor-high-cpu-utilization/m-p/1482148#M67503</guid>
      <dc:creator>Manjunatha Jayaram</dc:creator>
      <dc:date>2010-05-05T06:09:42Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco IPS 4255 Sensor High CPU Utilization</title>
      <link>https://community.cisco.com/t5/network-security/cisco-ips-4255-sensor-high-cpu-utilization/m-p/1482149#M67504</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Manohar;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; As I mentioned, the sole point of the CPU being at near 100% is not indicative of a problem with the sensor (as it is now expected with changes to the analysis engnie made with the E3 release).&amp;nbsp; Certainly since you indicated you are noting no packet loss, and the Inspection Load is fluctuating between 30 and 50, the sensor is functioning as expected.&amp;nbsp; From the release notes for the E3 engine:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P class="pBu1_Bullet1"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;The E3 signature engine&amp;nbsp; update contains changes from CSCsu77935 &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;A name="wp1236883"&gt;&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="pB2_Body2"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt; The resolution of this defect modified the idle time algorithm of the&amp;nbsp; sensor by applying additional CPU to polling of the NICs to decrease the&amp;nbsp; polling interval and reduce latency.&amp;nbsp; This results in the CPU usage&amp;nbsp; being reported higher than in previous releases, including using&amp;nbsp; external tools such as top and ps. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;A name="wp1236887"&gt;&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="pB2_Body2"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt; You can notice this additional CPU load on single-CPU platforms, as well&amp;nbsp; as the primary CPU of multi-core systems. Since the additional CPU load&amp;nbsp; that is reported while polling is actually available to process&amp;nbsp; packets, and reduces as inspection load goes up, it does not negatively&amp;nbsp; affect the overall throughput of the IPS. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;A name="wp1236894"&gt;&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="pB2_Body2"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt; The best indication of sensor load is shown under the Processing Load&amp;nbsp; Percentage section in the &lt;SPAN class="cBold"&gt;"show statistics&amp;nbsp; virtual-sensor"&lt;/SPAN&gt; command output and on the IME Home Page.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="pB2_Body2"&gt;&lt;/P&gt;&lt;P class="pB2_Body2"&gt;&amp;nbsp; If you still feel there is a problem with your sensor, I would recommend opening a service request with TAC so further troubleshooting may be performed.&lt;/P&gt;&lt;P class="pB2_Body2"&gt;&lt;/P&gt;&lt;P class="pB2_Body2"&gt;Scott&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 May 2010 10:43:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-ips-4255-sensor-high-cpu-utilization/m-p/1482149#M67504</guid>
      <dc:creator>Scott Fringer</dc:creator>
      <dc:date>2010-05-05T10:43:29Z</dc:date>
    </item>
    <item>
      <title>Cisco IPS 4255 Sensor High CPU Utilization</title>
      <link>https://community.cisco.com/t5/network-security/cisco-ips-4255-sensor-high-cpu-utilization/m-p/1482150#M67505</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also facing the same issue where my IPS cpu utilization heat up to 85% and sometimes goes over 95% especially during the peak hour. the IPS already upgraded to software version &lt;SPAN style="font-size: 10pt;"&gt;7.0(4)E4. Is it any issue if we are running the IPS on this software version? &lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Sep 2013 09:03:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-ips-4255-sensor-high-cpu-utilization/m-p/1482150#M67505</guid>
      <dc:creator>iswady kamas</dc:creator>
      <dc:date>2013-09-20T09:03:46Z</dc:date>
    </item>
    <item>
      <title>Cisco IPS 4255 Sensor High CPU Utilization</title>
      <link>https://community.cisco.com/t5/network-security/cisco-ips-4255-sensor-high-cpu-utilization/m-p/1482151#M67507</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;The high consumption of CPU is not of concern, since there is no drop packets.&lt;/P&gt;&lt;P&gt;I had the same problem after performing POC Cisco, we conclude that the high CPU consumption that relate to using this topology.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In my case several vlan ID used to separate traffic.&lt;/P&gt;&lt;P&gt;You to be aware that the Inpesion load, but this will be the parameter performace IPS.&lt;/P&gt;&lt;P&gt;Always remember that you must leave the IPS sensor always updated with the licenses and packages.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Oct 2013 13:49:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-ips-4255-sensor-high-cpu-utilization/m-p/1482151#M67507</guid>
      <dc:creator>Rodolfo Navero</dc:creator>
      <dc:date>2013-10-03T13:49:35Z</dc:date>
    </item>
  </channel>
</rss>

