<?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>article Nominated Discussion: Palo Alto Cluster Questions in General Articles</title>
    <link>https://live.paloaltonetworks.com/t5/general-articles/nominated-discussion-palo-alto-cluster-questions/ta-p/547093</link>
    <description>&lt;DIV class="lia-message-template-content-zone"&gt;
&lt;P&gt;&lt;SPAN&gt;This Nominated Discussion Article is based on the post "&lt;/SPAN&gt;&lt;A href="https://live.paloaltonetworks.com/t5/general-topics/palo-alto-cluster-questions/m-p/546417" target="_blank" rel="noopener"&gt;Palo Alto Cluster Questions&lt;/A&gt;&lt;SPAN&gt;" by&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/295274"&gt;@gongya&lt;/a&gt;&amp;nbsp;&amp;nbsp;and&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;answered by&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/70130"&gt;@aleksandar.astardzhiev&lt;/a&gt;&amp;nbsp;. Read on to see his response!&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P&gt;1. Palo Alto HA Sync links can be on different networks ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; HA1 seems not&amp;nbsp; "&lt;SPAN&gt;The HA1 IP address for both peers must be on the same subnet if they are directly connected or are connected to the same switch."&amp;nbsp; But like to confirm. I saw the gateway configuration for those links.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; HA2 seems possible, "Use Layer 3 only if the HA2 connection must communicate over a routed network."&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;2. Can 2 Palo Alto nodes be standalone with sessions synced ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;thanks !!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Response:&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/295274"&gt;@gongya&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;Q: Can HA1 be on different networks?&lt;/P&gt;
&lt;P&gt;A: Yes it can. HA1 is control link - it is used for keepaliaves and hellos, also for config sync. As you can see from the docs it is actually requiring to enter local and peer IP and network. If the members are in different networks you need to specify gateway as well - &lt;A href="https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-web-interface-help/device/device-high-availability/configure-ha-settings" target="_blank" rel="noopener"&gt;https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-web-interface-help/device/device-high-availability/configure-ha-settings&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;HA2 is the data link - it is used for session sync. By default this link is set to "Ethernet" for&amp;nbsp; transport type. This can only be used if FWs are connected directly or&amp;nbsp; at least in the same layer2 broadcast. However you can config the transport to use IP or UDP, which should&amp;nbsp; allow you to have HA2 in different networks. Default is ethernet, because it&amp;nbsp; is always recommended to have high-speed reliable connection for session sync, but you can change it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Q: Can 2 Palo Alto nodes be standalone with sessions synced ?&lt;/P&gt;
&lt;P&gt;A: Depends...PAN call this "HA Clustering" (which for me is little confusing with standard active/passive). It was introduced fairly recently - &lt;A href="https://docs.paloaltonetworks.com/pan-os/10-1/pan-os-admin/high-availability/ha-clustering-overview" target="_blank" rel="noopener"&gt;https://docs.paloaltonetworks.com/pan-os/10-1/pan-os-admin/high-availability/ha-clustering-overview&lt;/A&gt; It is supported only of some physical devices and not on public cloud platforms.&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;/DIV&gt;</description>
    <pubDate>Tue, 15 Aug 2023 18:04:35 GMT</pubDate>
    <dc:creator>JayGolf</dc:creator>
    <dc:date>2023-08-15T18:04:35Z</dc:date>
    <item>
      <title>Nominated Discussion: Palo Alto Cluster Questions</title>
      <link>https://live.paloaltonetworks.com/t5/general-articles/nominated-discussion-palo-alto-cluster-questions/ta-p/547093</link>
      <description>&lt;P&gt;&lt;SPAN&gt;This Nominated Discussion Article is based on the post "&lt;/SPAN&gt;&lt;A href="https://live.paloaltonetworks.com/t5/general-topics/palo-alto-cluster-questions/m-p/546417" target="_blank" rel="noopener"&gt;Palo Alto Cluster Questions&lt;/A&gt;&lt;SPAN&gt;".&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Aug 2023 18:04:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-articles/nominated-discussion-palo-alto-cluster-questions/ta-p/547093</guid>
      <dc:creator>JayGolf</dc:creator>
      <dc:date>2023-08-15T18:04:35Z</dc:date>
    </item>
    <item>
      <title>Re: Nominated Discussion: Palo Alto Cluster Questions</title>
      <link>https://live.paloaltonetworks.com/t5/general-articles/nominated-discussion-palo-alto-cluster-questions/tac-p/587190#M713</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I have two different geolocation DCs and I want to stretch my 5200 Cluters (Active / Active) on both sites.&lt;/P&gt;&lt;P&gt;I can't find any clear document about link requirements between cluster nodes.&lt;/P&gt;&lt;P&gt;I have to know first&amp;nbsp; The maximum allowed link latency and any limitations if I have only&amp;nbsp; L3 connection between my sites do I have to provide any l2 connection for ha1/ha2/ha3 links?&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Amirreza&lt;/P&gt;</description>
      <pubDate>Sat, 18 May 2024 14:13:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-articles/nominated-discussion-palo-alto-cluster-questions/tac-p/587190#M713</guid>
      <dc:creator>AmirReza</dc:creator>
      <dc:date>2024-05-18T14:13:38Z</dc:date>
    </item>
  </channel>
</rss>

