<?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 How do I configure ASA 5520 to send SNMP Trap when IP SLA monito in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/how-do-i-configure-asa-5520-to-send-snmp-trap-when-ip-sla/m-p/1913652#M456961</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;You can atleast use the following log message to see when these changes happen&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;H3&gt; 622001 &lt;/H3&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;A name="wp3743052"&gt;&lt;/A&gt;Error Message&amp;nbsp;&amp;nbsp;&amp;nbsp; %PIX|ASA-6-622001: string tracked route &lt;EM&gt;network&lt;/EM&gt; &lt;EM&gt;mask&lt;/EM&gt; &lt;EM&gt;address&lt;/EM&gt;, distance &lt;EM&gt;number&lt;/EM&gt;, &lt;BR /&gt;table &lt;EM&gt;string&lt;/EM&gt;, on interface &lt;EM&gt;interface-name&lt;BR /&gt;&lt;/EM&gt;&lt;/PRE&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;A name="wp3744170"&gt;&lt;/A&gt; &lt;/P&gt;
&lt;P&gt;Explanation&amp;nbsp;&amp;nbsp;&amp;nbsp; A tracked route has been added to or removed from a routing table, which means that&amp;nbsp; the state of the tracked object has changed from up or down. &lt;/P&gt;
&lt;P&gt;&lt;A name="wp4014445"&gt;&lt;/A&gt; &lt;/P&gt;
&lt;P&gt; &lt;EM&gt;string&lt;/EM&gt;—"Adding" or "Removing." &lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;A name="wp4014446"&gt;&lt;/A&gt; &lt;/P&gt;
&lt;P&gt; &lt;EM&gt;network&lt;/EM&gt;—The network address. &lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;A name="wp4014447"&gt;&lt;/A&gt; &lt;/P&gt;
&lt;P&gt; &lt;EM&gt;mask&lt;/EM&gt;—The network mask. &lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;A name="wp4014448"&gt;&lt;/A&gt; &lt;/P&gt;
&lt;P&gt; &lt;EM&gt;address&lt;/EM&gt;—The gateway address. &lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;A name="wp4014449"&gt;&lt;/A&gt; &lt;/P&gt;
&lt;P&gt; &lt;EM&gt;number&lt;/EM&gt;—The route administrative distance. &lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;A name="wp4014450"&gt;&lt;/A&gt; &lt;/P&gt;
&lt;P&gt; &lt;EM&gt;string&lt;/EM&gt;—The routing table name. &lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;A name="wp4014451"&gt;&lt;/A&gt; &lt;/P&gt;
&lt;P&gt; &lt;EM&gt;interface-name&lt;/EM&gt;—The interface name as specified by the &lt;STRONG&gt;nameif&lt;/STRONG&gt; command. &lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;A name="wp4020286"&gt;&lt;/A&gt; &lt;/P&gt;
&lt;P&gt;Recommended Action&amp;nbsp;&amp;nbsp;&amp;nbsp; None. This is an informational message that indicates a change in routing and&amp;nbsp; a likely change in forwarding paths, as configured by the tracking and SLA commands. &lt;/P&gt;
&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You also need to make sure your configuration line "logging trap &lt;LEVEL&gt;" is set to level 6 = informational. Or you have configured the log message in question to show otherwise.&lt;/LEVEL&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>Tue, 17 Apr 2012 14:33:17 GMT</pubDate>
    <dc:creator>Jouni Forss</dc:creator>
    <dc:date>2012-04-17T14:33:17Z</dc:date>
    <item>
      <title>How do I configure ASA 5520 to send SNMP Trap when IP SLA monitored port fails?</title>
      <link>https://community.cisco.com/t5/network-security/how-do-i-configure-asa-5520-to-send-snmp-trap-when-ip-sla/m-p/1913651#M456960</link>
      <description>&lt;P&gt;Below is my config for IP SLA.&amp;nbsp; I would like a SNMP trap to be sent when my primary fails over to my secondary and so on.&amp;nbsp; Is this even possible?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sla monitor 20&lt;/P&gt;&lt;P&gt; type echo protocol ipIcmpEcho 100.X.X.1 interface INET-FIOS150&lt;/P&gt;&lt;P&gt; num-packets 2&lt;/P&gt;&lt;P&gt; timeout 2000&lt;/P&gt;&lt;P&gt; threshold 2000&lt;/P&gt;&lt;P&gt; frequency 5&lt;/P&gt;&lt;P&gt;sla monitor schedule 20 life forever start-time now&lt;/P&gt;&lt;P&gt;sla monitor 21&lt;/P&gt;&lt;P&gt; type echo protocol ipIcmpEcho 96.X.X.1 interface INET-FIOS25&lt;/P&gt;&lt;P&gt; num-packets 2&lt;/P&gt;&lt;P&gt; timeout 2000&lt;/P&gt;&lt;P&gt; threshold 2000&lt;/P&gt;&lt;P&gt; frequency 5&lt;/P&gt;&lt;P&gt;sla monitor schedule 21 life forever start-time now&lt;/P&gt;&lt;P&gt;sla monitor 22&lt;/P&gt;&lt;P&gt; type echo protocol ipIcmpEcho 70.X.X.33 interface INET-WIND&lt;/P&gt;&lt;P&gt; num-packets 2&lt;/P&gt;&lt;P&gt; timeout 2000&lt;/P&gt;&lt;P&gt; threshold 2000&lt;/P&gt;&lt;P&gt; frequency 5&lt;/P&gt;&lt;P&gt;sla monitor schedule 22 life forever start-time now&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;snmp-server host CORPORATE 10.X.X.203 community ***** version 2c&lt;/P&gt;&lt;P&gt;snmp-server location Venice&lt;/P&gt;&lt;P&gt;snmp-server contact IT Tech Services&lt;/P&gt;&lt;P&gt;snmp-server community *****&lt;/P&gt;&lt;P&gt;snmp-server enable traps snmp authentication linkup linkdown coldstart warmstart&lt;/P&gt;&lt;P&gt;snmp-server enable traps syslog&lt;/P&gt;&lt;P&gt;snmp-server enable traps ipsec start stop&lt;/P&gt;&lt;P&gt;snmp-server enable traps entity config-change fru-insert fru-remove&lt;/P&gt;&lt;P&gt;snmp-server enable traps memory-threshold&lt;/P&gt;&lt;P&gt;snmp-server enable traps interface-threshold&lt;/P&gt;&lt;P&gt;snmp-server enable traps remote-access session-threshold-exceeded&lt;/P&gt;&lt;P&gt;snmp-server enable traps connection-limit-reached&lt;/P&gt;&lt;P&gt;snmp-server enable traps cpu threshold rising&lt;/P&gt;&lt;P&gt;snmp-server enable traps ikev2 start stop&lt;/P&gt;&lt;P&gt;snmp-server enable traps nat packet-discard&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 22:54:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-do-i-configure-asa-5520-to-send-snmp-trap-when-ip-sla/m-p/1913651#M456960</guid>
      <dc:creator>Luis Sanchez</dc:creator>
      <dc:date>2019-03-11T22:54:49Z</dc:date>
    </item>
    <item>
      <title>How do I configure ASA 5520 to send SNMP Trap when IP SLA monito</title>
      <link>https://community.cisco.com/t5/network-security/how-do-i-configure-asa-5520-to-send-snmp-trap-when-ip-sla/m-p/1913652#M456961</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;You can atleast use the following log message to see when these changes happen&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;H3&gt; 622001 &lt;/H3&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;A name="wp3743052"&gt;&lt;/A&gt;Error Message&amp;nbsp;&amp;nbsp;&amp;nbsp; %PIX|ASA-6-622001: string tracked route &lt;EM&gt;network&lt;/EM&gt; &lt;EM&gt;mask&lt;/EM&gt; &lt;EM&gt;address&lt;/EM&gt;, distance &lt;EM&gt;number&lt;/EM&gt;, &lt;BR /&gt;table &lt;EM&gt;string&lt;/EM&gt;, on interface &lt;EM&gt;interface-name&lt;BR /&gt;&lt;/EM&gt;&lt;/PRE&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;A name="wp3744170"&gt;&lt;/A&gt; &lt;/P&gt;
