<?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 device logging in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-device-logging/m-p/52321#M687424</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Set your PIX logging level to Debugging (Level 7):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;pix(config)# logging trap debugging&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I guess you have built a conduit (or ACL if you've moved on from conduits!) for this connection.  If you have configured the PIX as per the manual (it says for production use level 3 / errors) then the syslog will only contain denys etc.  If your firewalls are busy, then the logfile will become very large once you set the syslog level to debugging.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyway hope this sorts it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phil.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 14 Nov 2001 17:38:17 GMT</pubDate>
    <dc:creator>phil.benn</dc:creator>
    <dc:date>2001-11-14T17:38:17Z</dc:date>
    <item>
      <title>PIX device logging</title>
      <link>https://community.cisco.com/t5/network-security/pix-device-logging/m-p/52320#M687423</link>
      <description>&lt;P&gt;When I tried to access the PIX firewall using the external IP address (from the Internet), I noticed that the PIX did not created a syslog entry to report this attempt. Does someone know how to setup the PIX that attempts to access the pix are logged?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 05:54:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-device-logging/m-p/52320#M687423</guid>
      <dc:creator>rrbleeker</dc:creator>
      <dc:date>2020-02-21T05:54:16Z</dc:date>
    </item>
    <item>
      <title>Re: PIX device logging</title>
      <link>https://community.cisco.com/t5/network-security/pix-device-logging/m-p/52321#M687424</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Set your PIX logging level to Debugging (Level 7):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;pix(config)# logging trap debugging&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I guess you have built a conduit (or ACL if you've moved on from conduits!) for this connection.  If you have configured the PIX as per the manual (it says for production use level 3 / errors) then the syslog will only contain denys etc.  If your firewalls are busy, then the logfile will become very large once you set the syslog level to debugging.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyway hope this sorts it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phil.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Nov 2001 17:38:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-device-logging/m-p/52321#M687424</guid>
      <dc:creator>phil.benn</dc:creator>
      <dc:date>2001-11-14T17:38:17Z</dc:date>
    </item>
  </channel>
</rss>

