<?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 IPS packet captures-disk space in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ips-packet-captures-disk-space/m-p/1686564#M64966</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Justin. I have been relying on the packet captures because the email notifications are not working as you know. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jason&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 21 Jun 2011 15:40:08 GMT</pubDate>
    <dc:creator>jason.giambrone</dc:creator>
    <dc:date>2011-06-21T15:40:08Z</dc:date>
    <item>
      <title>IPS packet captures-disk space</title>
      <link>https://community.cisco.com/t5/network-security/ips-packet-captures-disk-space/m-p/1686562#M64953</link>
      <description>&lt;P&gt;I have been doing packet captures on High and Medium events and in the IME there is no obvious way to delete old captures. They don't take up alot space but I wanted to know if there is a way to view the disk capacity on the IPS and how I can delete old capture files from the IPS.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 12:22:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-packet-captures-disk-space/m-p/1686562#M64953</guid>
      <dc:creator>jason.giambrone</dc:creator>
      <dc:date>2019-03-10T12:22:57Z</dc:date>
    </item>
    <item>
      <title>IPS packet captures-disk space</title>
      <link>https://community.cisco.com/t5/network-security/ips-packet-captures-disk-space/m-p/1686563#M64960</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jason,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; The ip logging functionality stores the logs in a circular buffer, so there is no need (and no supported way) to delete/manage the old log files - they will be overwritten then new logs necessitate it.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All of the information on ip logging can be found here:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/ips/7.0/configuration/guide/cli/cli_ip_logging.html#wp1030704"&gt;http://www.cisco.com/en/US/docs/security/ips/7.0/configuration/guide/cli/cli_ip_logging.html#wp1030704&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, unless you have a specific need for full stream captures for all high/medium events, you can use the "Produce Verbose Alert" action instead of the ip logging actions to capture the offending packet with significantly less resource utilization per alert. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-JT&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Jun 2011 14:55:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-packet-captures-disk-space/m-p/1686563#M64960</guid>
      <dc:creator>Justin Teixeira</dc:creator>
      <dc:date>2011-06-21T14:55:01Z</dc:date>
    </item>
    <item>
      <title>IPS packet captures-disk space</title>
      <link>https://community.cisco.com/t5/network-security/ips-packet-captures-disk-space/m-p/1686564#M64966</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Justin. I have been relying on the packet captures because the email notifications are not working as you know. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jason&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Jun 2011 15:40:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-packet-captures-disk-space/m-p/1686564#M64966</guid>
      <dc:creator>jason.giambrone</dc:creator>
      <dc:date>2011-06-21T15:40:08Z</dc:date>
    </item>
  </channel>
</rss>

