<?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: logging history in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/logging-history/m-p/743206#M987992</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ben&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Normally logging provides you a bit of clue about the reason behind the abnormal behavior or  utilisation etc., MRTG graphs only gives you the trends of usage/utilisation of recent past to verify whether all in control..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So logging comes in handy during troubleshooting process. Refer the MRTG graphs for identifying the abnormal behavior/usage and use the logs for clues to find out the reason for the same..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regds&lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 05 Jun 2007 02:48:48 GMT</pubDate>
    <dc:creator>spremkumar</dc:creator>
    <dc:date>2007-06-05T02:48:48Z</dc:date>
    <item>
      <title>logging history</title>
      <link>https://community.cisco.com/t5/network-security/logging-history/m-p/743205#M987991</link>
      <description>&lt;P&gt;Hi &lt;/P&gt;&lt;P&gt;  In the pix ver 7.0, what is difference logging history debugging from logging history warning for MRTG monitoring pix?(logging history debugging makes pix cpu higher 20% than warning)&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ben &lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 10:24:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/logging-history/m-p/743205#M987991</guid>
      <dc:creator>bma</dc:creator>
      <dc:date>2019-03-11T10:24:33Z</dc:date>
    </item>
    <item>
      <title>Re: logging history</title>
      <link>https://community.cisco.com/t5/network-security/logging-history/m-p/743206#M987992</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ben&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Normally logging provides you a bit of clue about the reason behind the abnormal behavior or  utilisation etc., MRTG graphs only gives you the trends of usage/utilisation of recent past to verify whether all in control..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So logging comes in handy during troubleshooting process. Refer the MRTG graphs for identifying the abnormal behavior/usage and use the logs for clues to find out the reason for the same..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regds&lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Jun 2007 02:48:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/logging-history/m-p/743206#M987992</guid>
      <dc:creator>spremkumar</dc:creator>
      <dc:date>2007-06-05T02:48:48Z</dc:date>
    </item>
    <item>
      <title>Re: logging history</title>
      <link>https://community.cisco.com/t5/network-security/logging-history/m-p/743207#M987993</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ben&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Jun 2007 16:50:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/logging-history/m-p/743207#M987993</guid>
      <dc:creator>bma</dc:creator>
      <dc:date>2007-06-05T16:50:25Z</dc:date>
    </item>
  </channel>
</rss>

