<?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: Panorama HA Config question in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/panorama-ha-config-question/m-p/307525#M79872</link>
    <description>&lt;P&gt;you cant use the same template for hostname, ip and HA (priority)&amp;nbsp; for both members as that would cause a conflict, so there are 2 options:&lt;/P&gt;&lt;P&gt;- you create a unique template for each member that contains it's HA config, ip and hostname, or&lt;/P&gt;&lt;P&gt;- you dont include these parameters in the template and configure them locally&lt;/P&gt;</description>
    <pubDate>Wed, 22 Jan 2020 08:38:06 GMT</pubDate>
    <dc:creator>reaper</dc:creator>
    <dc:date>2020-01-22T08:38:06Z</dc:date>
    <item>
      <title>Panorama HA Config question</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/panorama-ha-config-question/m-p/307512#M79868</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Quick question on my new deployment for Panorama. I have a HA pair with unique hostnames and IP addresses with firewall as an active passive pair. The migration steps state the following:&lt;/P&gt;&lt;P&gt;Do not combine the HA firewall pair in to a single template if a unique Hostname, management IP address, or HA configuration is configured for each HA peer. You may also configure a unique Hostname, management IP address, or HA configuration locally on the firewalls.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What do I need to do to accommodate this? I may be having a "stupid" moment but the documentation is not 100% clear (bad night and 6.30am). Using this document:&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/panorama/8-1/panorama-admin/manage-firewalls/transition-a-firewall-to-panorama-management/migrate-a-firewall-ha-pair-to-panorama-management.html#id177DF10905Z" target="_blank"&gt;https://docs.paloaltonetworks.com/panorama/8-1/panorama-admin/manage-firewalls/transition-a-firewall-to-panorama-management/migrate-a-firewall-ha-pair-to-panorama-management.html#id177DF10905Z&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Adrian&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jan 2020 07:16:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/panorama-ha-config-question/m-p/307512#M79868</guid>
      <dc:creator>a.jones</dc:creator>
      <dc:date>2020-01-22T07:16:02Z</dc:date>
    </item>
    <item>
      <title>Re: Panorama HA Config question</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/panorama-ha-config-question/m-p/307525#M79872</link>
      <description>&lt;P&gt;you cant use the same template for hostname, ip and HA (priority)&amp;nbsp; for both members as that would cause a conflict, so there are 2 options:&lt;/P&gt;&lt;P&gt;- you create a unique template for each member that contains it's HA config, ip and hostname, or&lt;/P&gt;&lt;P&gt;- you dont include these parameters in the template and configure them locally&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jan 2020 08:38:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/panorama-ha-config-question/m-p/307525#M79872</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2020-01-22T08:38:06Z</dc:date>
    </item>
  </channel>
</rss>

