<?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: ASA Failover in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-failover/m-p/1260392#M857933</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;but the failover interfaces are monitored, so if I put the threshold on 1 no ASA will be active.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 02 Oct 2009 12:52:36 GMT</pubDate>
    <dc:creator>fvanlancker</dc:creator>
    <dc:date>2009-10-02T12:52:36Z</dc:date>
    <item>
      <title>ASA Failover</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover/m-p/1260386#M857919</link>
      <description>&lt;P&gt;If an ASA has lan failover and statefull crossover-cables connected without an intermediate switch. If one ASA goes down the other asa senses two links are down, will this be an issue ? In the cisco the second edition of the firewall handbook it is a tip not to connect the back to back but it does not say what happens in a real situation.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 16:22:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover/m-p/1260386#M857919</guid>
      <dc:creator>fvanlancker</dc:creator>
      <dc:date>2019-03-11T16:22:02Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Failover</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover/m-p/1260387#M857922</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Each interface should connect to a switch port so that the link status is always up to one firewall interface if the other firewall interface fails. Otherwise, both units sense a link-down condition and assume that their own interfaces have a failure.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Oct 2009 15:18:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover/m-p/1260387#M857922</guid>
      <dc:creator>Collin Clark</dc:creator>
      <dc:date>2009-10-01T15:18:38Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Failover</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover/m-p/1260388#M857923</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Collin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the info, but do you think that the statefull en Lan link are also monitored ? There is certainly no option to monitor them.&lt;/P&gt;&lt;P&gt;And what if switch would fail ? Will both asa's become active ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Oct 2009 15:22:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover/m-p/1260388#M857923</guid>
      <dc:creator>fvanlancker</dc:creator>
      <dc:date>2009-10-01T15:22:06Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Failover</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover/m-p/1260389#M857925</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You typically attach each ASA to a different switch for full redundancy. The failover link is inherently monitored because that link is where the majority of failover communications occur. If that link fails, then each ASA thinks it's primary.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Oct 2009 15:26:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover/m-p/1260389#M857925</guid>
      <dc:creator>Collin Clark</dc:creator>
      <dc:date>2009-10-01T15:26:21Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Failover</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover/m-p/1260390#M857927</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Assume:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;a:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2 ASA connected via 2 failover interfaces in active/standby configuration. The secondary ASA goes down.&lt;/P&gt;&lt;P&gt;What happens ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;b: Same scenario but the primary goes down.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;c: They both go down and come back up again,but the secondary is first. How will te switches mac-address tables and the routers handle their arp table ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Oct 2009 12:20:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover/m-p/1260390#M857927</guid>
      <dc:creator>fvanlancker</dc:creator>
      <dc:date>2009-10-02T12:20:53Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Failover</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover/m-p/1260391#M857929</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;a. Nothing really. The primary still thinks it's primary and continues to pass traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;b. Once the heartbeat fails (2 times I believe) the secondary becomes primary and starts passing traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;c. The ARP tables will be empty because of the ASA outage so when the ASAs come back up, the switch will populate their ARP tables as normal. Since the 2nd ASA comes up first, it will be primary. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Oct 2009 12:33:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover/m-p/1260391#M857929</guid>
      <dc:creator>Collin Clark</dc:creator>
      <dc:date>2009-10-02T12:33:27Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Failover</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover/m-p/1260392#M857933</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;but the failover interfaces are monitored, so if I put the threshold on 1 no ASA will be active.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Oct 2009 12:52:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover/m-p/1260392#M857933</guid>
      <dc:creator>fvanlancker</dc:creator>
      <dc:date>2009-10-02T12:52:36Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Failover</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover/m-p/1260393#M857936</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;They both think they are active. They both want to be active. The active keeps telling the secondary to 'stand down, I'm in charge right now.' The standby keeps waiting and wanting to be in charge. As soon as it doesn't here from the one in charge, it takes over and assumes the role.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Oct 2009 12:57:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover/m-p/1260393#M857936</guid>
      <dc:creator>Collin Clark</dc:creator>
      <dc:date>2009-10-02T12:57:10Z</dc:date>
    </item>
  </channel>
</rss>

