<?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 IDS 4250 High Memory Utilization in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/cisco-ids-4250-high-memory-utilization/m-p/1467437#M67451</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;First thing you should do is upgrade to the latest version of E4 code in your train (6.0, 6.0, 7.1 etc). Some of the older vsrions of code had a memory leak under certain conditions.&lt;/P&gt;&lt;P&gt;The second thing is to determine if this is being caused by traffic (in which case there is little you can do about it beside swapping in a larger sensor or changing your existing signature policy/actions). If you have three sensors have the same signature poilcy on them you can swap two of the and see if the problem follows the sensor of the traffic (my bet is it follows the traffic)&lt;/P&gt;&lt;P&gt;Lastly you should determine if this is really a problem (maybe this should be first). Are you seeing any missed packet percentages in yoru log?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Bob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 13 May 2010 17:01:06 GMT</pubDate>
    <dc:creator>rhermes</dc:creator>
    <dc:date>2010-05-13T17:01:06Z</dc:date>
    <item>
      <title>Cisco IDS 4250 High Memory Utilization</title>
      <link>https://community.cisco.com/t5/network-security/cisco-ids-4250-high-memory-utilization/m-p/1467436#M67450</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;My Name is Nelson.&lt;/P&gt;&lt;P&gt;&lt;SPAN class="long_text" id="result_box"&gt;&lt;SPAN&gt;I have three Devices IDs implemented but one of them has a high memory utilization (higher to 90%). I have disconnected all interfaces on the IDS but the use of memory remains high. How I can verify what is the origin of this high use from memory&amp;nbsp; and what steps should I followed.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="long_text"&gt;&lt;SPAN&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 11:59:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-ids-4250-high-memory-utilization/m-p/1467436#M67450</guid>
      <dc:creator>Nelsonmejia09</dc:creator>
      <dc:date>2019-03-10T11:59:31Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco IDS 4250 High Memory Utilization</title>
      <link>https://community.cisco.com/t5/network-security/cisco-ids-4250-high-memory-utilization/m-p/1467437#M67451</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;First thing you should do is upgrade to the latest version of E4 code in your train (6.0, 6.0, 7.1 etc). Some of the older vsrions of code had a memory leak under certain conditions.&lt;/P&gt;&lt;P&gt;The second thing is to determine if this is being caused by traffic (in which case there is little you can do about it beside swapping in a larger sensor or changing your existing signature policy/actions). If you have three sensors have the same signature poilcy on them you can swap two of the and see if the problem follows the sensor of the traffic (my bet is it follows the traffic)&lt;/P&gt;&lt;P&gt;Lastly you should determine if this is really a problem (maybe this should be first). Are you seeing any missed packet percentages in yoru log?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Bob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 May 2010 17:01:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-ids-4250-high-memory-utilization/m-p/1467437#M67451</guid>
      <dc:creator>rhermes</dc:creator>
      <dc:date>2010-05-13T17:01:06Z</dc:date>
    </item>
  </channel>
</rss>

