<?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 S1C managed SG9100-Cluster Upgrade R81.20 JHFT105 &amp;gt; R82JHFT39 / best practise, hints recommendations in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S1C-managed-SG9100-Cluster-Upgrade-R81-20-JHFT105-gt-R82JHFT39/m-p/258300#M50651</link>
    <description>&lt;P&gt;Dear Community,&lt;/P&gt;&lt;P&gt;We have a centrally-managed (S1C) SG9100-Cluster Upgrade from R81.20 JHFT105&amp;nbsp;&amp;gt; R82JHFT39 ahead. No private hotfixes installed.&lt;BR /&gt;So far R82 is now recommended release and we wanna implement HTTPSi soon, that's why we wanna change first to R82 for less CPU impact. Our S1C tenant is R82 since nearly 10 months.&lt;BR /&gt;Until now we did the JHFT-Updates within R81.20 via CPUSE (Gaia GUI).&lt;BR /&gt;But I read it's recommended to do that via SmartConsole now, as S1C will do all the automatics by itself (Multiversion Cluster while updating, etc.)&lt;BR /&gt;So far I would upgrade with the Blink Image R82 Take 777 including Recommended Jumbo Take 39 which CPUSE also recommends, but over the S1C repository.&lt;BR /&gt;Snapshots and backups are made, and also downloaded close to the SG's onsite for any case, console cables are connected and ready to both appliances&lt;/P&gt;&lt;P&gt;My questions now:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Anything against taking the Blink Image R82 T777 with JHFT39?&lt;/LI&gt;&lt;LI&gt;Would you do the "all cluster member" version upgrade option, or the "install on non-active member only", with turning non-active to active option selected, let it run, test first the R82-upgraded active member, and then proceed with the second one the same way? I ask that because I don't have experiences with the R82 at all, and also not with release upgrades.&lt;/LI&gt;&lt;LI&gt;Anything to check/prepare upon Wildcard certificates we have active for Mobile access VPN or regular S2S VPN Tunnels?&lt;/LI&gt;&lt;LI&gt;Anything else somebody experienced?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Thank you in advance&lt;/P&gt;</description>
    <pubDate>Fri, 26 Sep 2025 10:49:37 GMT</pubDate>
    <dc:creator>freshwater84</dc:creator>
    <dc:date>2025-09-26T10:49:37Z</dc:date>
    <item>
      <title>S1C managed SG9100-Cluster Upgrade R81.20 JHFT105 &gt; R82JHFT39 / best practise, hints recommendations</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S1C-managed-SG9100-Cluster-Upgrade-R81-20-JHFT105-gt-R82JHFT39/m-p/258300#M50651</link>
      <description>&lt;P&gt;Dear Community,&lt;/P&gt;&lt;P&gt;We have a centrally-managed (S1C) SG9100-Cluster Upgrade from R81.20 JHFT105&amp;nbsp;&amp;gt; R82JHFT39 ahead. No private hotfixes installed.&lt;BR /&gt;So far R82 is now recommended release and we wanna implement HTTPSi soon, that's why we wanna change first to R82 for less CPU impact. Our S1C tenant is R82 since nearly 10 months.&lt;BR /&gt;Until now we did the JHFT-Updates within R81.20 via CPUSE (Gaia GUI).&lt;BR /&gt;But I read it's recommended to do that via SmartConsole now, as S1C will do all the automatics by itself (Multiversion Cluster while updating, etc.)&lt;BR /&gt;So far I would upgrade with the Blink Image R82 Take 777 including Recommended Jumbo Take 39 which CPUSE also recommends, but over the S1C repository.&lt;BR /&gt;Snapshots and backups are made, and also downloaded close to the SG's onsite for any case, console cables are connected and ready to both appliances&lt;/P&gt;&lt;P&gt;My questions now:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Anything against taking the Blink Image R82 T777 with JHFT39?&lt;/LI&gt;&lt;LI&gt;Would you do the "all cluster member" version upgrade option, or the "install on non-active member only", with turning non-active to active option selected, let it run, test first the R82-upgraded active member, and then proceed with the second one the same way? I ask that because I don't have experiences with the R82 at all, and also not with release upgrades.&lt;/LI&gt;&lt;LI&gt;Anything to check/prepare upon Wildcard certificates we have active for Mobile access VPN or regular S2S VPN Tunnels?&lt;/LI&gt;&lt;LI&gt;Anything else somebody experienced?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Thank you in advance&lt;/P&gt;</description>
      <pubDate>Fri, 26 Sep 2025 10:49:37 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S1C-managed-SG9100-Cluster-Upgrade-R81-20-JHFT105-gt-R82JHFT39/m-p/258300#M50651</guid>
      <dc:creator>freshwater84</dc:creator>
      <dc:date>2025-09-26T10:49:37Z</dc:date>
    </item>
    <item>
      <title>Re: S1C managed SG9100-Cluster Upgrade R81.20 JHFT105 &gt; R82JHFT39 / best practise, hints recommen</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S1C-managed-SG9100-Cluster-Upgrade-R81-20-JHFT105-gt-R82JHFT39/m-p/258429#M50683</link>
      <description>&lt;P&gt;You are going to perform an in-place upgrade of your cluster, and your MGMT is already on R82.&lt;BR /&gt;&lt;BR /&gt;Did you read the &lt;A href="https://sc1.checkpoint.com/documents/R82/WebAdminGuides/EN/CP_R82_Installation_and_Upgrade_Guide/CP_R82_Installation_and_Upgrade_Guide.pdf" target="_self"&gt;R82 Installation and Upgrade guid&lt;/A&gt;e? If you did not, go there and look up MVP cluster upgrade procedure. You literally just need to do it by the book.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Concerning the version, I would go for the latest recommended release, including Jumbo.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 29 Sep 2025 08:09:37 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S1C-managed-SG9100-Cluster-Upgrade-R81-20-JHFT105-gt-R82JHFT39/m-p/258429#M50683</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2025-09-29T08:09:37Z</dc:date>
    </item>
    <item>
      <title>Re: S1C managed SG9100-Cluster Upgrade R81.20 JHFT105 &gt; R82JHFT39 / best practise, hints recommen</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S1C-managed-SG9100-Cluster-Upgrade-R81-20-JHFT105-gt-R82JHFT39/m-p/258430#M50684</link>
      <description>&lt;P&gt;Hi Val,&lt;/P&gt;&lt;P&gt;Thanks, we already did the upgrade.&lt;BR /&gt;Recommended was to do it via S1C SmartConsole, according to the Upgrade guide (R81 - unfortunately centrally managed upgrade process part on the R82 online guide is down since a few days). But he brought an error with a blocking reason in S1C. Could (even with support) not debug the error any further.&lt;BR /&gt;We contacted support, and he said, he would do it via CPUSE. So we did that. Then of course we had the problems with MVP, where he guided us through.&lt;BR /&gt;Also he said, he hate blink images - he would always upgrade first to R82 T777 and do the Jumbo's later, so we did in our case.&lt;BR /&gt;Everything was fine so far, and we are running on R82 JHFT39&lt;/P&gt;</description>
      <pubDate>Mon, 29 Sep 2025 08:30:09 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S1C-managed-SG9100-Cluster-Upgrade-R81-20-JHFT105-gt-R82JHFT39/m-p/258430#M50684</guid>
      <dc:creator>freshwater84</dc:creator>
      <dc:date>2025-09-29T08:30:09Z</dc:date>
    </item>
  </channel>
</rss>

