<?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: Considerations for a GAIA OS Upgrade in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/Considerations-for-a-GAIA-OS-Upgrade/m-p/187878#M31480</link>
    <description>&lt;P&gt;You shouldn't have needed to reset SIC. It definitely survives upgrades. During the upgrade on a firewall, services stop. Eventually the firewall reboots. You won't have any communications with it until it's done rebooting to the new version.&lt;/P&gt;
&lt;P&gt;I highly, highly recommend upgrading with CDT, either on the command line or in SmartConsole. Once you have your management upgraded to R81.10, connect to SmartConsole. Right-click on your cluster object, go to Actions, then pick Version Upgrade. It handles updating CPUSE, distributing the CPUSE package, upgrading one member, enabling cross-version sync, failing over, then upgrading the other member. Seriously, this is my favorite new feature from Check Point since the initial release of R80.&lt;/P&gt;
&lt;P&gt;I've upgraded around 70 clusters this way. There are occasional snags during the upgrade process, but those would have been hit during a manual upgrade, too.&lt;/P&gt;</description>
    <pubDate>Thu, 27 Jul 2023 14:10:18 GMT</pubDate>
    <dc:creator>Bob_Zimmerman</dc:creator>
    <dc:date>2023-07-27T14:10:18Z</dc:date>
    <item>
      <title>Considerations for a GAIA OS Upgrade</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Considerations-for-a-GAIA-OS-Upgrade/m-p/187756#M31441</link>
      <description>&lt;P&gt;Hello, team.&lt;/P&gt;
&lt;P&gt;Are there any considerations to take into account before upgrading from e.g. R81 to R81.10?&lt;/P&gt;
&lt;P&gt;I just "simulated" the scenario in a lab environment using the CPUSE UPGRADE from the GAIA PORTAL of my GW (I have only one SMS + 1 GW).&lt;/P&gt;
&lt;P&gt;At the moment when I was "applying the installation" on the GW, I lost the connection between the SMS and the GW (In the SmartConsole, it appears that the GW has lost the connection).&lt;/P&gt;
&lt;P&gt;This left me wondering "why?", because to recover the management, I had to wait for the GW to update, and I had to "reset" the SIC again.&lt;/P&gt;
&lt;P&gt;I want to avoid mishaps at the time of upgrading in my productive environment (since I have to upgrade 2 Clusters with R81 version to R81.10) and that is why I consult on the basis of your experiences.&lt;/P&gt;
&lt;P&gt;Thanks for your comments.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jul 2023 18:26:49 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Considerations-for-a-GAIA-OS-Upgrade/m-p/187756#M31441</guid>
      <dc:creator>Matlu</dc:creator>
      <dc:date>2023-07-26T18:26:49Z</dc:date>
    </item>
    <item>
      <title>Re: Considerations for a GAIA OS Upgrade</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Considerations-for-a-GAIA-OS-Upgrade/m-p/187878#M31480</link>
      <description>&lt;P&gt;You shouldn't have needed to reset SIC. It definitely survives upgrades. During the upgrade on a firewall, services stop. Eventually the firewall reboots. You won't have any communications with it until it's done rebooting to the new version.&lt;/P&gt;
&lt;P&gt;I highly, highly recommend upgrading with CDT, either on the command line or in SmartConsole. Once you have your management upgraded to R81.10, connect to SmartConsole. Right-click on your cluster object, go to Actions, then pick Version Upgrade. It handles updating CPUSE, distributing the CPUSE package, upgrading one member, enabling cross-version sync, failing over, then upgrading the other member. Seriously, this is my favorite new feature from Check Point since the initial release of R80.&lt;/P&gt;
&lt;P&gt;I've upgraded around 70 clusters this way. There are occasional snags during the upgrade process, but those would have been hit during a manual upgrade, too.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jul 2023 14:10:18 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Considerations-for-a-GAIA-OS-Upgrade/m-p/187878#M31480</guid>
      <dc:creator>Bob_Zimmerman</dc:creator>
      <dc:date>2023-07-27T14:10:18Z</dc:date>
    </item>
    <item>
      <title>Re: Considerations for a GAIA OS Upgrade</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Considerations-for-a-GAIA-OS-Upgrade/m-p/187887#M31485</link>
      <description>&lt;P&gt;As&amp;nbsp;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/27871"&gt;@Bob_Zimmerman&lt;/a&gt;&amp;nbsp;said, SIC reset would not be needed. Personally, I always use CPUSE, as it never gave me trouble, but thats just my own preference, to each their own : - )&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jul 2023 14:34:28 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Considerations-for-a-GAIA-OS-Upgrade/m-p/187887#M31485</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2023-07-27T14:34:28Z</dc:date>
    </item>
  </channel>
</rss>

