<?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 Upgrade gateways to R82 T127 - Installer stuck at 99% in Firewall &amp; Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-Security-Management/Upgrade-gateways-to-R82-T127-Installer-stuck-at-99/m-p/282993#M106937</link>
    <description>&lt;P&gt;R82 T122 ElasticXL VSNext Dual-Site. Tried to install T127 on the second site.&lt;/P&gt;
&lt;P&gt;SMS upgraded from T122 to T127 OK.&lt;/P&gt;
&lt;P&gt;CPUSE Agent 2808 (auto-updated).&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As the title says, install got there but stayed at 99% for an hour. After a reboot, it came back nicely in the cluster with T122.&lt;/P&gt;
&lt;P&gt;First time this happens, as we went with that cluster since at least Take 60 and upgrades were always fine.&lt;/P&gt;
&lt;P&gt;Is it a known issue? We will try again with Take 126 in a few days - still need to get used to the Initial/Wide adoption and not fetch the latest JHF anymore.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We didn't want to leave the second unit in what was potentially an unstable state, even though no issues were visible and there were no traces of leftovers from 127.&lt;/P&gt;
&lt;P&gt;So I just took the member out of the ElasticXL cluster, rejoined it and it came back as new. On this, ElasticXL is a great improvement in cluster manageability.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2026 12:34:32 GMT</pubDate>
    <dc:creator>Alex-</dc:creator>
    <dc:date>2026-09-29T12:34:32Z</dc:date>
    <item>
      <title>Upgrade gateways to R82 T127 - Installer stuck at 99%</title>
      <link>https://community.checkpoint.com/t5/Firewall-Security-Management/Upgrade-gateways-to-R82-T127-Installer-stuck-at-99/m-p/282993#M106937</link>
      <description>&lt;P&gt;R82 T122 ElasticXL VSNext Dual-Site. Tried to install T127 on the second site.&lt;/P&gt;
&lt;P&gt;SMS upgraded from T122 to T127 OK.&lt;/P&gt;
&lt;P&gt;CPUSE Agent 2808 (auto-updated).&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As the title says, install got there but stayed at 99% for an hour. After a reboot, it came back nicely in the cluster with T122.&lt;/P&gt;
&lt;P&gt;First time this happens, as we went with that cluster since at least Take 60 and upgrades were always fine.&lt;/P&gt;
&lt;P&gt;Is it a known issue? We will try again with Take 126 in a few days - still need to get used to the Initial/Wide adoption and not fetch the latest JHF anymore.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We didn't want to leave the second unit in what was potentially an unstable state, even though no issues were visible and there were no traces of leftovers from 127.&lt;/P&gt;
&lt;P&gt;So I just took the member out of the ElasticXL cluster, rejoined it and it came back as new. On this, ElasticXL is a great improvement in cluster manageability.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2026 12:34:32 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-Security-Management/Upgrade-gateways-to-R82-T127-Installer-stuck-at-99/m-p/282993#M106937</guid>
      <dc:creator>Alex-</dc:creator>
      <dc:date>2026-09-29T12:34:32Z</dc:date>
    </item>
  </channel>
</rss>

