<?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: FirePower Cluster Question in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firepower-cluster-question/m-p/4928090#M1104480</link>
    <description>&lt;P&gt;You meaning interconnect both cluster FW.&lt;/P&gt;</description>
    <pubDate>Sat, 23 Sep 2023 08:57:12 GMT</pubDate>
    <dc:creator>MHM Cisco World</dc:creator>
    <dc:date>2023-09-23T08:57:12Z</dc:date>
    <item>
      <title>FirePower Cluster Question</title>
      <link>https://community.cisco.com/t5/network-security/firepower-cluster-question/m-p/4927997#M1104477</link>
      <description>&lt;P&gt;I'm in the process of adding more switches to support the FTD 3140 Cluster.&amp;nbsp; Here's the question, won't the Firepower devices go down if the switches that it's connected to also goes down?&amp;nbsp; Wouldn't that make the Switches (even more importantly, the connections as well, if they go down) that it's connected to as a single point of failure?&amp;nbsp; Why won't Cisco support direct connect Clustering or even better Direct connect clustering as well as connected through a switch?&amp;nbsp; That way if one of the Clustered devices go down, you'll still have the Switches to uphold the line protocol and if the connections to the switches or the switches themselves go down, the Cluster will survive.&lt;/P&gt;&lt;P&gt;For instance,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cluster Mem A port1 --&amp;gt;C9500--&amp;gt;Cluster Mem B port1&lt;/P&gt;&lt;P&gt;Cluster Mem A port2 --&amp;gt;C9500--&amp;gt;Cluster Mem B port2&lt;/P&gt;&lt;P&gt;Cluster Mem A port3 --&amp;gt;Cluster Mem B port3&lt;/P&gt;&lt;P&gt;Cluster Mem A port4 --&amp;gt;Cluster Mem B port4&lt;/P&gt;&lt;P&gt;To me, that makes 10x more sense than the current setup.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Sep 2023 20:44:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-cluster-question/m-p/4927997#M1104477</guid>
      <dc:creator>red2play</dc:creator>
      <dc:date>2023-09-22T20:44:17Z</dc:date>
    </item>
    <item>
      <title>Re: FirePower Cluster Question</title>
      <link>https://community.cisco.com/t5/network-security/firepower-cluster-question/m-p/4928088#M1104479</link>
      <description>&lt;P&gt;Most of the use case have Dual Switches they are part of VSS or SVL or Stack or vPC&lt;/P&gt;
&lt;P&gt;So if you looking more failure scenario&amp;nbsp; adding more Links to Dual switch is appropriate rather a singe device.&lt;/P&gt;
&lt;P&gt;If all the devices in same place next each other (that is another drawback if the single comm room power failure) - so cluster streched in different place (if one can invest dark fiber between cluster that is good idea - depends on use case and cost )&lt;/P&gt;
&lt;P&gt;more guide lines can be find here :&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/firepower/fxos/clustering/ftd-4100-9300-cluster.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/firepower/fxos/clustering/ftd-4100-9300-cluster.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 23 Sep 2023 08:37:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-cluster-question/m-p/4928088#M1104479</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2023-09-23T08:37:06Z</dc:date>
    </item>
    <item>
      <title>Re: FirePower Cluster Question</title>
      <link>https://community.cisco.com/t5/network-security/firepower-cluster-question/m-p/4928090#M1104480</link>
      <description>&lt;P&gt;You meaning interconnect both cluster FW.&lt;/P&gt;</description>
      <pubDate>Sat, 23 Sep 2023 08:57:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-cluster-question/m-p/4928090#M1104480</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-09-23T08:57:12Z</dc:date>
    </item>
  </channel>
</rss>

