<?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 SYSLOG MSG? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/syslog-msg/m-p/1834732#M460378</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to do some changes for syslog message:&lt;/P&gt;&lt;P&gt;As per below message like message ID 302014 or some more are examples, are sending log to my log server and server utilization is very high. So I want to do like these message alert on syslog server is not necessary for me... but its still sending so I need a help to block the particular message id don't need to send on server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How I can do this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Aug 24 2007 11:15:33: %ASA-6-302013: Built inbound TCP connection 733283 for outside:192.168.208.63/51608 (192.168.208.63/51608) to inside:192.168.150.63/80 (192.168.150.63/80)&lt;/P&gt;&lt;P&gt;Aug 24 2007 11:15:33: %ASA-6-302014: Teardown TCP connection 733283 for outside:192.168.208.63/51608 to inside:192.168.150.63/80 duration 0:00:00 bytes 0 &lt;/P&gt;&lt;P&gt;Aug 24 2007 10:27:22: %ASA-6-302015: Built inbound UDP connection 732748 for outside:192.168.208.63/49804 (192.168.208.63/49804) to inside:192.168.150.70/53 (192.168.150.70/53)&lt;/P&gt;&lt;P&gt;Aug 24 2007 10:27:22: %ASA-6-302015: Built inbound UDP connection 732749 for outside:192.168.208.63/49804 (192.168.208.63/49804) to inside:192.168.150.70/123 (192.168.150.70/123)&lt;/P&gt;&lt;P&gt;Aug 24 2007 10:27:22: %ASA-6-302015: Built inbound UDP connection 732750 for outside:192.168.208.63/49804 (192.168.208.63/49804) to inside:192.168.150.70/&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ug 24 2007 10:27:22: %ASA-6-302020: Built ICMP connection for faddr 192.168.208.63/15343 gaddr 192.168.150.70/0 laddr 192.168.150.70/0&lt;/P&gt;&lt;P&gt;Aug 24 2007 10:27:22: %ASA-6-302021: Teardown ICMP connection for faddr 192.168.208.63/0 gaddr 192.168.150.70/0 laddr 192.168.150.70/0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance....&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 22:21:25 GMT</pubDate>
    <dc:creator>abhi-adte</dc:creator>
    <dc:date>2019-03-11T22:21:25Z</dc:date>
    <item>
      <title>SYSLOG MSG?</title>
      <link>https://community.cisco.com/t5/network-security/syslog-msg/m-p/1834732#M460378</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to do some changes for syslog message:&lt;/P&gt;&lt;P&gt;As per below message like message ID 302014 or some more are examples, are sending log to my log server and server utilization is very high. So I want to do like these message alert on syslog server is not necessary for me... but its still sending so I need a help to block the particular message id don't need to send on server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How I can do this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Aug 24 2007 11:15:33: %ASA-6-302013: Built inbound TCP connection 733283 for outside:192.168.208.63/51608 (192.168.208.63/51608) to inside:192.168.150.63/80 (192.168.150.63/80)&lt;/P&gt;&lt;P&gt;Aug 24 2007 11:15:33: %ASA-6-302014: Teardown TCP connection 733283 for outside:192.168.208.63/51608 to inside:192.168.150.63/80 duration 0:00:00 bytes 0 &lt;/P&gt;&lt;P&gt;Aug 24 2007 10:27:22: %ASA-6-302015: Built inbound UDP connection 732748 for outside:192.168.208.63/49804 (192.168.208.63/49804) to inside:192.168.150.70/53 (192.168.150.70/53)&lt;/P&gt;&lt;P&gt;Aug 24 2007 10:27:22: %ASA-6-302015: Built inbound UDP connection 732749 for outside:192.168.208.63/49804 (192.168.208.63/49804) to inside:192.168.150.70/123 (192.168.150.70/123)&lt;/P&gt;&lt;P&gt;Aug 24 2007 10:27:22: %ASA-6-302015: Built inbound UDP connection 732750 for outside:192.168.208.63/49804 (192.168.208.63/49804) to inside:192.168.150.70/&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ug 24 2007 10:27:22: %ASA-6-302020: Built ICMP connection for faddr 192.168.208.63/15343 gaddr 192.168.150.70/0 laddr 192.168.150.70/0&lt;/P&gt;&lt;P&gt;Aug 24 2007 10:27:22: %ASA-6-302021: Teardown ICMP connection for faddr 192.168.208.63/0 gaddr 192.168.150.70/0 laddr 192.168.150.70/0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance....&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 22:21:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/syslog-msg/m-p/1834732#M460378</guid>
      <dc:creator>abhi-adte</dc:creator>
      <dc:date>2019-03-11T22:21:25Z</dc:date>
    </item>
    <item>
      <title>SYSLOG MSG?</title>
      <link>https://community.cisco.com/t5/network-security/syslog-msg/m-p/1834733#M460380</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Try 'no logging message &lt;MESSAGE id=""&gt;' on ASA.&lt;/MESSAGE&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hth&lt;/P&gt;&lt;P&gt;MS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Jan 2012 18:17:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/syslog-msg/m-p/1834733#M460380</guid>
      <dc:creator>mvsheik123</dc:creator>
      <dc:date>2012-01-31T18:17:30Z</dc:date>
    </item>
    <item>
      <title>Re: SYSLOG MSG?</title>
      <link>https://community.cisco.com/t5/network-security/syslog-msg/m-p/1834734#M460382</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As MS noted, you can disable individual log messages by their ID number. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Another approach is to raise the logging message level globally using the command:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE style="font-size: 10px; color: #000000; background-color: #ffffff; padding-left: 30px;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;&lt;STRONG&gt;logging trap &lt;/STRONG&gt;{&lt;EM&gt;severity_level&lt;/EM&gt; | &lt;EM&gt;message_list&lt;/EM&gt;}&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The messages you cite are all Level 6 (Informational). If you change the level to 5 (Notification), only messages of that severity or greater ( = lower numerical value) will be logged. &lt;A href="http://www.cisco.com/en/US/docs/security/asa/asa84/system/message/logsevp.html"&gt;Here&lt;/A&gt; is a listing of messages by severity.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See &lt;A href="http://www.cisco.com/en/US/docs/security/asa/asa84/configuration/guide/monitor_syslog.html#wp1085049" rel="nofollow"&gt;here&lt;/A&gt; for details on configuring logging options.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Jan 2012 18:31:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/syslog-msg/m-p/1834734#M460382</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2012-01-31T18:31:08Z</dc:date>
    </item>
  </channel>
</rss>

