<?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 Cisco ASA Failover Link Redundancy in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/cisco-asa-failover-link-redundancy/m-p/3747266#M8924</link>
    <description>&lt;P&gt;Hi folks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;at one of my customer´s sites I was confronted with a split brain ASA failover situation. Unfortunately the SFP of the failover link was broken. Both firewalls did not "see" each other while the failover link was broken.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I did not find a solution to eliminate this single point of failure. I tried to use a Port-Channel as failover interface but the command was rejected by ASA.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there any chance to get the failover interface set up redundant?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Simon&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 16:28:27 GMT</pubDate>
    <dc:creator>Simon Rittner</dc:creator>
    <dc:date>2020-02-21T16:28:27Z</dc:date>
    <item>
      <title>Cisco ASA Failover Link Redundancy</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-failover-link-redundancy/m-p/3747266#M8924</link>
      <description>&lt;P&gt;Hi folks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;at one of my customer´s sites I was confronted with a split brain ASA failover situation. Unfortunately the SFP of the failover link was broken. Both firewalls did not "see" each other while the failover link was broken.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I did not find a solution to eliminate this single point of failure. I tried to use a Port-Channel as failover interface but the command was rejected by ASA.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there any chance to get the failover interface set up redundant?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Simon&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 16:28:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-failover-link-redundancy/m-p/3747266#M8924</guid>
      <dc:creator>Simon Rittner</dc:creator>
      <dc:date>2020-02-21T16:28:27Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA Failover Link Redundancy</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-failover-link-redundancy/m-p/3747365#M8926</link>
      <description>&lt;P&gt;Which ASA software version are you using? In newer versions, EtherChannels should work for the FO-link.&lt;/P&gt;
&lt;P&gt;Instead of using a channel, you can also configure the redundant interfaces for this link:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/asa/asa94/config-guides/cli/general/asa-94-general-config/interface-echannel.html#ID-2077-000000af" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/asa/asa94/config-guides/cli/general/asa-94-general-config/interface-echannel.html#ID-2077-000000af&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Nov 2018 13:18:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-failover-link-redundancy/m-p/3747365#M8926</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2018-11-15T13:18:27Z</dc:date>
    </item>
  </channel>
</rss>

