<?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: SNMPtrap delay in sending for ASA in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/snmptrap-delay-in-sending-for-asa/m-p/3204206#M1065278</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/254261"&gt;@seanwaite&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;with SNMP traps probably you can´t.&amp;nbsp; However, Netflow allows this with the command "&lt;SPAN&gt;flow-export delay flow-create 10". Make sure Netflow has the trap you need and give it a try.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;-If I helped you somehow, please, rate it as useful.-&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 24 Oct 2017 13:43:39 GMT</pubDate>
    <dc:creator>Flavio Miranda</dc:creator>
    <dc:date>2017-10-24T13:43:39Z</dc:date>
    <item>
      <title>SNMPtrap delay in sending for ASA</title>
      <link>https://community.cisco.com/t5/network-security/snmptrap-delay-in-sending-for-asa/m-p/3204132#M1065277</link>
      <description>&lt;P&gt;I am trying find a solution to having snmp trap sent from the ASA, but delayed by 1-2 minutes after the event that triggered.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Background- The ASA is using SLA feature providing redundant backup on 2nd interface connecting to a cellular modem. The ASA is remote tunneling back to me where NMS\trap receiver &amp;amp; server monitors remote devices as well as the ASA itself. I have configured syslog monitor for event&amp;nbsp;&lt;SPAN&gt;622001 and snmp to send syslog. However when an interface goes down, the trap is instantaneous where as there is a delay in both the SLA to switch to the backup interface, and for the tunnel to reconnect through that backup. I have configured a snmp host in lab here that is outside the tunnel so I am no longer necessarily dependent&amp;nbsp;on that being up&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;In short, I need an alarm, just cant be sent instantly&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 14:33:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/snmptrap-delay-in-sending-for-asa/m-p/3204132#M1065277</guid>
      <dc:creator>seanwaite</dc:creator>
      <dc:date>2020-02-21T14:33:27Z</dc:date>
    </item>
    <item>
      <title>Re: SNMPtrap delay in sending for ASA</title>
      <link>https://community.cisco.com/t5/network-security/snmptrap-delay-in-sending-for-asa/m-p/3204206#M1065278</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/254261"&gt;@seanwaite&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;with SNMP traps probably you can´t.&amp;nbsp; However, Netflow allows this with the command "&lt;SPAN&gt;flow-export delay flow-create 10". Make sure Netflow has the trap you need and give it a try.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;-If I helped you somehow, please, rate it as useful.-&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Oct 2017 13:43:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/snmptrap-delay-in-sending-for-asa/m-p/3204206#M1065278</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2017-10-24T13:43:39Z</dc:date>
    </item>
  </channel>
</rss>