&lt;P&gt;Explanation&amp;nbsp;&amp;nbsp;&amp;nbsp; A tracked route has been added to or removed from a routing table, which means that&amp;nbsp; the state of the tracked object has changed from up or down. &lt;/P&gt;
&lt;P&gt;&lt;A name="wp4014445"&gt;&lt;/A&gt; &lt;/P&gt;
&lt;P&gt; &lt;EM&gt;string&lt;/EM&gt;—"Adding" or "Removing." &lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;A name="wp4014446"&gt;&lt;/A&gt; &lt;/P&gt;
&lt;P&gt; &lt;EM&gt;network&lt;/EM&gt;—The network address. &lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;A name="wp4014447"&gt;&lt;/A&gt; &lt;/P&gt;
&lt;P&gt; &lt;EM&gt;mask&lt;/EM&gt;—The network mask. &lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;A name="wp4014448"&gt;&lt;/A&gt; &lt;/P&gt;
&lt;P&gt; &lt;EM&gt;address&lt;/EM&gt;—The gateway address. &lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;A name="wp4014449"&gt;&lt;/A&gt; &lt;/P&gt;
&lt;P&gt; &lt;EM&gt;number&lt;/EM&gt;—The route administrative distance. &lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;A name="wp4014450"&gt;&lt;/A&gt; &lt;/P&gt;
&lt;P&gt; &lt;EM&gt;string&lt;/EM&gt;—The routing table name. &lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;A name="wp4014451"&gt;&lt;/A&gt; &lt;/P&gt;
&lt;P&gt; &lt;EM&gt;interface-name&lt;/EM&gt;—The interface name as specified by the &lt;STRONG&gt;nameif&lt;/STRONG&gt; command. &lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;A name="wp4020286"&gt;&lt;/A&gt; &lt;/P&gt;
&lt;P&gt;Recommended Action&amp;nbsp;&amp;nbsp;&amp;nbsp; None. This is an informational message that indicates a change in routing and&amp;nbsp; a likely change in forwarding paths, as configured by the tracking and SLA commands. &lt;/P&gt;
&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You also need to make sure your configuration line "logging trap &lt;LEVEL&gt;" is set to level 6 = informational. Or you have configured the log message in question to show otherwise.&lt;/LEVEL&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>Tue, 17 Apr 2012 14:33:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-do-i-configure-asa-5520-to-send-snmp-trap-when-ip-sla/m-p/1913652#M456961</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2012-04-17T14:33:17Z</dc:date>
    </item>
    <item>
      <title>How do I configure ASA 5520 to send SNMP Trap when IP SLA monito</title>
      <link>https://community.cisco.com/t5/network-security/how-do-i-configure-asa-5520-to-send-snmp-trap-when-ip-sla/m-p/1913653#M456962</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Logging Level 6 can get intense.&amp;nbsp; Soon as I turned it on my syslog server was flooded with 100's of events. Any other options?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Apr 2012 18:45:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-do-i-configure-asa-5520-to-send-snmp-trap-when-ip-sla/m-p/1913653#M456962</guid>
      <dc:creator>Luis Sanchez</dc:creator>
      <dc:date>2012-04-17T18:45:16Z</dc:date>
    </item>
    <item>
      <title>How do I configure ASA 5520 to send SNMP Trap when IP SLA monito</title>
      <link>https://community.cisco.com/t5/network-security/how-do-i-configure-asa-5520-to-send-snmp-trap-when-ip-sla/m-p/1913654#M456963</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;I think you can modify the default logging level of some log messages&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The command format is this&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;logging message &lt;SYSLOG message="" number=""&gt; level &lt;LEVEL&gt;&lt;/LEVEL&gt;&lt;/SYSLOG&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So for your setup you could for example do&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;logging message 622001 level notifications&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;or in other format&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;logging message 622001 level 5&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;or even change the level some more&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Apr 2012 18:55:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-do-i-configure-asa-5520-to-send-snmp-trap-when-ip-sla/m-p/1913654#M456963</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2012-04-17T18:55:41Z</dc:date>
    </item>
    <item>
      <title>How do I configure ASA 5520 to send SNMP Trap when IP SLA monito</title>
      <link>https://community.cisco.com/t5/network-security/how-do-i-configure-asa-5520-to-send-snmp-trap-when-ip-sla/m-p/1913655#M456964</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can use the logging list feature to create a group of syslog messages that can be acted upon.&amp;nbsp; This group called sla-mon will only match the added|removed tracked route syslog messages.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;logging list sla-mon message 622001&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I usally use a group like this for email notifications as follows but you could use it to only send syslog messages that match this group.&amp;nbsp; Note that even if you use the "logging message &lt;MSG-NUMBER&gt; level warnings" command to move this message to the warning or another logging level, the mail program will only pick it up based on its original logging level (info for 622001).&amp;nbsp; Here is the full config:&lt;/MSG-NUMBER&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;logging list sla-mon message 622001&lt;/P&gt;&lt;P&gt; smtp-server &lt;EMAIL server="" ip=""&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/EMAIL&gt;&lt;/P&gt;&lt;P&gt;!&amp;nbsp; [ note that if you specify your own smtp server, no authentication is required if sending to your own domain ]&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;logging from-address &lt;/SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:ASA@domain.com"&gt;ASA@domain.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;logging recipient-address &lt;/SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:Recepient@domain.com"&gt;Recepient@domain.com&lt;/A&gt;&lt;SPAN&gt; level informational&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;logging mail sla-mon&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will only send 622001 messages to you by email.&amp;nbsp; If you have multiple tracked routes, however, it will send one for each route that is added/removed from the routing table each time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want to just send these messages to the syslog server, you can use the logging list in that setup.&amp;nbsp;&amp;nbsp; For a normal syslog setup that I use, I normally do something like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;logging enable&lt;/P&gt;&lt;P&gt;logging asdm warn&lt;/P&gt;&lt;P&gt;logging trap warn&lt;/P&gt;&lt;P&gt;logging host &lt;SYSLOG server=""&gt;&lt;/SYSLOG&gt;&lt;/P&gt;&lt;P&gt;logging message 622001 level warn&lt;/P&gt;&lt;P&gt;! This moves the tracked route added/removed message to the warning level and it will be sent to the syslog server.&lt;/P&gt;&lt;P&gt;logging message 111008 level warn&lt;/P&gt;&lt;P&gt;! This one is User &lt;USER&gt; executed the &lt;COMMAND&gt; command.&lt;/COMMAND&gt;&lt;/USER&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Oct 2012 19:28:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-do-i-configure-asa-5520-to-send-snmp-trap-when-ip-sla/m-p/1913655#M456964</guid>
      <dc:creator>ccordes</dc:creator>
      <dc:date>2012-10-12T19:28:34Z</dc:date>
    </item>
  </channel>
</rss>

