<?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 R80.30 Jumbo Hotfix Accumulator - New Ongoing Take 180 in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-30-Jumbo-Hotfix-Accumulator-New-Ongoing-Take-180/m-p/81271#M6291</link>
    <description>&lt;P&gt;A fresh ongoing take of R80.30 Jumbo Take 180 is ready, but all can be glad that still have Take 155 on their clusters, as we read:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Customers on cluster environments using R80.30 Jumbo Hotfix Takes 163-168 that would like to install Take 180, should refer to&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk166192" target="_blank" rel="nofollow noopener noreferrer"&gt;sk166192&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;And after reading the&amp;nbsp;&lt;SPAN&gt;sk166192&amp;nbsp;Security gateway may crash during Jumbo Hotfix install/uninstall from R80.30 JHF Takes 163-168, i began thinking about recent cases where Jumbo install over 155 failed or was reverted because of big trouble with the Jumbo Take e.g. 168. I thought that not the JT had been the reason for the issue(s). but i still have to find out&amp;nbsp;&lt;/SPAN&gt;more...&lt;/P&gt;</description>
    <pubDate>Wed, 08 Apr 2020 07:48:29 GMT</pubDate>
    <dc:creator>G_W_Albrecht</dc:creator>
    <dc:date>2020-04-08T07:48:29Z</dc:date>
    <item>
      <title>R80.30 Jumbo Hotfix Accumulator - New Ongoing Take 180</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-30-Jumbo-Hotfix-Accumulator-New-Ongoing-Take-180/m-p/81271#M6291</link>
      <description>&lt;P&gt;A fresh ongoing take of R80.30 Jumbo Take 180 is ready, but all can be glad that still have Take 155 on their clusters, as we read:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Customers on cluster environments using R80.30 Jumbo Hotfix Takes 163-168 that would like to install Take 180, should refer to&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk166192" target="_blank" rel="nofollow noopener noreferrer"&gt;sk166192&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;And after reading the&amp;nbsp;&lt;SPAN&gt;sk166192&amp;nbsp;Security gateway may crash during Jumbo Hotfix install/uninstall from R80.30 JHF Takes 163-168, i began thinking about recent cases where Jumbo install over 155 failed or was reverted because of big trouble with the Jumbo Take e.g. 168. I thought that not the JT had been the reason for the issue(s). but i still have to find out&amp;nbsp;&lt;/SPAN&gt;more...&lt;/P&gt;</description>
      <pubDate>Wed, 08 Apr 2020 07:48:29 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-30-Jumbo-Hotfix-Accumulator-New-Ongoing-Take-180/m-p/81271#M6291</guid>
      <dc:creator>G_W_Albrecht</dc:creator>
      <dc:date>2020-04-08T07:48:29Z</dc:date>
    </item>
    <item>
      <title>Re: R80.30 Jumbo Hotfix Accumulator - New Ongoing Take 180</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-30-Jumbo-Hotfix-Accumulator-New-Ongoing-Take-180/m-p/81384#M6300</link>
      <description>I'm not familiar with the details around the bug, but it does seem like, in the wrong circumstances, it could be highly problematic.</description>
      <pubDate>Wed, 08 Apr 2020 23:59:57 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-30-Jumbo-Hotfix-Accumulator-New-Ongoing-Take-180/m-p/81384#M6300</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2020-04-08T23:59:57Z</dc:date>
    </item>
  </channel>
</rss>

