<?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 Memory Utilization on 5510 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/memory-utilization-on-5510/m-p/2133025#M395289</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Shane,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Okay, good to know that,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here are some facts about memory problems:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;H3 style="color: #000000;"&gt;&lt;A name="memory"&gt;High Memory Utilization&lt;/A&gt;&lt;/H3&gt;&lt;P style="color: #000000; font-size: 12px;"&gt;Here are some possible causes and resolutions for high memory utilization:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;Event logging:&lt;/STRONG&gt; Event logging can consume large amounts of memory. In order to resolve this issue, install and log all events to an external server, such as a syslog server.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Memory Leakage:&lt;/STRONG&gt; A known issue in the security appliance software can lead to high memory consumption. In order to resolve this issue, upgrade the security appliance software.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Debugging Enabled:&lt;/STRONG&gt; Debugging can consume large amounts of memory. In order to resolve this issue, disable debugging with the &lt;TT&gt;undebug all&lt;/TT&gt; command.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Blocking Ports:&lt;/STRONG&gt; Blocking ports on the outside interface of a security appliance cause the security appliance to consume high amounts of memory to block the packets through the specified ports.In order to resolve this issue, block the offending traffic at the ISP end.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Threat-Detection:&lt;/STRONG&gt; The threat detection feature consists of different levels of statistics gathering for various threats, as well as scanning threat detection, which determines when a host is performing a scan. &lt;STRONG&gt;Turn off&lt;/STRONG&gt; this feature to consume less memory.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN style="line-height: 0px;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Regards,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 22 Nov 2012 16:57:13 GMT</pubDate>
    <dc:creator>Julio Carvajal</dc:creator>
    <dc:date>2012-11-22T16:57:13Z</dc:date>
    <item>
      <title>Memory Utilization on 5510</title>
      <link>https://community.cisco.com/t5/network-security/memory-utilization-on-5510/m-p/2133022#M395283</link>
      <description>&lt;P&gt;Hi Folks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just want to check with you about memory utilization on the Asa 5510 ..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Free memory: 19%&lt;/P&gt;&lt;P&gt;Used Memory: 81%&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this normal? Because we hade a problem this morning and the memory was at 100%..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Device Manager version 6.1(5) 57&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hardware:&amp;nbsp;&amp;nbsp; ASA5510-K8, 256 MB RAM, CPU Pentium 4 Celeron 1600 MHz&lt;/P&gt;&lt;P&gt;Internal ATA Compact Flash, 256MB&lt;/P&gt;&lt;P&gt;BIOS Flash M50FW080 @ 0xffe00000, 1024KB&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any tips and tricks?&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 00:26:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/memory-utilization-on-5510/m-p/2133022#M395283</guid>
      <dc:creator>Shane Riley</dc:creator>
      <dc:date>2019-03-12T00:26:36Z</dc:date>
    </item>
    <item>
      <title>Memory Utilization on 5510</title>
      <link>https://community.cisco.com/t5/network-security/memory-utilization-on-5510/m-p/2133023#M395284</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Shane,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Open a TAC case as soon as you can so we can take the required outputs to decode what is going on, This is definetely not expected (&amp;nbsp; Because we hade a problem this morning and the memory was at 100%)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Julio&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Nov 2012 14:58:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/memory-utilization-on-5510/m-p/2133023#M395284</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2012-11-22T14:58:58Z</dc:date>
    </item>
    <item>
      <title>Memory Utilization on 5510</title>
      <link>https://community.cisco.com/t5/network-security/memory-utilization-on-5510/m-p/2133024#M395287</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well i don't think its a huge problem, I think it was a spanning tree issue on the switches..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But for now the mem utilization is at 81%..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/Shane&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Nov 2012 16:17:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/memory-utilization-on-5510/m-p/2133024#M395287</guid>
      <dc:creator>Shane Riley</dc:creator>
      <dc:date>2012-11-22T16:17:55Z</dc:date>
    </item>
    <item>
      <title>Memory Utilization on 5510</title>
      <link>https://community.cisco.com/t5/network-security/memory-utilization-on-5510/m-p/2133025#M395289</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Shane,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Okay, good to know that,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here are some facts about memory problems:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;H3 style="color: #000000;"&gt;&lt;A name="memory"&gt;High Memory Utilization&lt;/A&gt;&lt;/H3&gt;&lt;P style="color: #000000; font-size: 12px;"&gt;Here are some possible causes and resolutions for high memory utilization:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;Event logging:&lt;/STRONG&gt; Event logging can consume large amounts of memory. In order to resolve this issue, install and log all events to an external server, such as a syslog server.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Memory Leakage:&lt;/STRONG&gt; A known issue in the security appliance software can lead to high memory consumption. In order to resolve this issue, upgrade the security appliance software.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Debugging Enabled:&lt;/STRONG&gt; Debugging can consume large amounts of memory. In order to resolve this issue, disable debugging with the &lt;TT&gt;undebug all&lt;/TT&gt; command.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Blocking Ports:&lt;/STRONG&gt; Blocking ports on the outside interface of a security appliance cause the security appliance to consume high amounts of memory to block the packets through the specified ports.In order to resolve this issue, block the offending traffic at the ISP end.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Threat-Detection:&lt;/STRONG&gt; The threat detection feature consists of different levels of statistics gathering for various threats, as well as scanning threat detection, which determines when a host is performing a scan. &lt;STRONG&gt;Turn off&lt;/STRONG&gt; this feature to consume less memory.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN style="line-height: 0px;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Regards,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Nov 2012 16:57:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/memory-utilization-on-5510/m-p/2133025#M395289</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2012-11-22T16:57:13Z</dc:date>
    </item>
    <item>
      <title>Re: Memory Utilization on 5510</title>
      <link>https://community.cisco.com/t5/network-security/memory-utilization-on-5510/m-p/2133026#M395291</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the info,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have one more question, now the &lt;STRONG&gt;ASA&lt;/STRONG&gt; is working fine, but one thing is a little off, the dmz interface is not working the way it suppose to. Clients are not reaching the servers on the DMZ interface &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt; Maybe it has something to do with that we hade a &lt;STRONG&gt;failover firewall &lt;/STRONG&gt;that was On before..But probably not..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also Syslog Messages in the ASDM, i see a bunch of&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;DENY ICMP revers path check from x.x.xx to x.x.x.x on interface dmz&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;STRONG&gt;DENY ICMP revers path check from x.x.xx to x.x.x.x on interface outside&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Shane&lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Nov 2012 12:12:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/memory-utilization-on-5510/m-p/2133026#M395291</guid>
      <dc:creator>Shane Riley</dc:creator>
      <dc:date>2012-11-23T12:12:28Z</dc:date>
    </item>
  </channel>
</rss>

