<?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 PA-VM HA Clustering architecture in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/pa-vm-ha-clustering-architecture/m-p/508159#M194</link>
    <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are working to deploy 4xPA-VM 300 firewalls in our 2 DCs. We would like to have a pair of Active/Passive firewalls in each DC. We would then want these 4 firewalls to be in a cluster as well.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Our objective is to have complete redundancy across DCs and intra-DC as well, but these firewalls to work as logically same firewalls and achieve the horizontal scaling scaling as well. Since both the DCs, although diff locations act as a single DC due to common IP addressing and the virtual environment.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am looking for some configuration steps or architecture around HA clustering. How does the IP addressing on these physicall different but logically same firewalls work? Would we need to create a Virtual IP that at as a gateway for the network to send the traffic to and then the 2 active/passive pairs in cluster load-balance it?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;How does clustering work in case of failures, is there a concept of floating/virtual IPs in it or would I need different IP addressing on the HA pairs in each DC.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any help would be appreciated, couldn't find much in Palo docs except how to configure it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;regards,&lt;/P&gt;
&lt;P&gt;V&lt;/P&gt;</description>
    <pubDate>Thu, 07 Jul 2022 05:15:55 GMT</pubDate>
    <dc:creator>varunrao8</dc:creator>
    <dc:date>2022-07-07T05:15:55Z</dc:date>
    <item>
      <title>PA-VM HA Clustering architecture</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/pa-vm-ha-clustering-architecture/m-p/508159#M194</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are working to deploy 4xPA-VM 300 firewalls in our 2 DCs. We would like to have a pair of Active/Passive firewalls in each DC. We would then want these 4 firewalls to be in a cluster as well.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Our objective is to have complete redundancy across DCs and intra-DC as well, but these firewalls to work as logically same firewalls and achieve the horizontal scaling scaling as well. Since both the DCs, although diff locations act as a single DC due to common IP addressing and the virtual environment.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am looking for some configuration steps or architecture around HA clustering. How does the IP addressing on these physicall different but logically same firewalls work? Would we need to create a Virtual IP that at as a gateway for the network to send the traffic to and then the 2 active/passive pairs in cluster load-balance it?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;How does clustering work in case of failures, is there a concept of floating/virtual IPs in it or would I need different IP addressing on the HA pairs in each DC.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any help would be appreciated, couldn't find much in Palo docs except how to configure it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;regards,&lt;/P&gt;
&lt;P&gt;V&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jul 2022 05:15:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/pa-vm-ha-clustering-architecture/m-p/508159#M194</guid>
      <dc:creator>varunrao8</dc:creator>
      <dc:date>2022-07-07T05:15:55Z</dc:date>
    </item>
  </channel>
</rss>

