<?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 Check Point 6700 believes it's a 3800 in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Check-Point-6700-believes-it-s-a-3800/m-p/159172#M27831</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We received a pair of new 6700 appliances today.&lt;BR /&gt;&lt;SPAN&gt;Out of the box, on R81, we were unable to get the Mgmt or eth1 interface working.&lt;BR /&gt;&lt;/SPAN&gt;Switching to R80.40 on the boot menu failed (automatic reboot during boot).&lt;BR /&gt;Updating the system with ISOmorphic failed (same).&lt;BR /&gt;We were able to manually update to R81.10 from USB, but the network issue remained.&lt;/P&gt;&lt;P&gt;Then I realized that there was a problem with the network interface naming.&lt;BR /&gt;The logical Mgmt interface was actually mapped to the eth1 physical port, and some interface names had the "_rename" suffix attached to them.&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;gw-c0571d&amp;gt; show interfaces&lt;BR /&gt;Mgmt&lt;BR /&gt;eth0&lt;BR /&gt;eth1&lt;BR /&gt;eth2&lt;BR /&gt;eth3&lt;BR /&gt;eth4&lt;BR /&gt;eth5&lt;BR /&gt;eth6&lt;BR /&gt;eth7&lt;BR /&gt;eth8&lt;BR /&gt;eth9&lt;BR /&gt;eth10_rename&lt;BR /&gt;eth11_rename&lt;BR /&gt;eth12&lt;BR /&gt;lo&lt;BR /&gt;gw-c0571d&amp;gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We were then able to get a working WebUI... only to discover that the appliance model displayed is "3800".&lt;BR /&gt;"dmidecode -t system" still shows its SKU is QM-15, which mean its a 6700 appliance indeed (phew) as per&amp;nbsp;sk37692.&lt;/P&gt;&lt;P&gt;The appliance model misdetection seems to be the cause to the network interface mismatch, as the interface count and naming on a 3800 is not the same, and makes the onboot interface rename fail.&lt;/P&gt;&lt;P&gt;It seems like in this modern world, Check Point appliances won't accept the model that was "assigned" to them...&lt;/P&gt;&lt;P&gt;Does this look like a known issue?&lt;BR /&gt;Is there an easy fix for this?&lt;/P&gt;&lt;P&gt;NB: Before you ask, this was raised to TAC, remote session scheduled for tomorrow.&lt;/P&gt;</description>
    <pubDate>Mon, 10 Oct 2022 17:31:10 GMT</pubDate>
    <dc:creator>nmelay</dc:creator>
    <dc:date>2022-10-10T17:31:10Z</dc:date>
    <item>
      <title>Check Point 6700 believes it's a 3800</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Check-Point-6700-believes-it-s-a-3800/m-p/159172#M27831</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We received a pair of new 6700 appliances today.&lt;BR /&gt;&lt;SPAN&gt;Out of the box, on R81, we were unable to get the Mgmt or eth1 interface working.&lt;BR /&gt;&lt;/SPAN&gt;Switching to R80.40 on the boot menu failed (automatic reboot during boot).&lt;BR /&gt;Updating the system with ISOmorphic failed (same).&lt;BR /&gt;We were able to manually update to R81.10 from USB, but the network issue remained.&lt;/P&gt;&lt;P&gt;Then I realized that there was a problem with the network interface naming.&lt;BR /&gt;The logical Mgmt interface was actually mapped to the eth1 physical port, and some interface names had the "_rename" suffix attached to them.&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;gw-c0571d&amp;gt; show interfaces&lt;BR /&gt;Mgmt&lt;BR /&gt;eth0&lt;BR /&gt;eth1&lt;BR /&gt;eth2&lt;BR /&gt;eth3&lt;BR /&gt;eth4&lt;BR /&gt;eth5&lt;BR /&gt;eth6&lt;BR /&gt;eth7&lt;BR /&gt;eth8&lt;BR /&gt;eth9&lt;BR /&gt;eth10_rename&lt;BR /&gt;eth11_rename&lt;BR /&gt;eth12&lt;BR /&gt;lo&lt;BR /&gt;gw-c0571d&amp;gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We were then able to get a working WebUI... only to discover that the appliance model displayed is "3800".&lt;BR /&gt;"dmidecode -t system" still shows its SKU is QM-15, which mean its a 6700 appliance indeed (phew) as per&amp;nbsp;sk37692.&lt;/P&gt;&lt;P&gt;The appliance model misdetection seems to be the cause to the network interface mismatch, as the interface count and naming on a 3800 is not the same, and makes the onboot interface rename fail.&lt;/P&gt;&lt;P&gt;It seems like in this modern world, Check Point appliances won't accept the model that was "assigned" to them...&lt;/P&gt;&lt;P&gt;Does this look like a known issue?&lt;BR /&gt;Is there an easy fix for this?&lt;/P&gt;&lt;P&gt;NB: Before you ask, this was raised to TAC, remote session scheduled for tomorrow.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Oct 2022 17:31:10 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Check-Point-6700-believes-it-s-a-3800/m-p/159172#M27831</guid>
      <dc:creator>nmelay</dc:creator>
      <dc:date>2022-10-10T17:31:10Z</dc:date>
    </item>
    <item>
      <title>Re: Check Point 6700 believes it's a 3800</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Check-Point-6700-believes-it-s-a-3800/m-p/159182#M27836</link>
      <description>&lt;P&gt;Yeah, this is definitely TAC case territory.&lt;/P&gt;
