<?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: Hardware failure recovery in  an HA pair in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/hardware-failure-recovery-in-an-ha-pair/m-p/244266#M69725</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/15603"&gt;@Raido_Rattameister&lt;/a&gt;&lt;/P&gt;&lt;P&gt;Yes I would assume that the secondary would take over to, this hasn't actually happened I was thinking about the best way to deal with it. So you would let the secondary sync to the new hardware?&lt;/P&gt;&lt;P&gt;No panorama&lt;/P&gt;</description>
    <pubDate>Fri, 21 Dec 2018 16:11:55 GMT</pubDate>
    <dc:creator>jdprovine</dc:creator>
    <dc:date>2018-12-21T16:11:55Z</dc:date>
    <item>
      <title>Hardware failure recovery in  an HA pair</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/hardware-failure-recovery-in-an-ha-pair/m-p/244251#M69717</link>
      <description>&lt;P&gt;What is the best way to recover the primary PA 5050 if the hardware completely dies?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Dec 2018 14:41:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/hardware-failure-recovery-in-an-ha-pair/m-p/244251#M69717</guid>
      <dc:creator>jdprovine</dc:creator>
      <dc:date>2018-12-21T14:41:39Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware failure recovery in  an HA pair</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/hardware-failure-recovery-in-an-ha-pair/m-p/244264#M69723</link>
      <description>&lt;P&gt;Well I guess that second firewall took over.&lt;/P&gt;&lt;P&gt;So when you get new hardware then configure mgmt interface, HA settings and from firewall that has config you sync to peer.&lt;/P&gt;&lt;P&gt;Also Link and Path monitoring needs to be configured on both firewalls seperately.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are they in Panorama?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Dec 2018 16:05:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/hardware-failure-recovery-in-an-ha-pair/m-p/244264#M69723</guid>
      <dc:creator>Raido_Rattameister</dc:creator>
      <dc:date>2018-12-21T16:05:20Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware failure recovery in  an HA pair</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/hardware-failure-recovery-in-an-ha-pair/m-p/244266#M69725</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/15603"&gt;@Raido_Rattameister&lt;/a&gt;&lt;/P&gt;&lt;P&gt;Yes I would assume that the secondary would take over to, this hasn't actually happened I was thinking about the best way to deal with it. So you would let the secondary sync to the new hardware?&lt;/P&gt;&lt;P&gt;No panorama&lt;/P&gt;</description>
      <pubDate>Fri, 21 Dec 2018 16:11:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/hardware-failure-recovery-in-an-ha-pair/m-p/244266#M69725</guid>
      <dc:creator>jdprovine</dc:creator>
      <dc:date>2018-12-21T16:11:55Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware failure recovery in  an HA pair</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/hardware-failure-recovery-in-an-ha-pair/m-p/244267#M69726</link>
      <description>&lt;P&gt;Yes that is all you have to do.&lt;/P&gt;&lt;P&gt;But be careful. Sync to peer is available on both firewalls. If you accidentally click on it on the empty firewall then empty config is pushed to other one and your environment will go down &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Dec 2018 16:14:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/hardware-failure-recovery-in-an-ha-pair/m-p/244267#M69726</guid>
      <dc:creator>Raido_Rattameister</dc:creator>
      <dc:date>2018-12-21T16:14:57Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware failure recovery in  an HA pair</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/hardware-failure-recovery-in-an-ha-pair/m-p/244268#M69727</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/15603"&gt;@Raido_Rattameister&lt;/a&gt;&lt;/P&gt;&lt;P&gt;So did you make new hardware the secondary or the primary again. Recently PA TAC told me to disable sync to peer on the secondary&lt;/P&gt;</description>
      <pubDate>Fri, 21 Dec 2018 16:44:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/hardware-failure-recovery-in-an-ha-pair/m-p/244268#M69727</guid>
      <dc:creator>jdprovine</dc:creator>
      <dc:date>2018-12-21T16:44:27Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware failure recovery in  an HA pair</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/hardware-failure-recovery-in-an-ha-pair/m-p/244269#M69728</link>
      <description>&lt;P&gt;If one firewall fails then you replace it, set up management, ha, path and link monitoring.&lt;/P&gt;&lt;P&gt;Make sure to set ha priority higher number on new firewall so it would not become active with empty config.&lt;/P&gt;&lt;P&gt;Log into old firewall and click sync to peer.&lt;/P&gt;&lt;P&gt;Done&lt;/P&gt;</description>
      <pubDate>Fri, 21 Dec 2018 16:46:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/hardware-failure-recovery-in-an-ha-pair/m-p/244269#M69728</guid>
      <dc:creator>Raido_Rattameister</dc:creator>
      <dc:date>2018-12-21T16:46:51Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware failure recovery in  an HA pair</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/hardware-failure-recovery-in-an-ha-pair/m-p/244274#M69730</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/15603"&gt;@Raido_Rattameister&lt;/a&gt;&lt;/P&gt;&lt;P&gt;So you would bring the replaced one back on as the primary again? We only have 2 PA's and primary and a secondary.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Dec 2018 17:14:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/hardware-failure-recovery-in-an-ha-pair/m-p/244274#M69730</guid>
      <dc:creator>jdprovine</dc:creator>
      <dc:date>2018-12-21T17:14:33Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware failure recovery in  an HA pair</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/hardware-failure-recovery-in-an-ha-pair/m-p/244297#M69732</link>
      <description>&lt;P&gt;Let's assume you call them primary and secondary.&lt;/P&gt;&lt;P&gt;Primary is active.&lt;/P&gt;&lt;P&gt;Primary fails.&lt;/P&gt;&lt;P&gt;Secondary becames active.&lt;/P&gt;&lt;P&gt;You RMA the hardware.&lt;/P&gt;&lt;P&gt;Configure settings on new primary.&lt;/P&gt;&lt;P&gt;If it becames acitve before you have synced config from secondary then your environment goes down.&lt;/P&gt;&lt;P&gt;So initially you have to have HA priorithy higher number on new primary compared to secondary so it would not become active.&lt;/P&gt;&lt;P&gt;After sync to peer you can change priority settings so that new primary becomes active again.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Dec 2018 18:53:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/hardware-failure-recovery-in-an-ha-pair/m-p/244297#M69732</guid>
      <dc:creator>Raido_Rattameister</dc:creator>
      <dc:date>2018-12-21T18:53:43Z</dc:date>
    </item>
  </channel>
</rss>

