<?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: PIX messages in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-messages/m-p/199778#M639628</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are seeing that bug still across our entire environment.  Do you have an ETA when the bug will be fixed?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 23 Apr 2003 14:53:05 GMT</pubDate>
    <dc:creator>rrussell</dc:creator>
    <dc:date>2003-04-23T14:53:05Z</dc:date>
    <item>
      <title>PIX messages</title>
      <link>https://community.cisco.com/t5/network-security/pix-messages/m-p/199775#M639625</link>
      <description>&lt;P&gt;Why when I check de log of the Firewall an event appears "%PIX-3-106011", which indicates that it is an event of severity 3, but reading the documentation of this event, it says that it is of severity 7?.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the same happens with the event "%PIX-2-400019", which indicates that it is an event of severity 2, but in fact it is of severity 4.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;R.a.M.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 06:31:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-messages/m-p/199775#M639625</guid>
      <dc:creator>ramiro</dc:creator>
      <dc:date>2020-02-21T06:31:21Z</dc:date>
    </item>
    <item>
      <title>Re: PIX messages</title>
      <link>https://community.cisco.com/t5/network-security/pix-messages/m-p/199776#M639626</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This sounds like it may be a glitch with the software. Here is a possible Bug CSCdt64462 that you may be running into. You should be able to view the bug here &lt;A class="jive-link-custom" href="http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl" target="_blank"&gt;http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Feb 2003 15:21:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-messages/m-p/199776#M639626</guid>
      <dc:creator>kmarrero</dc:creator>
      <dc:date>2003-02-03T15:21:20Z</dc:date>
    </item>
    <item>
      <title>Re: PIX messages</title>
      <link>https://community.cisco.com/t5/network-security/pix-messages/m-p/199777#M639627</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok Kyle, thank you very much!. Your response apart from being opportune, it clarifies my doubts with regard to this case.&lt;/P&gt;&lt;P&gt;Thanks again!&lt;/P&gt;&lt;P&gt;R.a.M.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Feb 2003 19:38:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-messages/m-p/199777#M639627</guid>
      <dc:creator>ramiro</dc:creator>
      <dc:date>2003-02-03T19:38:34Z</dc:date>
    </item>
    <item>
      <title>Re: PIX messages</title>
      <link>https://community.cisco.com/t5/network-security/pix-messages/m-p/199778#M639628</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are seeing that bug still across our entire environment.  Do you have an ETA when the bug will be fixed?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Apr 2003 14:53:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-messages/m-p/199778#M639628</guid>
      <dc:creator>rrussell</dc:creator>
      <dc:date>2003-04-23T14:53:05Z</dc:date>
    </item>
  </channel>
</rss>

