<?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: VSX UPPAK issues in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/VSX-UPPAK-issues/m-p/258525#M43669</link>
    <description>&lt;P&gt;For the first issue, no TX errors or carrier transitions on any interfaces.&lt;BR /&gt;&lt;BR /&gt;As for the second issue, see the attached outputs.&lt;BR /&gt;RX-ERR,&amp;nbsp;rx_length_errors.nic&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 30 Sep 2025 07:57:23 GMT</pubDate>
    <dc:creator>sebfuuu</dc:creator>
    <dc:date>2025-09-30T07:57:23Z</dc:date>
    <item>
      <title>VSX UPPAK issues</title>
      <link>https://community.checkpoint.com/t5/General-Topics/VSX-UPPAK-issues/m-p/258287#M43586</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;I noticed a few interesting issues with VSX and UPPAK.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Appliance 9300&lt;BR /&gt;R81.20 JHF 111&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;* First issue:&lt;/P&gt;&lt;P&gt;When traffic goes through two different VS in the same VSX hardware via a Virtual Switch we see 1-2% "packet-loss"&lt;/P&gt;&lt;P&gt;With zdebug we see this output that matches the traffic:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;@;628145396.20082;[uspace];[tid_1];[SIM4];prepare_cut_through:do_routing returned invalid out_ifn 65535, conn:&amp;lt;x.x.x.x,53,y.y.y.y,46771,17&amp;gt;;&lt;/P&gt;&lt;P&gt;@;628145396.20083;[uspace];[tid_1];[SIM4];sim_pkt_send_drop_notification:(5,0) received drop, reason: Interface Down (8), conn:&amp;lt;y.y.y.y,46771,x.x.x.x,53,17&amp;gt;;&lt;/P&gt;&lt;P&gt;@;628145396.20084;[uspace];[tid_1];[SIM4];sim_pkt_send_drop_notification:no track is needed for this drop - not sending a notificaion, conn:&amp;lt;y.y.y.y,46771,x.x.x.x,53,17&amp;gt;;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It is always dropped on the first VS, it does not matter what traffic and which VS.&lt;/P&gt;&lt;P&gt;(More than two VS see this behavior)&lt;/P&gt;&lt;P&gt;After change of the SecureXL mode from UPPAK to KPPAK this issues goes away.&lt;/P&gt;&lt;P&gt;TAC case was raised but the customer was not willing to share the data needed to proceed with the case at that time.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;* Second issue:&lt;/P&gt;&lt;P&gt;After SecureXL mode change to KPPAK we get RX errors on a lot on 10g fiber interfaces.&lt;/P&gt;&lt;P&gt;We have confirmed this on four 9300 hardware (two diffrent clusters).&lt;/P&gt;&lt;P&gt;If you switch to UPPAK, the errors goes away.&lt;/P&gt;&lt;P&gt;If you go back to KPPAK you get the same amount of errors on the same interfaces.&lt;/P&gt;&lt;P&gt;Reboot of FW/Switch or disconnect/reconnect of SFP and cable does not have any impact.&lt;/P&gt;&lt;P&gt;No TAC case raised yet.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have not seen these issues on larger 9xxx appliances with VSX.&lt;/P&gt;&lt;P&gt;So one guess would be the Intel E-cores / P-cores architecture. (Like sk183438)&lt;/P&gt;&lt;P&gt;USFW is used.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The questions I have for the community.&lt;/P&gt;&lt;P&gt;Have anyone seen any issues like this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks again to everyone for this great community.&lt;/P&gt;&lt;P&gt;/Seb&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 26 Sep 2025 07:57:12 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/VSX-UPPAK-issues/m-p/258287#M43586</guid>
      <dc:creator>sebfuuu</dc:creator>
      <dc:date>2025-09-26T07:57:12Z</dc:date>
    </item>
    <item>
      <title>Re: VSX UPPAK issues</title>
      <link>https://community.checkpoint.com/t5/General-Topics/VSX-UPPAK-issues/m-p/258290#M43589</link>
      <description>&lt;P&gt;Your experiences mirrors ours.&lt;/P&gt;
&lt;P&gt;Furthermore we have a 9400 vsx cluster waiting to be onboarded with production traffic still with no VSs built.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;One node becomes unresponsive every 2-4 days and needs to be power cycled from LOM. We made RMA of both nodes. Same result. The node crashing in the cluster varies. jumbo t113&lt;/P&gt;
&lt;P&gt;We are investigating options to replace the model to 9700+&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;/Henrik&lt;/P&gt;</description>
      <pubDate>Fri, 26 Sep 2025 08:55:33 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/VSX-UPPAK-issues/m-p/258290#M43589</guid>
      <dc:creator>Henrik_Noerr1</dc:creator>
      <dc:date>2025-09-26T08:55:33Z</dc:date>
    </item>
    <item>
      <title>Re: VSX UPPAK issues</title>
      <link>https://community.checkpoint.com/t5/General-Topics/VSX-UPPAK-issues/m-p/258382#M43616</link>
      <description>&lt;P&gt;RX buffers could be related with:&amp;nbsp;&lt;A href="https://support.checkpoint.com/results/sk/sk182825" target="_blank"&gt;https://support.checkpoint.com/results/sk/sk182825&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;does not 100% match&lt;/P&gt;</description>
      <pubDate>Sat, 27 Sep 2025 19:10:40 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/VSX-UPPAK-issues/m-p/258382#M43616</guid>
      <dc:creator>Lesley</dc:creator>
      <dc:date>2025-09-27T19:10:40Z</dc:date>
    </item>
    <item>
      <title>Re: VSX UPPAK issues</title>
      <link>https://community.checkpoint.com/t5/General-Topics/VSX-UPPAK-issues/m-p/258387#M43621</link>
      <description>&lt;P&gt;You could install jumbo 113, which is recommended and see if it helps. If not, I would certainly open TAC case for this.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Sun, 28 Sep 2025 12:01:00 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/VSX-UPPAK-issues/m-p/258387#M43621</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-09-28T12:01:00Z</dc:date>
    </item>
    <item>
      <title>Re: VSX UPPAK issues</title>
      <link>https://community.checkpoint.com/t5/General-Topics/VSX-UPPAK-issues/m-p/258394#M43626</link>
      <description>&lt;P&gt;For the first issue, are you seeing TX errors in the output of &lt;STRONG&gt;netstat -ni&lt;/STRONG&gt;?&amp;nbsp; I practically never saw TX errors with KPPAK, but with UPPAK they seem much more likely now.&amp;nbsp; If you run &lt;STRONG&gt;ifconfig -a&lt;/STRONG&gt; are you seeing any carrier transitions on any interfaces?&amp;nbsp; That "interface down" message is weird.&lt;/P&gt;
