<?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 Enabling syslog id 113019 for firewall reporting in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/enabling-syslog-id-113019-for-firewall-reporting/m-p/2208605#M349052</link>
    <description>&lt;P&gt;I'm having a problem with an ASA 5510 and software from ManagEngine (Firewall Analyzer).&amp;nbsp; They are saying that syslog 113019 is not getting data over to the server where the firewall analyzer is installed.&amp;nbsp; I'm checking the config and I see it enabled.&amp;nbsp; I could use some help figuring out why this particular syslog info isn't making it to the reporting software when other data is.&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 01:50:38 GMT</pubDate>
    <dc:creator>dbrown</dc:creator>
    <dc:date>2019-03-12T01:50:38Z</dc:date>
    <item>
      <title>Enabling syslog id 113019 for firewall reporting</title>
      <link>https://community.cisco.com/t5/network-security/enabling-syslog-id-113019-for-firewall-reporting/m-p/2208605#M349052</link>
      <description>&lt;P&gt;I'm having a problem with an ASA 5510 and software from ManagEngine (Firewall Analyzer).&amp;nbsp; They are saying that syslog 113019 is not getting data over to the server where the firewall analyzer is installed.&amp;nbsp; I'm checking the config and I see it enabled.&amp;nbsp; I could use some help figuring out why this particular syslog info isn't making it to the reporting software when other data is.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 01:50:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/enabling-syslog-id-113019-for-firewall-reporting/m-p/2208605#M349052</guid>
      <dc:creator>dbrown</dc:creator>
      <dc:date>2019-03-12T01:50:38Z</dc:date>
    </item>
    <item>
      <title>Enabling syslog id 113019 for firewall reporting</title>
      <link>https://community.cisco.com/t5/network-security/enabling-syslog-id-113019-for-firewall-reporting/m-p/2208606#M349053</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So if you issue the command &lt;STRONG&gt;"show run logging"&lt;/STRONG&gt; you CANT see the following command?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;no logging message 113019&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 May 2013 13:25:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/enabling-syslog-id-113019-for-firewall-reporting/m-p/2208606#M349053</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-05-29T13:25:04Z</dc:date>
    </item>
    <item>
      <title>Enabling syslog id 113019 for firewall reporting</title>
      <link>https://community.cisco.com/t5/network-security/enabling-syslog-id-113019-for-firewall-reporting/m-p/2208607#M349054</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi JouniForss, thanks for the quick reply.&amp;nbsp; I hadn't run that command prior and it does ideed show "no logging message 113019" which I assume is my problem.&amp;nbsp; When viewing the syslog IDs in the ASDM it shows that one as debugging.&amp;nbsp; I'm not sure why there is a difference between the two but that has to be the issue.&amp;nbsp; Can you share the command I would need to run in order to enable that syslog message?&amp;nbsp; Thank you for the help!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 May 2013 13:30:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/enabling-syslog-id-113019-for-firewall-reporting/m-p/2208607#M349054</guid>
      <dc:creator>dbrown</dc:creator>
      <dc:date>2013-05-29T13:30:15Z</dc:date>
    </item>
    <item>
      <title>Enabling syslog id 113019 for firewall reporting</title>
      <link>https://community.cisco.com/t5/network-security/enabling-syslog-id-113019-for-firewall-reporting/m-p/2208608#M349055</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Actually I think I got it:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;logging message 113019 level 5&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'll know for sure when I see data in the reports tomorrow.&amp;nbsp; Thanks again for the assist!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 May 2013 13:42:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/enabling-syslog-id-113019-for-firewall-reporting/m-p/2208608#M349055</guid>
      <dc:creator>dbrown</dc:creator>
      <dc:date>2013-05-29T13:42:58Z</dc:date>
    </item>
    <item>
      <title>Enabling syslog id 113019 for firewall reporting</title>
      <link>https://community.cisco.com/t5/network-security/enabling-syslog-id-113019-for-firewall-reporting/m-p/2208609#M349056</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you saw the command that I mentioned above then it meant that that Syslog ID was disabled on the ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This could have been negated by issuing the command&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;logging message 113019&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After this issuing the command &lt;STRONG&gt;"show run logging"&lt;/STRONG&gt; wouldnt have any mention of the that Syslog ID as all the Syslog IDs are enabled by default.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The command you mention naturally works too. It just alters the Syslog IDs default logging level. The default level is 4 (Warnings) and its now set to 5 (Notifications)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Naturally it depends on the rest of your logging configuration what level messages are sent where. The command you mention is naturally a good way to move some Syslog ID you deem important to another level without increasing the logging output considerably.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 May 2013 14:06:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/enabling-syslog-id-113019-for-firewall-reporting/m-p/2208609#M349056</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-05-29T14:06:30Z</dc:date>
    </item>
  </channel>
</rss>

