<?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: HA recovery advice after upgrading Active first in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ha-recovery-advice-after-upgrading-active-first/m-p/12335#M9032</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-family: arial, helvetica, sans-serif; font-size: 8pt;"&gt;I did the same thing too the first time. &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://live.paloaltonetworks.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="line-height: 1.5em; font-family: arial, helvetica, sans-serif; font-size: 8pt;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="line-height: 1.5em; font-family: arial, helvetica, sans-serif; font-size: 8pt;"&gt;Basically what you want to do is revert the firewall you upgraded, and then when the HA pair is back how they were running 4.1.7, you can start over and follow the proper method. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: arial, helvetica, sans-serif; font-size: 8pt;"&gt;If I remember correctly, this should work...&lt;/SPAN&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;SPAN style="line-height: 1.5em; font-family: arial, helvetica, sans-serif; font-size: 8pt;"&gt;On active (4.1.10) firewall you upgraded, export the last several configs that the system saved before and after you upgraded the firewall. You can do this from Setup&amp;gt;Export&amp;gt;Export&amp;gt;Config Verison in the GUI. This step is precautionary, just so you have a copy of the config it was running before and after you upgraded the firewall.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-family: arial, helvetica, sans-serif; font-size: 8pt;"&gt;Next, make sure the running configs are synced in the GUI's Dashboard&amp;gt;HA pane. This will ensure your latest config will be retained on the HA pair.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-family: arial, helvetica, sans-serif; font-size: 8pt;"&gt;Suspend your primary (4.1.10) firewall using the Device&amp;gt;HA&amp;gt;Operation Commands&amp;gt;'suspend local device' in the GUI, or the "request high-availability state suspend" from CLI. The 4.1.7 firewall will now be the active firewall.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-family: arial, helvetica, sans-serif; font-size: 8pt;"&gt;Now in Device&amp;gt;Software you can install the 4.1.7 software to revert the firewall back. After it reboots, the config (we just synced) from the active 4.1.7 firewall will be pushed over.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-family: arial, helvetica, sans-serif; font-size: 8pt;"&gt;Both firewalls are now running the same OS again, and you can make the downgraded firewall the active node again by performing the 'suspend' and 'make functional' procedure on the opposite firewall.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;Now you are back to square one, and you can follow this guide for the correct procedure to upgrading a clustered pair:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;A __default_attr="4043" __jive_macro_name="document" class="jive_macro jive_macro_document" href="https://live.paloaltonetworks.com/"&gt;&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 18 Jan 2013 15:56:47 GMT</pubDate>
    <dc:creator>panman</dc:creator>
    <dc:date>2013-01-18T15:56:47Z</dc:date>
    <item>
      <title>HA recovery advice after upgrading Active first</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ha-recovery-advice-after-upgrading-active-first/m-p/12333#M9030</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Being a newb and never having updated my Active/Passive HA pair, I took the 4.1.10 release notes at face value. There is no mention of special provisions for HA upgrades so I clicked "install" and now have a 4.1.10 Active member and a mismatched 4.1.7 passive member. Having now read the full product documentation I understand the "proper" way to upgrade an HA pair.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What are my best options for proceeding from here?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Jan 2013 14:53:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ha-recovery-advice-after-upgrading-active-first/m-p/12333#M9030</guid>
      <dc:creator>MCmgt</dc:creator>
      <dc:date>2013-01-18T14:53:44Z</dc:date>
    </item>
    <item>
      <title>Re: HA recovery advice after upgrading Active first</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ha-recovery-advice-after-upgrading-active-first/m-p/12334#M9031</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Active is passing traffic so now, only recourse is to proceed with your passive upgrade.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Jan 2013 15:19:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ha-recovery-advice-after-upgrading-active-first/m-p/12334#M9031</guid>
      <dc:creator>gswcowboy</dc:creator>
      <dc:date>2013-01-18T15:19:44Z</dc:date>
    </item>
    <item>
      <title>Re: HA recovery advice after upgrading Active first</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ha-recovery-advice-after-upgrading-active-first/m-p/12335#M9032</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-family: arial, helvetica, sans-serif; font-size: 8pt;"&gt;I did the same thing too the first time. &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://live.paloaltonetworks.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="line-height: 1.5em; font-family: arial, helvetica, sans-serif; font-size: 8pt;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="line-height: 1.5em; font-family: arial, helvetica, sans-serif; font-size: 8pt;"&gt;Basically what you want to do is revert the firewall you upgraded, and then when the HA pair is back how they were running 4.1.7, you can start over and follow the proper method. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: arial, helvetica, sans-serif; font-size: 8pt;"&gt;If I remember correctly, this should work...&lt;/SPAN&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;SPAN style="line-height: 1.5em; font-family: arial, helvetica, sans-serif; font-size: 8pt;"&gt;On active (4.1.10) firewall you upgraded, export the last several configs that the system saved before and after you upgraded the firewall. You can do this from Setup&amp;gt;Export&amp;gt;Export&amp;gt;Config Verison in the GUI. This step is precautionary, just so you have a copy of the config it was running before and after you upgraded the firewall.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-family: arial, helvetica, sans-serif; font-size: 8pt;"&gt;Next, make sure the running configs are synced in the GUI's Dashboard&amp;gt;HA pane. This will ensure your latest config will be retained on the HA pair.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-family: arial, helvetica, sans-serif; font-size: 8pt;"&gt;Suspend your primary (4.1.10) firewall using the Device&amp;gt;HA&amp;gt;Operation Commands&amp;gt;'suspend local device' in the GUI, or the "request high-availability state suspend" from CLI. The 4.1.7 firewall will now be the active firewall.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-family: arial, helvetica, sans-serif; font-size: 8pt;"&gt;Now in Device&amp;gt;Software you can install the 4.1.7 software to revert the firewall back. After it reboots, the config (we just synced) from the active 4.1.7 firewall will be pushed over.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-family: arial, helvetica, sans-serif; font-size: 8pt;"&gt;Both firewalls are now running the same OS again, and you can make the downgraded firewall the active node again by performing the 'suspend' and 'make functional' procedure on the opposite firewall.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;Now you are back to square one, and you can follow this guide for the correct procedure to upgrading a clustered pair:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;A __default_attr="4043" __jive_macro_name="document" class="jive_macro jive_macro_document" href="https://live.paloaltonetworks.com/"&gt;&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Jan 2013 15:56:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ha-recovery-advice-after-upgrading-active-first/m-p/12335#M9032</guid>
      <dc:creator>panman</dc:creator>
      <dc:date>2013-01-18T15:56:47Z</dc:date>
    </item>
  </channel>
</rss>

