<?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 Paloalto FW HA(Active/Passive) OS Upgrade Procedure 10.1.X -&amp;gt; 11.1.X in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/paloalto-fw-ha-active-passive-os-upgrade-procedure-10-1-x-gt-11/m-p/615527#M4916</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Hello&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have a question about upgrading the Palo Alto Fire Wall OS.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;From the 11.1.X version, we've seen that you can upgrade right away without a 10.2.X or 11.0.X install.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="sky95hhhh_0-1730177508043.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/63636iCECBE64D7BE1B94D/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="sky95hhhh_0-1730177508043.png" alt="sky95hhhh_0-1730177508043.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;ex) OS Upgrade(10.1.13-h1 -&amp;gt; 11.1.5)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I ran the test on my Standalone firewall (10.1.13-h1) and verified that the upgrade was successful through 11.1.5 install after 11.1.0, 11.1.5 downloads.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;My question is whether it applies to HA (Active/Passive).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;A href="https://docs.paloaltonetworks.com/pan-os/11-1/pan-os-upgrade/upgrade-pan-os/upgrade-the-firewall-pan-os/upgrade-an-ha-firewall-pair" target="_blank"&gt;https://docs.paloaltonetworks.com/pan-os/11-1/pan-os-upgrade/upgrade-pan-os/upgrade-the-firewall-pan-os/upgrade-an-ha-firewall-pair&lt;/A&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;When you look at the HA Upgrade Guide document above, it says.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; For example, you are upgrading HA peers from PAN-OS 10.2 to PAN-OS 11.1. You must upgrade both HA peers to PAN-OS 11.0 before you can continue upgrading to the target PAN-OS 11.1 release. When HA peers are two or more feature releases apart, the firewall with the older release installed enters a suspended state with the message Peer version too old.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So I set up HA active/passive internally and conducted the test, and the process is as follows.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Prerequisites: PAN-OS 11.1.0, 11.1.5 download&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;1. Primary(Active) : 10.1.13-h1, Secondary(Passive) : 10.1.13-h1&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;[failover-User requested]&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2. Primary(Suspend) : 10.1.13-h1, Secondary(Active) : 10.1.13-h1&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;[Primary 11.1.5 install and reboot]&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;3. Primary(Passive) : 11.1.5, Secondary(Active) : 10.1.13-h1&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;[failback-User requested]&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;4. Primary(Active) : 11.1.5, Secondary(Suspend) : 10.1.13-h1&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;[Secondary 11.1.5 install and reboot]&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;5. Primary(Active) : 11.1.5, Secondary(Passive) : 11.1.5&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;According to the above, I think the secondary device should enter the suspend state in number 3, "Primary(passive): 11.1.5, Secondary(Active): 10.1.13-h1".&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;However, even if the HA peer is separated into more than one release, the firewall with the old release was not put in a suspended state and functioned normally.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So I continued the No. 4 procedure and the two devices were upgraded to 11.1.5 OS normally.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Is there an improvement in the functionality to prevent the old release from entering the suspend in No.3?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 29 Oct 2024 05:00:01 GMT</pubDate>
    <dc:creator>sky95hhhh</dc:creator>
    <dc:date>2024-10-29T05:00:01Z</dc:date>
    <item>
      <title>Paloalto FW HA(Active/Passive) OS Upgrade Procedure 10.1.X -&gt; 11.1.X</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/paloalto-fw-ha-active-passive-os-upgrade-procedure-10-1-x-gt-11/m-p/615527#M4916</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hello&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have a question about upgrading the Palo Alto Fire Wall OS.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;From the 11.1.X version, we've seen that you can upgrade right away without a 10.2.X or 11.0.X install.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="sky95hhhh_0-1730177508043.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/63636iCECBE64D7BE1B94D/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="sky95hhhh_0-1730177508043.png" alt="sky95hhhh_0-1730177508043.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;ex) OS Upgrade(10.1.13-h1 -&amp;gt; 11.1.5)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I ran the test on my Standalone firewall (10.1.13-h1) and verified that the upgrade was successful through 11.1.5 install after 11.1.0, 11.1.5 downloads.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;My question is whether it applies to HA (Active/Passive).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;A href="https://docs.paloaltonetworks.com/pan-os/11-1/pan-os-upgrade/upgrade-pan-os/upgrade-the-firewall-pan-os/upgrade-an-ha-firewall-pair" target="_blank"&gt;https://docs.paloaltonetworks.com/pan-os/11-1/pan-os-upgrade/upgrade-pan-os/upgrade-the-firewall-pan-os/upgrade-an-ha-firewall-pair&lt;/A&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;When you look at the HA Upgrade Guide document above, it says.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; For example, you are upgrading HA peers from PAN-OS 10.2 to PAN-OS 11.1. You must upgrade both HA peers to PAN-OS 11.0 before you can continue upgrading to the target PAN-OS 11.1 release. When HA peers are two or more feature releases apart, the firewall with the older release installed enters a suspended state with the message Peer version too old.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So I set up HA active/passive internally and conducted the test, and the process is as follows.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Prerequisites: PAN-OS 11.1.0, 11.1.5 download&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;1. Primary(Active) : 10.1.13-h1, Secondary(Passive) : 10.1.13-h1&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;[failover-User requested]&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2. Primary(Suspend) : 10.1.13-h1, Secondary(Active) : 10.1.13-h1&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;[Primary 11.1.5 install and reboot]&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;3. Primary(Passive) : 11.1.5, Secondary(Active) : 10.1.13-h1&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;[failback-User requested]&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;4. Primary(Active) : 11.1.5, Secondary(Suspend) : 10.1.13-h1&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;[Secondary 11.1.5 install and reboot]&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;5. Primary(Active) : 11.1.5, Secondary(Passive) : 11.1.5&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;According to the above, I think the secondary device should enter the suspend state in number 3, "Primary(passive): 11.1.5, Secondary(Active): 10.1.13-h1".&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;However, even if the HA peer is separated into more than one release, the firewall with the old release was not put in a suspended state and functioned normally.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So I continued the No. 4 procedure and the two devices were upgraded to 11.1.5 OS normally.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Is there an improvement in the functionality to prevent the old release from entering the suspend in No.3?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Oct 2024 05:00:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/paloalto-fw-ha-active-passive-os-upgrade-procedure-10-1-x-gt-11/m-p/615527#M4916</guid>
      <dc:creator>sky95hhhh</dc:creator>
      <dc:date>2024-10-29T05:00:01Z</dc:date>
    </item>
  </channel>
</rss>

