<?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 standby pix with high memory in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/standby-pix-with-high-memory/m-p/1981690#M440073</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rajesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You would need the output of the following commands:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;show process (taken 2-3 times in an interval of a minute)&lt;/P&gt;&lt;P&gt;show proc cpu-usage non-zero&lt;/P&gt;&lt;P&gt;show mem&lt;/P&gt;&lt;P&gt;show conn&lt;/P&gt;&lt;P&gt;shwo traffic&lt;/P&gt;&lt;P&gt;show interface&lt;/P&gt;&lt;P&gt;show cpu profile (for this, you would need to first activate CPU profile by "cpu profile activate 5000", and then an output of the command)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;These outputs would be needed to troubleshoot high CPU.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, &lt;BR /&gt;Varun Rao &lt;BR /&gt;Security Team, &lt;BR /&gt;Cisco TAC&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 04 Jul 2012 08:30:38 GMT</pubDate>
    <dc:creator>varrao</dc:creator>
    <dc:date>2012-07-04T08:30:38Z</dc:date>
    <item>
      <title>standby pix with high memory</title>
      <link>https://community.cisco.com/t5/network-security/standby-pix-with-high-memory/m-p/1981687#M440062</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone come across pix 525 with 7.2.4 , 256 MB RAM, experienceing high memory utilization ?..&lt;/P&gt;&lt;P&gt;show memory was giving used memory = 97%.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All I had done was, i did a reboot of the firewall since we were not able to take the control of the f/w.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I wonder why only the standby f/w had this issue and not the primary does not have, just to rule out that it was not due to Traffic.&lt;/P&gt;&lt;P&gt;I have searched in bugtool kits and support forums and did not find anything relevant except for a similar issue for ASA CSCsg43844.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can somebody please help me to find out any bugs are available for this issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Problem was resolved after the reboot, but cause is still Missing &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 23:25:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/standby-pix-with-high-memory/m-p/1981687#M440062</guid>
      <dc:creator>secureIT</dc:creator>
      <dc:date>2019-03-11T23:25:51Z</dc:date>
    </item>
    <item>
      <title>standby pix with high memory</title>
      <link>https://community.cisco.com/t5/network-security/standby-pix-with-high-memory/m-p/1981688#M440066</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rajesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unforunately if you have reloaded the device, then all the counters on the PIX, which could have led us to the might have been reset now. All the evidence might have been erased. What I can suggest is monitor the firewall, if you see a spike again, then open a TAC case with us, we would help you troubleshoot it. On the forum it might be difficult to troubleshoot a critical issue like this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, &lt;BR /&gt;Varun Rao &lt;BR /&gt;Security Team, &lt;BR /&gt;Cisco TAC&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Jul 2012 14:19:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/standby-pix-with-high-memory/m-p/1981688#M440066</guid>
      <dc:creator>varrao</dc:creator>
      <dc:date>2012-07-03T14:19:11Z</dc:date>
    </item>
    <item>
      <title>standby pix with high memory</title>
      <link>https://community.cisco.com/t5/network-security/standby-pix-with-high-memory/m-p/1981689#M440069</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; could you please provide the CLI cmd outputs to be taken during the problem ??&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Jul 2012 06:14:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/standby-pix-with-high-memory/m-p/1981689#M440069</guid>
      <dc:creator>secureIT</dc:creator>
      <dc:date>2012-07-04T06:14:39Z</dc:date>
    </item>
    <item>
      <title>standby pix with high memory</title>
      <link>https://community.cisco.com/t5/network-security/standby-pix-with-high-memory/m-p/1981690#M440073</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rajesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You would need the output of the following commands:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;show process (taken 2-3 times in an interval of a minute)&lt;/P&gt;&lt;P&gt;show proc cpu-usage non-zero&lt;/P&gt;&lt;P&gt;show mem&lt;/P&gt;&lt;P&gt;show conn&lt;/P&gt;&lt;P&gt;shwo traffic&lt;/P&gt;&lt;P&gt;show interface&lt;/P&gt;&lt;P&gt;show cpu profile (for this, you would need to first activate CPU profile by "cpu profile activate 5000", and then an output of the command)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;These outputs would be needed to troubleshoot high CPU.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, &lt;BR /&gt;Varun Rao &lt;BR /&gt;Security Team, &lt;BR /&gt;Cisco TAC&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Jul 2012 08:30:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/standby-pix-with-high-memory/m-p/1981690#M440073</guid>
      <dc:creator>varrao</dc:creator>
      <dc:date>2012-07-04T08:30:38Z</dc:date>
    </item>
  </channel>
</rss>