&lt;P&gt;For R80.40, you need a special image linked here:&amp;nbsp;&lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk139932&amp;amp;partition=Basic&amp;amp;product=Quantum" target="_blank"&gt;https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk139932&amp;amp;partition=Basic&amp;amp;product=Quantum&lt;/A&gt;&lt;BR /&gt;R81/R81.10 should use the standard image...and I would expect a 6700 should be detected properly.&lt;BR /&gt;You can try this procedure, but it's for Open Servers:&amp;nbsp;&lt;A href="https://supportcenter.us.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk69621&amp;amp;partition=Expert&amp;amp;product=Quantum" target="_blank"&gt;https://supportcenter.us.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk69621&amp;amp;partition=Expert&amp;amp;product=Quantum&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Oct 2022 19:12:27 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Check-Point-6700-believes-it-s-a-3800/m-p/159182#M27836</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2022-10-10T19:12:27Z</dc:date>
    </item>
    <item>
      <title>Re: Check Point 6700 believes it's a 3800</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Check-Point-6700-believes-it-s-a-3800/m-p/159201#M27838</link>
      <description>&lt;P&gt;We used the generic R81.10 Take 335 image, which as you said is supposed to detect 6700's properly.&lt;/P&gt;&lt;P&gt;The Open Servers interface rename procedure won't work indeed, and&amp;nbsp;&lt;A title="Interfaces have names such as 'eth3_rename' and 'eth4_rename' in Gaia OS" href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk97446" target="_self"&gt;sk97446&lt;/A&gt; explains the udev rules file used for interface (re-)naming is selected according to the appliance model.&lt;/P&gt;&lt;P&gt;Which brings us back to the wrong appliance model being detected/selected.&lt;/P&gt;&lt;P&gt;What really worries me is we both have issues with the installed system and are unable to boot on a new ISO.&lt;BR /&gt;Oh well, we were also unable to boot on the factory reset partitions, or the diagnostics partition.&lt;BR /&gt;Smells like RMA.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Oct 2022 23:59:02 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Check-Point-6700-believes-it-s-a-3800/m-p/159201#M27838</guid>
      <dc:creator>nmelay</dc:creator>
      <dc:date>2022-10-10T23:59:02Z</dc:date>
    </item>
    <item>
      <title>Re: Check Point 6700 believes it's a 3800</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Check-Point-6700-believes-it-s-a-3800/m-p/159203#M27839</link>
      <description>&lt;P&gt;Agree 100% with you, definitely "smells" like RMA.&lt;/P&gt;</description>
      <pubDate>Tue, 11 Oct 2022 01:01:04 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Check-Point-6700-believes-it-s-a-3800/m-p/159203#M27839</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2022-10-11T01:01:04Z</dc:date>
    </item>
    <item>
      <title>Re: Check Point 6700 believes it's a 3800</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Check-Point-6700-believes-it-s-a-3800/m-p/159716#M28036</link>
      <description>&lt;P&gt;Just curious, what is your current status with this?&lt;/P&gt;</description>
      <pubDate>Mon, 17 Oct 2022 11:00:36 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Check-Point-6700-believes-it-s-a-3800/m-p/159716#M28036</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2022-10-17T11:00:36Z</dc:date>
    </item>
    <item>
      <title>Re: Check Point 6700 believes it's a 3800</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Check-Point-6700-believes-it-s-a-3800/m-p/159884#M28120</link>
      <description>&lt;P&gt;TAC is still working on it, but this got nowhere so far.&lt;BR /&gt;We've been told one other customer hit the same issue.&lt;/P&gt;&lt;P&gt;We asked for a RMA, waiting for the delivery.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Oct 2022 19:17:20 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Check-Point-6700-believes-it-s-a-3800/m-p/159884#M28120</guid>
      <dc:creator>nmelay</dc:creator>
      <dc:date>2022-10-18T19:17:20Z</dc:date>
    </item>
  </channel>
</rss>

