<?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: FTD snort memory allocation &amp;quot;Policy Configuration Memory&amp;quot in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ftd-snort-memory-allocation-quot-policy-configuration-memory/m-p/5218689#M1117219</link>
    <description>&lt;P&gt;Yes, escalations has certainly some tools around this, so it maybe better to open a TAC case to better assist you on better balancing your memory usage within snort. Just a general suggestion though, snort3 is using much less memory than snort2 so if you are in that version right now, I would look into upgrading to the newer snort engine.&lt;/P&gt;</description>
    <pubDate>Fri, 01 Nov 2024 16:41:01 GMT</pubDate>
    <dc:creator>ckleopa</dc:creator>
    <dc:date>2024-11-01T16:41:01Z</dc:date>
    <item>
      <title>FTD snort memory allocation "Policy Configuration Memory"</title>
      <link>https://community.cisco.com/t5/network-security/ftd-snort-memory-allocation-quot-policy-configuration-memory/m-p/5218686#M1117217</link>
      <description>&lt;P&gt;Hi Cisco Community&lt;/P&gt;&lt;P&gt;Is there a way to get a more broken down view to see what is actually consuming the most memory in the "&lt;SPAN&gt;Policy Configuration Memory"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I am getting some warnings about it using too much memory so we tried to delete some ACLs that were not in use plus there was a few ACLs that had huge object lists but it didn't make that big of a difference.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What I'd like to see is what is really the biggest memory consumers within "&lt;SPAN&gt;Policy Configuration Memory"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 01 Nov 2024 16:34:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-snort-memory-allocation-quot-policy-configuration-memory/m-p/5218686#M1117217</guid>
      <dc:creator>Alex-Pr</dc:creator>
      <dc:date>2024-11-01T16:34:00Z</dc:date>
    </item>
    <item>
      <title>Re: FTD snort memory allocation "Policy Configuration Memory&amp;quot</title>
      <link>https://community.cisco.com/t5/network-security/ftd-snort-memory-allocation-quot-policy-configuration-memory/m-p/5218689#M1117219</link>
      <description>&lt;P&gt;Yes, escalations has certainly some tools around this, so it maybe better to open a TAC case to better assist you on better balancing your memory usage within snort. Just a general suggestion though, snort3 is using much less memory than snort2 so if you are in that version right now, I would look into upgrading to the newer snort engine.&lt;/P&gt;</description>
      <pubDate>Fri, 01 Nov 2024 16:41:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-snort-memory-allocation-quot-policy-configuration-memory/m-p/5218689#M1117219</guid>
      <dc:creator>ckleopa</dc:creator>
      <dc:date>2024-11-01T16:41:01Z</dc:date>
    </item>
  </channel>
</rss>

