<?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 FTD High Availability Failover using EtherChannel in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ftd-high-availability-failover-using-etherchannel/m-p/3216649#M1019645</link>
    <description>&lt;P&gt;I have 2 x FTD2110 managed by an FMCv, all v6.2.2. I'm trying to create an HA pair using an EtherChannel rather than a single physical link. However, only the physical interfaces are appearing in the dialog box to create the HA pair. The documentation states that &lt;EM&gt;"You can use any unused data interface (physical, redundant, or&amp;nbsp;EtherChannel) as the&amp;nbsp;failover&lt;/EM&gt;&lt;SPAN&gt;&lt;EM&gt;&amp;nbsp;link"&lt;/EM&gt;though. This is really simple to do with ASAs... what am I missing when it comes to FTDs? Thanks!&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 14:45:19 GMT</pubDate>
    <dc:creator>noisey_uk</dc:creator>
    <dc:date>2020-02-21T14:45:19Z</dc:date>
    <item>
      <title>FTD High Availability Failover using EtherChannel</title>
      <link>https://community.cisco.com/t5/network-security/ftd-high-availability-failover-using-etherchannel/m-p/3216649#M1019645</link>
      <description>&lt;P&gt;I have 2 x FTD2110 managed by an FMCv, all v6.2.2. I'm trying to create an HA pair using an EtherChannel rather than a single physical link. However, only the physical interfaces are appearing in the dialog box to create the HA pair. The documentation states that &lt;EM&gt;"You can use any unused data interface (physical, redundant, or&amp;nbsp;EtherChannel) as the&amp;nbsp;failover&lt;/EM&gt;&lt;SPAN&gt;&lt;EM&gt;&amp;nbsp;link"&lt;/EM&gt;though. This is really simple to do with ASAs... what am I missing when it comes to FTDs? Thanks!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 14:45:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-high-availability-failover-using-etherchannel/m-p/3216649#M1019645</guid>
      <dc:creator>noisey_uk</dc:creator>
      <dc:date>2020-02-21T14:45:19Z</dc:date>
    </item>
    <item>
      <title>Re: FTD High Availability Failover using EtherChannel</title>
      <link>https://community.cisco.com/t5/network-security/ftd-high-availability-failover-using-etherchannel/m-p/3216944#M1019646</link>
      <description>&lt;P&gt;Have you assigned an IP address to the Etherchannel first?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I don't have one to check but I believe some other posters reported success after having done that.&lt;/P&gt;</description>
      <pubDate>Wed, 15 Nov 2017 11:43:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-high-availability-failover-using-etherchannel/m-p/3216944#M1019646</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2017-11-15T11:43:34Z</dc:date>
    </item>
    <item>
      <title>Re: FTD High Availability Failover using EtherChannel</title>
      <link>https://community.cisco.com/t5/network-security/ftd-high-availability-failover-using-etherchannel/m-p/3216957#M1020153</link>
      <description>&lt;P&gt;Just tried it - no difference. Thanks for the suggestion though.&lt;/P&gt;</description>
      <pubDate>Wed, 15 Nov 2017 12:16:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-high-availability-failover-using-etherchannel/m-p/3216957#M1020153</guid>
      <dc:creator>noisey_uk</dc:creator>
      <dc:date>2017-11-15T12:16:24Z</dc:date>
    </item>
    <item>
      <title>Re: FTD High Availability Failover using EtherChannel</title>
      <link>https://community.cisco.com/t5/network-security/ftd-high-availability-failover-using-etherchannel/m-p/3217697#M1020154</link>
      <description>Just in case anyone else comes across this problem - ensure that you haven't named your Portchannel interface prior to creating the HA pair. If you have named your Portchannel, FMC thinks that it's unavailable for use as the HA link.</description>
      <pubDate>Thu, 16 Nov 2017 13:50:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-high-availability-failover-using-etherchannel/m-p/3217697#M1020154</guid>
      <dc:creator>noisey_uk</dc:creator>
      <dc:date>2017-11-16T13:50:15Z</dc:date>
    </item>
    <item>
      <title>Re: FTD High Availability Failover using EtherChannel</title>
      <link>https://community.cisco.com/t5/network-security/ftd-high-availability-failover-using-etherchannel/m-p/5047431#M1110265</link>
      <description>&lt;P&gt;Thank you&amp;nbsp;&lt;A id="link_41" class="lia-link-navigation lia-page-link lia-user-name-link" href="https://community.cisco.com/t5/user/viewprofilepage/user-id/321107" target="_self" aria-label="View Profile of noisey_uk"&gt;&lt;SPAN class=""&gt;noisey_uk.&lt;/SPAN&gt;&lt;/A&gt;&amp;nbsp;&lt;SPAN class=""&gt;Works for me.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Mar 2024 07:19:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-high-availability-failover-using-etherchannel/m-p/5047431#M1110265</guid>
      <dc:creator>dinos1979</dc:creator>
      <dc:date>2024-03-22T07:19:13Z</dc:date>
    </item>
    <item>
      <title>Re: FTD High Availability Failover using EtherChannel</title>
      <link>https://community.cisco.com/t5/network-security/ftd-high-availability-failover-using-etherchannel/m-p/5364161#M1124215</link>
      <description>&lt;P&gt;Don't give a logical name to the port-channel, and don't assign an IP address. Otherwise, FMC will see it as a used interface.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Jan 2026 08:39:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-high-availability-failover-using-etherchannel/m-p/5364161#M1124215</guid>
      <dc:creator>sinade101</dc:creator>
      <dc:date>2026-01-22T08:39:49Z</dc:date>
    </item>
  </channel>
</rss>