&lt;P&gt;For the second issue what specific type of RX errors are you seeing (OVR,ERR,DRP)?&amp;nbsp; Can you please post the &lt;STRONG&gt;netstat -ni&lt;/STRONG&gt; output including the interface seeing the RX errors along with &lt;STRONG&gt;ethtool -S (interface)&lt;/STRONG&gt; for the affected 10Gbit interface?&amp;nbsp; If the RX problems are RX-DRP, it is possible it is "junk" traffic for invalid VLAN tags and/or invalid EtherType protocols.&amp;nbsp; UPPAK might not increment the RX-DRP counter for this junk traffic like KPPAK does.&amp;nbsp; See here:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.checkpoint.com/results/sk/sk166424" target="_blank" rel="noopener"&gt;&lt;SPAN&gt;sk166424: Number of RX packet drops on interfaces increases on a Security Gateway R80.30 and higher with Gaia kernel 3.10&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.checkpoint.com/results/sk/sk183847" target="_blank" rel="noopener"&gt;sk183847: RX-ERR and&amp;nbsp;RX-DRP&amp;nbsp;Counters on Bonded Ports&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 28 Sep 2025 13:37:22 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/VSX-UPPAK-issues/m-p/258394#M43626</guid>
      <dc:creator>Timothy_Hall</dc:creator>
      <dc:date>2025-09-28T13:37:22Z</dc:date>
    </item>
    <item>
      <title>Re: VSX UPPAK issues</title>
      <link>https://community.checkpoint.com/t5/General-Topics/VSX-UPPAK-issues/m-p/258395#M43627</link>
      <description>&lt;P&gt;Your crashes are almost certainly related to P-Cores/E-Cores on the 9300/9400.&amp;nbsp; Not sure what the heck Intel was thinking implementing this in a server-based architecture, as opposed to just mobile architectures where battery life is important.&amp;nbsp; However, one could argue that the same criticism applies to many of Intel's recent leadership decisions, which is why the company is currently in such big trouble.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.checkpoint.com/results/sk/sk183438" target="_blank" rel="noopener"&gt;&lt;SPAN&gt;sk183438: Stability issue in Check Point appliances 9300 and 9400&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 28 Sep 2025 13:42:30 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/VSX-UPPAK-issues/m-p/258395#M43627</guid>
      <dc:creator>Timothy_Hall</dc:creator>
      <dc:date>2025-09-28T13:42:30Z</dc:date>
    </item>
    <item>
      <title>Re: VSX UPPAK issues</title>
      <link>https://community.checkpoint.com/t5/General-Topics/VSX-UPPAK-issues/m-p/258525#M43669</link>
      <description>&lt;P&gt;For the first issue, no TX errors or carrier transitions on any interfaces.&lt;BR /&gt;&lt;BR /&gt;As for the second issue, see the attached outputs.&lt;BR /&gt;RX-ERR,&amp;nbsp;rx_length_errors.nic&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Sep 2025 07:57:23 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/VSX-UPPAK-issues/m-p/258525#M43669</guid>
      <dc:creator>sebfuuu</dc:creator>
      <dc:date>2025-09-30T07:57:23Z</dc:date>
    </item>
    <item>
      <title>Re: VSX UPPAK issues</title>
      <link>https://community.checkpoint.com/t5/General-Topics/VSX-UPPAK-issues/m-p/258526#M43670</link>
      <description>&lt;P data-unlink="true"&gt;Found this SK:&amp;nbsp;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;sk183040&lt;BR /&gt;&lt;BR /&gt;"&amp;nbsp;This not a Check Point issue. The issue is cosmetic and does not have an effect on network traffic flows. The rx_length_errors statistic is not meaningful and can be safely ignored.&lt;BR /&gt;&lt;BR /&gt;According to Linux kernel commit f9f9de23dc88, the statistic was removed from the ice driver in the upstream Linux kernel due to its lack of relevance.&lt;BR /&gt;"&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;I have checked and "ice" driver is used on the interface&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Sep 2025 08:17:42 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/VSX-UPPAK-issues/m-p/258526#M43670</guid>
      <dc:creator>sebfuuu</dc:creator>
      <dc:date>2025-09-30T08:17:42Z</dc:date>
    </item>
    <item>
      <title>Re: VSX UPPAK issues</title>
      <link>https://community.checkpoint.com/t5/General-Topics/VSX-UPPAK-issues/m-p/258755#M43733</link>
      <description>&lt;P&gt;Thanks for letting us know!&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Thu, 02 Oct 2025 00:00:05 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/VSX-UPPAK-issues/m-p/258755#M43733</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-10-02T00:00:05Z</dc:date>
    </item>
  </channel>
</rss>

