<?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 SNMP Traps in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/snmp-traps/m-p/1119798#M878232</link>
    <description>&lt;P&gt;On PIX 7.2(4), I configured SNMP and Syslog on separate server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;snmp-server host inside 10.1.1.1&lt;/P&gt;&lt;P&gt;snmp-server enable traps snmp authentication linkup linkdown coldstart&lt;/P&gt;&lt;P&gt;snmp-server enable traps syslog&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;logging enable&lt;/P&gt;&lt;P&gt;logging timestamp&lt;/P&gt;&lt;P&gt;logging standby&lt;/P&gt;&lt;P&gt;logging asdm-buffer-size 512&lt;/P&gt;&lt;P&gt;logging console alerts&lt;/P&gt;&lt;P&gt;logging monitor notifications&lt;/P&gt;&lt;P&gt;logging buffered debugging&lt;/P&gt;&lt;P&gt;logging trap notifications&lt;/P&gt;&lt;P&gt;logging history informational&lt;/P&gt;&lt;P&gt;logging asdm debugging&lt;/P&gt;&lt;P&gt;logging facility 16&lt;/P&gt;&lt;P&gt;logging host inside 10.1.1.2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However 10.1.1.1 also picking up syslog traps (e.g., TCP tear-down, ..., etc).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/docs/security/asa/asa72/system/message/logconf.html#wp1104110" target="_blank"&gt;http://www.cisco.com/en/US/docs/security/asa/asa72/system/message/logconf.html#wp1104110&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;indicate I need to change logging history  &amp;lt;level&amp;gt;, but that would also impact syslog. What's best way to go about this?&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 14:31:23 GMT</pubDate>
    <dc:creator>normanzhang</dc:creator>
    <dc:date>2019-03-11T14:31:23Z</dc:date>
    <item>
      <title>SNMP Traps</title>
      <link>https://community.cisco.com/t5/network-security/snmp-traps/m-p/1119798#M878232</link>
      <description>&lt;P&gt;On PIX 7.2(4), I configured SNMP and Syslog on separate server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;snmp-server host inside 10.1.1.1&lt;/P&gt;&lt;P&gt;snmp-server enable traps snmp authentication linkup linkdown coldstart&lt;/P&gt;&lt;P&gt;snmp-server enable traps syslog&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;logging enable&lt;/P&gt;&lt;P&gt;logging timestamp&lt;/P&gt;&lt;P&gt;logging standby&lt;/P&gt;&lt;P&gt;logging asdm-buffer-size 512&lt;/P&gt;&lt;P&gt;logging console alerts&lt;/P&gt;&lt;P&gt;logging monitor notifications&lt;/P&gt;&lt;P&gt;logging buffered debugging&lt;/P&gt;&lt;P&gt;logging trap notifications&lt;/P&gt;&lt;P&gt;logging history informational&lt;/P&gt;&lt;P&gt;logging asdm debugging&lt;/P&gt;&lt;P&gt;logging facility 16&lt;/P&gt;&lt;P&gt;logging host inside 10.1.1.2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However 10.1.1.1 also picking up syslog traps (e.g., TCP tear-down, ..., etc).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/docs/security/asa/asa72/system/message/logconf.html#wp1104110" target="_blank"&gt;http://www.cisco.com/en/US/docs/security/asa/asa72/system/message/logconf.html#wp1104110&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;indicate I need to change logging history  &amp;lt;level&amp;gt;, but that would also impact syslog. What's best way to go about this?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 14:31:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/snmp-traps/m-p/1119798#M878232</guid>
      <dc:creator>normanzhang</dc:creator>
      <dc:date>2019-03-11T14:31:23Z</dc:date>
    </item>
    <item>
      <title>Re: SNMP Traps</title>
      <link>https://community.cisco.com/t5/network-security/snmp-traps/m-p/1119799#M878237</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Norman&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Actually changing the logging history &lt;LEVEL&gt; does not impact syslog logging. It is not intiutivly obvious but the logging history &lt;LEVEL&gt; command does not change the syslog logging levels but does control the level of syslog message sent as an SNMP trap.&lt;/LEVEL&gt;&lt;/LEVEL&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your post seems to indicate that you were not expecting 10.1.1.1 to pick up syslog messages. But the command snmp-server enable traps syslog instructs the PIX to send syslog messages formatted as snmp traps. You use the logging history &lt;LEVEL&gt; to control the level of syslog messages to send - which allows you to control the minimum syslog message level to the snmp server separate from what you send to the syslog server.&lt;/LEVEL&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rick&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Jan 2009 03:45:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/snmp-traps/m-p/1119799#M878237</guid>
      <dc:creator>Richard Burts</dc:creator>
      <dc:date>2009-01-02T03:45:11Z</dc:date>
    </item>
    <item>
      <title>Re: SNMP Traps</title>
      <link>https://community.cisco.com/t5/network-security/snmp-traps/m-p/1119800#M878239</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i will do&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;no snmp-server enable traps syslog&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;to stop syslog being sent as snmp traps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Jan 2009 19:31:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/snmp-traps/m-p/1119800#M878239</guid>
      <dc:creator>normanzhang</dc:creator>
      <dc:date>2009-01-02T19:31:04Z</dc:date>
    </item>
    <item>
      <title>Re: SNMP Traps</title>
      <link>https://community.cisco.com/t5/network-security/snmp-traps/m-p/1119801#M878243</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Norman&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes that should stop sending syslog messages as SNMP traps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am glad that my response was helpful. Thank you for using the rating system to indicate that your question was resolved (and thanks for the rating). It makes the forum more useful when people can read a question and can know that there were responses that led to a solution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The forum is an excellent place to learn about Cisco networking. I encourage you to continue your participation in the forum.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rick&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Jan 2009 19:58:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/snmp-traps/m-p/1119801#M878243</guid>
      <dc:creator>Richard Burts</dc:creator>
      <dc:date>2009-01-02T19:58:34Z</dc:date>
    </item>
  </channel>
</rss>

