<?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 H/A split brain issues in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ftd-h-a-split-brain-issues/m-p/5292912#M1121119</link>
    <description>&lt;P&gt;It could be, can you ping across that link? Some other configuration issue? What version?&lt;/P&gt;</description>
    <pubDate>Thu, 22 May 2025 12:13:26 GMT</pubDate>
    <dc:creator>ahollifield</dc:creator>
    <dc:date>2025-05-22T12:13:26Z</dc:date>
    <item>
      <title>FTD H/A split brain issues</title>
      <link>https://community.cisco.com/t5/network-security/ftd-h-a-split-brain-issues/m-p/5292846#M1121114</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;A customer has around 20 H/A pairs of FTD 1010's that are managed by a cdFMC.&amp;nbsp; Recently I saw some alerts in the FMC saying "High availability is in split brain"&lt;/P&gt;
&lt;P&gt;When I Iogin to the FTD's and do a "show failover state", both FTD's says communication errors and they are both active. However, the failover interface is up on both firewalls and there is no switch between. It's only a cable directly connected on interface 1/8 between the two FTD's.&lt;/P&gt;
&lt;P&gt;Could it still be a cable issue even though both the status and the protocol is up when checking with "show interface IP brief" or could it be something else?&lt;/P&gt;
&lt;P&gt;When trying to do a deploy, I get the following error when deploying "Deployment is not possible for this HA pair as both units are active. Correct the failover link else try force breaking the HA pair."&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;/Chess&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 22 May 2025 07:34:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-h-a-split-brain-issues/m-p/5292846#M1121114</guid>
      <dc:creator>Chess Norris</dc:creator>
      <dc:date>2025-05-22T07:34:05Z</dc:date>
    </item>
    <item>
      <title>Re: FTD H/A split brain issues</title>
      <link>https://community.cisco.com/t5/network-security/ftd-h-a-split-brain-issues/m-p/5292912#M1121119</link>
      <description>&lt;P&gt;It could be, can you ping across that link? Some other configuration issue? What version?&lt;/P&gt;</description>
      <pubDate>Thu, 22 May 2025 12:13:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-h-a-split-brain-issues/m-p/5292912#M1121119</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2025-05-22T12:13:26Z</dc:date>
    </item>
    <item>
      <title>Re: FTD H/A split brain issues</title>
      <link>https://community.cisco.com/t5/network-security/ftd-h-a-split-brain-issues/m-p/5293173#M1121128</link>
      <description>&lt;P&gt;I discovered something really strange&lt;SPAN&gt;&amp;nbsp;on the primary FTD. We are using physical Ethernet1/1 and 1/2 as a port-channel. When doing a "show ip int brief", It says the port-channel is up but the physical interfaces are both down and unassociated.&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;Never seen this before. How can the port-channel be upp if the physical interfaces are down?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;firepower# show int ip brie&lt;BR /&gt;Interface IP-Address OK? Method Status Protocol&lt;BR /&gt;Internal-Data0/0 unassigned YES unset up up &lt;BR /&gt;Port-channel1 unassigned YES unset up up &lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Ethernet1/1 unassigned unassociated unset admin down down&lt;BR /&gt;Ethernet1/2 unassigned unassociated unset admin down down&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;/Chess&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 23 May 2025 08:02:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-h-a-split-brain-issues/m-p/5293173#M1121128</guid>
      <dc:creator>Chess Norris</dc:creator>
      <dc:date>2025-05-23T08:02:46Z</dc:date>
    </item>
    <item>
      <title>Re: FTD H/A split brain issues</title>
      <link>https://community.cisco.com/t5/network-security/ftd-h-a-split-brain-issues/m-p/5293189#M1121129</link>
      <description>&lt;P&gt;Hi, did you end up resolving this ?&lt;/P&gt;
&lt;P&gt;If so, how ?&lt;/P&gt;</description>
      <pubDate>Fri, 23 May 2025 09:06:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-h-a-split-brain-issues/m-p/5293189#M1121129</guid>
      <dc:creator>Tshepo</dc:creator>
      <dc:date>2025-05-23T09:06:41Z</dc:date>
    </item>
    <item>
      <title>Re: FTD H/A split brain issues</title>
      <link>https://community.cisco.com/t5/network-security/ftd-h-a-split-brain-issues/m-p/5293307#M1121132</link>
      <description>&lt;P&gt;TAC belive we are hitting the following defect&amp;nbsp;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwh17965" target="_self"&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwh17965&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The workaround was to delete and re-create the port-channel, but that's need to be done in FXOS. Normally we can only do configuration changes in FXOS on the bigger chassi firewalls (4100/9300) Smaller firewalls let us access FXOS, but we cannot do any changes to the configuration. However, TAC had a backdoor making it possible to commit changes in FXOS.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;/Chess&lt;/P&gt;</description>
      <pubDate>Fri, 23 May 2025 13:58:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-h-a-split-brain-issues/m-p/5293307#M1121132</guid>
      <dc:creator>Chess Norris</dc:creator>
      <dc:date>2025-05-23T13:58:57Z</dc:date>
    </item>
    <item>
      <title>Re: FTD H/A split brain issues</title>
      <link>https://community.cisco.com/t5/network-security/ftd-h-a-split-brain-issues/m-p/5293647#M1121142</link>
      <description>&lt;P&gt;Frightning ... LACP port-channeling must be a pretty new and experimental technology!&lt;/P&gt;</description>
      <pubDate>Mon, 26 May 2025 04:46:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-h-a-split-brain-issues/m-p/5293647#M1121142</guid>
      <dc:creator>Network Diver</dc:creator>
      <dc:date>2025-05-26T04:46:12Z</dc:date>
    </item>
  </channel>
</rss>

