<?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: sk168513 - Cpu on first instances high on R80.30 take 210 and higher in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/sk168513-Cpu-on-first-instances-high-on-R80-30-take-210-and/m-p/98220#M8621</link>
    <description>&lt;P&gt;If I'm reading those two SK's correctly, you need a special hotfix for this issue under VSX that is separate from the hotfix added into R80.30 Jumbo HFA Take 219 for non-VSX gateways.&lt;/P&gt;</description>
    <pubDate>Mon, 05 Oct 2020 13:50:38 GMT</pubDate>
    <dc:creator>Timothy_Hall</dc:creator>
    <dc:date>2020-10-05T13:50:38Z</dc:date>
    <item>
      <title>sk168513 - Cpu on first instances high on R80.30 take 210 and higher</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/sk168513-Cpu-on-first-instances-high-on-R80-30-take-210-and/m-p/98184#M8620</link>
      <description>&lt;P&gt;Hi!&lt;BR /&gt;&lt;BR /&gt;We did a clean install (upgrade) to R80.30 take 215 on our 23900 appliances (vsx with vsls) three weeks ago.&lt;BR /&gt;After two weeks we noticed that we were hit by the sk168513. There is a hotfix for it in take 219,&amp;nbsp;&lt;BR /&gt;but that doesnt seem to work for VSX as mentioned in&amp;nbsp;&lt;SPAN&gt;sk169352...&lt;BR /&gt;&lt;BR /&gt;There is a workaround mentioned in sk168513 though:&lt;BR /&gt;fw ctl set int fwmultik_enable_increment_first 1&lt;BR /&gt;fw ctl set int fwmultik_enable_round_robin 1&lt;BR /&gt;&lt;BR /&gt;Does anyone know if this workaround also is working and supported on VSX/vsls?&lt;BR /&gt;If yes: should it be enabled on the affected virtual-server or on vs0? (fwkern.conf)&lt;BR /&gt;&lt;BR /&gt;Thx&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Mattias&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Oct 2020 07:26:19 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/sk168513-Cpu-on-first-instances-high-on-R80-30-take-210-and/m-p/98184#M8620</guid>
      <dc:creator>Mattias_Jansson</dc:creator>
      <dc:date>2020-10-05T07:26:19Z</dc:date>
    </item>
    <item>
      <title>Re: sk168513 - Cpu on first instances high on R80.30 take 210 and higher</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/sk168513-Cpu-on-first-instances-high-on-R80-30-take-210-and/m-p/98220#M8621</link>
      <description>&lt;P&gt;If I'm reading those two SK's correctly, you need a special hotfix for this issue under VSX that is separate from the hotfix added into R80.30 Jumbo HFA Take 219 for non-VSX gateways.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Oct 2020 13:50:38 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/sk168513-Cpu-on-first-instances-high-on-R80-30-take-210-and/m-p/98220#M8621</guid>
      <dc:creator>Timothy_Hall</dc:creator>
      <dc:date>2020-10-05T13:50:38Z</dc:date>
    </item>
    <item>
      <title>Re: sk168513 - Cpu on first instances high on R80.30 take 210 and higher</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/sk168513-Cpu-on-first-instances-high-on-R80-30-take-210-and/m-p/98222#M8622</link>
      <description>&lt;P&gt;Yes, I agree with you about the hotfix.&lt;BR /&gt;Therefore my question if the workaround is working (and is supported) on VSX?&lt;/P&gt;</description>
      <pubDate>Mon, 05 Oct 2020 13:56:58 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/sk168513-Cpu-on-first-instances-high-on-R80-30-take-210-and/m-p/98222#M8622</guid>
      <dc:creator>Mattias_Jansson</dc:creator>
      <dc:date>2020-10-05T13:56:58Z</dc:date>
    </item>
    <item>
      <title>Re: sk168513 - Cpu on first instances high on R80.30 take 210 and higher</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/sk168513-Cpu-on-first-instances-high-on-R80-30-take-210-and/m-p/98293#M8623</link>
      <description>&lt;P&gt;The workaround and (non Jumbo) hotfix are in seperate SKs hence address different problems.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2020 13:32:47 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/sk168513-Cpu-on-first-instances-high-on-R80-30-take-210-and/m-p/98293#M8623</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2020-10-06T13:32:47Z</dc:date>
    </item>
    <item>
      <title>Re: sk168513 - Cpu on first instances high on R80.30 take 210 and higher</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/sk168513-Cpu-on-first-instances-high-on-R80-30-take-210-and/m-p/107746#M14445</link>
      <description>&lt;P&gt;Applying the below in the affected VS resolves the issue? Anybody tried it and the CPU come down?&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;fw ctl set int fwmultik_enable_increment_first 1&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;fw ctl set int fwmultik_enable_round_robin 1&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;We are facing the same issue after we upgraded the VSX cluster from R77.30 to R80.30 with the Take 219 HF&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Jan 2021 16:49:21 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/sk168513-Cpu-on-first-instances-high-on-R80-30-take-210-and/m-p/107746#M14445</guid>
      <dc:creator>Sanjay_S</dc:creator>
      <dc:date>2021-01-13T16:49:21Z</dc:date>
    </item>
    <item>
      <title>Re: sk168513 - Cpu on first instances high on R80.30 take 210 and higher</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/sk168513-Cpu-on-first-instances-high-on-R80-30-take-210-and/m-p/107773#M14452</link>
      <description>&lt;P&gt;For VSX JHF T227 or above is needed.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Jan 2021 22:46:03 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/sk168513-Cpu-on-first-instances-high-on-R80-30-take-210-and/m-p/107773#M14452</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2021-01-13T22:46:03Z</dc:date>
    </item>
    <item>
      <title>Re: sk168513 - Cpu on first instances high on R80.30 take 210 and higher</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/sk168513-Cpu-on-first-instances-high-on-R80-30-take-210-and/m-p/107804#M14463</link>
      <description>&lt;P&gt;We are running VSX and the issue was solved for us after installing take 219&lt;BR /&gt;I never tried the workaround.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Jan 2021 09:02:48 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/sk168513-Cpu-on-first-instances-high-on-R80-30-take-210-and/m-p/107804#M14463</guid>
      <dc:creator>Mattias_Jansson</dc:creator>
      <dc:date>2021-01-14T09:02:48Z</dc:date>
    </item>
  </channel>
</rss>

