<?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: Query on HA failover in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/query-on-ha-failover/m-p/280479#M75850</link>
    <description>&lt;P&gt;so you curerntly have:&lt;BR /&gt;&lt;BR /&gt;fw1 --&amp;gt; running the new os and passive?&lt;/P&gt;&lt;P&gt;fw2 --&amp;gt; running the old image and active.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ha status is okay but pan-os version is mismatch and config is not synced( which is normal during upgrade of a cluster)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;the fastest way according to me( if you have followed upgrade best practices and turned preempt off)&lt;/P&gt;&lt;P&gt;is to suspend the active firewall(running old os) and with preempt disable there should be no issue making the device functional again right away.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;at this point you will have failed over to the fw1 running the new image.&lt;BR /&gt;if you notice issues it's simply a case of suspending the fw1 with the new image so you fallback to the other cluster member.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;the failovers during an upgrade should be just as fast as before teh upgrade. so if you did not lose any pings when failing over before you started you can expect the same now.&lt;/P&gt;</description>
    <pubDate>Thu, 01 Aug 2019 08:40:11 GMT</pubDate>
    <dc:creator>TommieVanHove</dc:creator>
    <dc:date>2019-08-01T08:40:11Z</dc:date>
    <item>
      <title>Query on HA failover</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/query-on-ha-failover/m-p/280454#M75847</link>
      <description>&lt;P&gt;Currently our secondary unit is running as Primary.&lt;/P&gt;&lt;P&gt;We have upgraded our Secondary (originally Primary) FW and now would like to do the failover so that it becomes Primary.&lt;/P&gt;&lt;P&gt;If the failover doesn't work as expected what should be done straightaway to avoid any traffic loss?&lt;/P&gt;</description>
      <pubDate>Thu, 01 Aug 2019 06:07:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/query-on-ha-failover/m-p/280454#M75847</guid>
      <dc:creator>FarzanaMustafa</dc:creator>
      <dc:date>2019-08-01T06:07:40Z</dc:date>
    </item>
    <item>
      <title>Re: Query on HA failover</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/query-on-ha-failover/m-p/280479#M75850</link>
      <description>&lt;P&gt;so you curerntly have:&lt;BR /&gt;&lt;BR /&gt;fw1 --&amp;gt; running the new os and passive?&lt;/P&gt;&lt;P&gt;fw2 --&amp;gt; running the old image and active.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ha status is okay but pan-os version is mismatch and config is not synced( which is normal during upgrade of a cluster)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;the fastest way according to me( if you have followed upgrade best practices and turned preempt off)&lt;/P&gt;&lt;P&gt;is to suspend the active firewall(running old os) and with preempt disable there should be no issue making the device functional again right away.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;at this point you will have failed over to the fw1 running the new image.&lt;BR /&gt;if you notice issues it's simply a case of suspending the fw1 with the new image so you fallback to the other cluster member.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;the failovers during an upgrade should be just as fast as before teh upgrade. so if you did not lose any pings when failing over before you started you can expect the same now.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Aug 2019 08:40:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/query-on-ha-failover/m-p/280479#M75850</guid>
      <dc:creator>TommieVanHove</dc:creator>
      <dc:date>2019-08-01T08:40:11Z</dc:date>
    </item>
  </channel>
</rss>

