<?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: FTD Failover Link Recommendations in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ftd-failover-link-recommendations/m-p/5243291#M1118575</link>
    <description>&lt;P&gt;Can I know SW form VSS or vPC or stack wise virtual?&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
    <pubDate>Sat, 04 Jan 2025 11:34:20 GMT</pubDate>
    <dc:creator>MHM Cisco World</dc:creator>
    <dc:date>2025-01-04T11:34:20Z</dc:date>
    <item>
      <title>FTD Failover Link Recommendations</title>
      <link>https://community.cisco.com/t5/network-security/ftd-failover-link-recommendations/m-p/5243283#M1118572</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I'm currently implementing a pair of Cisco 3130 FTDs in active/stanby HA. The firewalls will be located within the same campus site but in different buildings. I'm trying to determine the recommendations and best practises for the failover link. My initial plan was to connect the firewalls back-to-back using a single 10G LR link (which I have done for other deployments without any issues), however in this instance I've been advised to either use a back-to-back port-channel, with each fibre link taking a seperate path for increased availability, or by connecting a single failover link via our inside or outside switch infrastrucutre, so an indirect failover link.&lt;/P&gt;&lt;P&gt;Is there a general recommendation or best practise for FTD failover connectivity that I should be following?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 04 Jan 2025 10:53:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-failover-link-recommendations/m-p/5243283#M1118572</guid>
      <dc:creator>packet2020</dc:creator>
      <dc:date>2025-01-04T10:53:36Z</dc:date>
    </item>
    <item>
      <title>Re: FTD Failover Link Recommendations</title>
      <link>https://community.cisco.com/t5/network-security/ftd-failover-link-recommendations/m-p/5243287#M1118573</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1304848"&gt;@packet2020&lt;/a&gt; using an Etherchannel via different paths for the failover link would be sensible. The failover link can also be shared with the stateful failover link. Sharing a failover link is the best way to conserve interfaces, but consider a dedicated interface for the state link and failover link, if you have a large configuration and a high traffic network.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This are the different scenarios&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="RobIngram_0-1735988615962.png" style="width: 651px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/236923i21FC87F867DA3340/image-dimensions/651x627?v=v2" width="651" height="627" role="button" title="RobIngram_0-1735988615962.png" alt="RobIngram_0-1735988615962.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;The Cisco guides covers each option &lt;A href="https://www.cisco.com/c/en/us/td/docs/security/secure-firewall/management-center/device-config/760/management-center-device-config-76/high-availability.html#ID-2107-00000039" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/secure-firewall/management-center/device-config/760/management-center-device-config-76/high-availability.html#ID-2107-00000039&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 04 Jan 2025 11:05:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-failover-link-recommendations/m-p/5243287#M1118573</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2025-01-04T11:05:58Z</dc:date>
    </item>
    <item>
      <title>Re: FTD Failover Link Recommendations</title>
      <link>https://community.cisco.com/t5/network-security/ftd-failover-link-recommendations/m-p/5243291#M1118575</link>
      <description>&lt;P&gt;Can I know SW form VSS or vPC or stack wise virtual?&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Sat, 04 Jan 2025 11:34:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-failover-link-recommendations/m-p/5243291#M1118575</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2025-01-04T11:34:20Z</dc:date>
    </item>
    <item>
      <title>Re: FTD Failover Link Recommendations</title>
      <link>https://community.cisco.com/t5/network-security/ftd-failover-link-recommendations/m-p/5243309#M1118577</link>
      <description>&lt;P&gt;The switches that the FTDs connect to are independant, so we have core switch 1 and core switch 2 that are connected togther using a trunk, with FTD1 connected only to core switch 1 and FTD2 connected only to core switch 2. We generally dont use VSS/SWV in the core/critical parts of our network&lt;/P&gt;</description>
      <pubDate>Sat, 04 Jan 2025 13:13:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-failover-link-recommendations/m-p/5243309#M1118577</guid>
      <dc:creator>packet2020</dc:creator>
      <dc:date>2025-01-04T13:13:24Z</dc:date>
    </item>
  </channel>
</rss>

