<?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 Failover triggers on ASA in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/failover-triggers-on-asa/m-p/1955080#M439300</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The ASA sends kind of hello-packets on all interfaces (you can control which interfaces should be monitored). These hellos need to reach the other unit. If they don't, the ASAs try to find out which unit is better connected to the network. That device gets active.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The inteface status is only one criteria that gets tested.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the following document are some example when and when not a failover happens:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/ha_active_standby.html#wp1079547"&gt;http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/ha_active_standby.html#wp1079547&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also relevant to your question is the Health monitoring:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/ha_overview.html#wp1079010"&gt;http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/ha_overview.html#wp1079010&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--&amp;nbsp; &lt;BR /&gt;Don't stop after you've improved your network! Improve the world by lending money to the working poor: &lt;BR /&gt;&lt;A class="jive-link-external-small" href="http://www.kiva.org/invitedby/karsteni"&gt;http://www.kiva.org/invitedby/karsteni&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 09 Aug 2012 21:20:42 GMT</pubDate>
    <dc:creator>Karsten Iwen</dc:creator>
    <dc:date>2012-08-09T21:20:42Z</dc:date>
    <item>
      <title>Failover triggers on ASA</title>
      <link>https://community.cisco.com/t5/network-security/failover-triggers-on-asa/m-p/1955079#M439299</link>
      <description>&lt;P&gt;Hi guys:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I got a question regarding on how the failover activate, as far as I know there are only 3 ways to trigger the failover:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.- With the command "no failover active" on the Active device.&lt;/P&gt;&lt;P&gt;2.- If one of the interfaces (INSIDE/OUTSIDE) is down.&lt;/P&gt;&lt;P&gt;3.- If the device goes down.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any other reason that could trigger the failover? I mean if I got configured some vlans and they are monitored if some of those vlans goes down the failover will trigger?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The reason I'm asking you this is because I'm doing some test with the failovers, there're 2 switches that are connected to the ASA primary and secondary, If I shutdown the interfaces that are connected to the other switches on the LAN but the interfaces that goes to the firewall (INSIDE/OUTSIDE) are not shutdown the failover are not triggered, I guess is because these interfaces are still up. Is this ok or not?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 23:40:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-triggers-on-asa/m-p/1955079#M439299</guid>
      <dc:creator>Luis Carranza</dc:creator>
      <dc:date>2019-03-11T23:40:25Z</dc:date>
    </item>
    <item>
      <title>Failover triggers on ASA</title>
      <link>https://community.cisco.com/t5/network-security/failover-triggers-on-asa/m-p/1955080#M439300</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The ASA sends kind of hello-packets on all interfaces (you can control which interfaces should be monitored). These hellos need to reach the other unit. If they don't, the ASAs try to find out which unit is better connected to the network. That device gets active.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The inteface status is only one criteria that gets tested.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the following document are some example when and when not a failover happens:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/ha_active_standby.html#wp1079547"&gt;http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/ha_active_standby.html#wp1079547&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also relevant to your question is the Health monitoring:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/ha_overview.html#wp1079010"&gt;http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/ha_overview.html#wp1079010&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--&amp;nbsp; &lt;BR /&gt;Don't stop after you've improved your network! Improve the world by lending money to the working poor: &lt;BR /&gt;&lt;A class="jive-link-external-small" href="http://www.kiva.org/invitedby/karsteni"&gt;http://www.kiva.org/invitedby/karsteni&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Aug 2012 21:20:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-triggers-on-asa/m-p/1955080#M439300</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2012-08-09T21:20:42Z</dc:date>
    </item>
  </channel>
</rss>

