<?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: HA Failover Issue on PA-3420 with AE LACP – Both Nodes Active (Split Brain ?) in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ha-failover-issue-on-pa-3420-with-ae-lacp-both-nodes-active/m-p/1229170#M124306</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/958952627"&gt;@romen54&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Did this start out of the blue or after you applied 11.1.6-h3? I've had multiple instances where recent PAN-OS releases have caused a split-brain scenario and reverting has immediately resolved the issue across multiple different models in active/passive setups. &lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As for the LACP issue causing a split-brain scenario, I think your LACP issues are more than likely a consequence of your split-brain scenario than the issue causing your split-brain scenario. Do you have HA1/HA2 directly connected between the two units or are you passing it through a switch? If you're passing it through a switch, is it the same one handling your aggregates? &lt;/P&gt;</description>
    <pubDate>Thu, 15 May 2025 16:58:34 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2025-05-15T16:58:34Z</dc:date>
    <item>
      <title>HA Failover Issue on PA-3420 with AE LACP – Both Nodes Active (Split Brain ?)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ha-failover-issue-on-pa-3420-with-ae-lacp-both-nodes-active/m-p/1229039#M124288</link>
      <description>&lt;P&gt;We’re experiencing a critical issue with our HA setup on a pair of Palo Alto PA‑3420 firewalls running PAN‑OS 11.1.6‑h3 in Active‑Passive mode (HA Group 25, preemptive disabled). Both firewalls simultaneously believed they were active, causing a complete traffic halt and requiring a manual reboot of the actual active node to restore service. We suspect the problem is tied to our LACP configuration on AE-group ae1 (aggregating Ethernet1/13–16 with LACP in fast mode). Logs indicate that interfaces were being moved out of the AE-group due to link down events, and there were HA sync issues (Can't synchronize control plane data). We’ve verified cabling, switch configuration, and LACP status (ports show collecting/distributing when stable). Our HA settings and IPs are correctly matched, and we’re using a PSK for HA communication. We’re looking for guidance on how to stabilize LACP and prevent AE-group flapping from affecting HA, whether there are known bugs in PAN-OS 11.1.6-h3 related to HA or LACP, and any best practices to ensure HA state remains consistent during link transitions. Any insights or suggestions would be greatly appreciated.&lt;/P&gt;</description>
      <pubDate>Thu, 15 May 2025 12:09:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ha-failover-issue-on-pa-3420-with-ae-lacp-both-nodes-active/m-p/1229039#M124288</guid>
      <dc:creator>romen54</dc:creator>
      <dc:date>2025-05-15T12:09:31Z</dc:date>
    </item>
    <item>
      <title>Re: HA Failover Issue on PA-3420 with AE LACP – Both Nodes Active (Split Brain ?)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ha-failover-issue-on-pa-3420-with-ae-lacp-both-nodes-active/m-p/1229163#M124302</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/958952627"&gt;@romen54&lt;/a&gt;&amp;nbsp;Did you checked &lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u0000004OPJCA2&amp;amp;lang=en_US%E2%80%A9" target="_self"&gt;this&lt;/A&gt; article? This will help to check all the causes and resolutions of Split-Brain situation.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 15 May 2025 13:21:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ha-failover-issue-on-pa-3420-with-ae-lacp-both-nodes-active/m-p/1229163#M124302</guid>
      <dc:creator>SutareMayur</dc:creator>
      <dc:date>2025-05-15T13:21:35Z</dc:date>
    </item>
    <item>
      <title>Re: HA Failover Issue on PA-3420 with AE LACP – Both Nodes Active (Split Brain ?)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ha-failover-issue-on-pa-3420-with-ae-lacp-both-nodes-active/m-p/1229170#M124306</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/958952627"&gt;@romen54&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Did this start out of the blue or after you applied 11.1.6-h3? I've had multiple instances where recent PAN-OS releases have caused a split-brain scenario and reverting has immediately resolved the issue across multiple different models in active/passive setups. &lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As for the LACP issue causing a split-brain scenario, I think your LACP issues are more than likely a consequence of your split-brain scenario than the issue causing your split-brain scenario. Do you have HA1/HA2 directly connected between the two units or are you passing it through a switch? If you're passing it through a switch, is it the same one handling your aggregates? &lt;/P&gt;</description>
      <pubDate>Thu, 15 May 2025 16:58:34 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ha-failover-issue-on-pa-3420-with-ae-lacp-both-nodes-active/m-p/1229170#M124306</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2025-05-15T16:58:34Z</dc:date>
    </item>
  </channel>
</rss>

