<?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 ASA Failover issue in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-failover-issue/m-p/2051074#M438995</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Nitesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As you know ASA failover is based on the exchange of hello packets on the interfaces being monitored so both ASA's can detect if one of the devices is down.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now by default after an interface is down the mate will stop reciving hello packets from that peer and it will trigger failover.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In your case that is what happen, the status on one of the interfaces being monitored went down and failover was triggered.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rate all the helpful posts &lt;IMG ___jive_emoticon_name="wink" jivemacro="emoticon" src="https://community.cisco.com/4.5.4/images/tiny_mce3/plugins/jiveemoticons/images/spacer.gif" /&gt;&lt;SPAN __jive_emoticon_name="wink" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/tiny_mce3/plugins/jiveemoticons/images/spacer.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Julio&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 23 Aug 2012 18:40:26 GMT</pubDate>
    <dc:creator>Julio Carvajal</dc:creator>
    <dc:date>2012-08-23T18:40:26Z</dc:date>
    <item>
      <title>ASA Failover issue</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover-issue/m-p/2051073#M438994</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have configured Cisco ASA in Active/Standby mode. This firewall has been in production for more than 2 years and recently, there was a issue where both firewall went down. The reason was&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt; IFC Failure&lt;/STRONG&gt;&lt;/SPAN&gt; which was showing in show failover state and show failover history was showing "&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;Inferface Failure&lt;/STRONG&gt;&lt;/SPAN&gt;"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have gone through many documents but it doesnt clearly say what does it mean? This two sets have been in production for long time and suddenly this issue coming up is not making sense.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If some can help and guide it will be great.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nitesh&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 23:45:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover-issue/m-p/2051073#M438994</guid>
      <dc:creator>saxenanitesh8522</dc:creator>
      <dc:date>2019-03-11T23:45:44Z</dc:date>
    </item>
    <item>
      <title>ASA Failover issue</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover-issue/m-p/2051074#M438995</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Nitesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As you know ASA failover is based on the exchange of hello packets on the interfaces being monitored so both ASA's can detect if one of the devices is down.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now by default after an interface is down the mate will stop reciving hello packets from that peer and it will trigger failover.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In your case that is what happen, the status on one of the interfaces being monitored went down and failover was triggered.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rate all the helpful posts &lt;IMG ___jive_emoticon_name="wink" jivemacro="emoticon" src="https://community.cisco.com/4.5.4/images/tiny_mce3/plugins/jiveemoticons/images/spacer.gif" /&gt;&lt;SPAN __jive_emoticon_name="wink" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/tiny_mce3/plugins/jiveemoticons/images/spacer.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Julio&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Aug 2012 18:40:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover-issue/m-p/2051074#M438995</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2012-08-23T18:40:26Z</dc:date>
    </item>
  </channel>
</rss>

