<?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: cpu hog in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/cpu-hog/m-p/3924088#M11414</link>
    <description>&lt;P&gt;Were you able to find a resolution to this issue? Did you open a TAC case.&lt;/P&gt;</description>
    <pubDate>Fri, 13 Sep 2019 17:26:03 GMT</pubDate>
    <dc:creator>Alex Pfeil</dc:creator>
    <dc:date>2019-09-13T17:26:03Z</dc:date>
    <item>
      <title>cpu hog</title>
      <link>https://community.cisco.com/t5/network-security/cpu-hog/m-p/3843967#M11413</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I&amp;nbsp; am getting the below from the crash analysis&amp;nbsp; , I would like to know the crash might be due to the cpu hog ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;and What is that&amp;nbsp;&lt;SPAN class="ng-binding"&gt;Process: IKE Receiver&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class="vdw__msg-header panel panel--flat toggle"&gt;&lt;DIV class="flex"&gt;&lt;DIV class="vdw__msg-disclosure flex-fluid"&gt;&lt;SPAN class="vdw__msg-title ng-binding ng-scope"&gt;Long CPU hogs of 500ms or more occurred recently (within the last 5 minutes), which could contribute to high CPU usage, dropped packets and poor performance&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class="vdw__msg-body flex-fluid ng-scope"&gt;&lt;DIV class="text-mono vdw__msg-body-wrapper"&gt;&lt;P class="vdw__msg-content ng-binding"&gt;CPU hogs were detected where the most recent hog lasted longer than 500ms. This might cause jitter and drops on flows, voice quality problems and cause the interface overrun counter to increase. Open a case with the Cisco TAC to diagnose this problem further.&lt;/P&gt;&lt;DIV class="vdw__msg-snippet panel panel--flat ng-scope"&gt;&lt;DIV class="clearfix ng-scope"&gt;&lt;SPAN class="ng-binding"&gt;Process: IKE Receiver, PROC_PC_TOTAL: 1, MAXHOG: 1815, LASTHOG: 1815&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV class="clearfix ng-scope"&gt;&lt;SPAN class="ng-binding"&gt;...&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV class="clearfix ng-scope"&gt;&lt;SPAN class="ng-binding"&gt;Process: IKE Receiver, NUMHOG: 1, MAXHOG: 1815, LASTHOG: 1815&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV class="clearfix ng-scope"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="clearfix ng-scope"&gt;&lt;SPAN class="ng-binding"&gt;Thanks&amp;nbsp;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 21 Feb 2020 17:04:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cpu-hog/m-p/3843967#M11413</guid>
      <dc:creator>elite2010</dc:creator>
      <dc:date>2020-02-21T17:04:15Z</dc:date>
    </item>
    <item>
      <title>Re: cpu hog</title>
      <link>https://community.cisco.com/t5/network-security/cpu-hog/m-p/3924088#M11414</link>
      <description>&lt;P&gt;Were you able to find a resolution to this issue? Did you open a TAC case.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2019 17:26:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cpu-hog/m-p/3924088#M11414</guid>
      <dc:creator>Alex Pfeil</dc:creator>
      <dc:date>2019-09-13T17:26:03Z</dc:date>
    </item>
    <item>
      <title>Re: cpu hog</title>
      <link>https://community.cisco.com/t5/network-security/cpu-hog/m-p/3945535#M11415</link>
      <description>&lt;P&gt;upgrade your image&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 22 Oct 2019 17:38:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cpu-hog/m-p/3945535#M11415</guid>
      <dc:creator>elite2010</dc:creator>
      <dc:date>2019-10-22T17:38:29Z</dc:date>
    </item>
  </channel>
</rss>

