<?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 interface creation issue in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-interface-creation-issue/m-p/169406#M30662</link>
    <description>&lt;P&gt;try to force fetching conf file by vsx fetch on affected vs&amp;nbsp;&lt;A href="https://sc1.checkpoint.com/documents/R81/WebAdminGuides/EN/CP_R81_VSX_AdminGuide/Topics-VSXG/CLI/vsx-fetch.htm" target="_blank"&gt;https://sc1.checkpoint.com/documents/R81/WebAdminGuides/EN/CP_R81_VSX_AdminGuide/Topics-VSXG/CLI/vsx-fetch.htm&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;please compare fwkern.conf files from both member&lt;/P&gt;</description>
    <pubDate>Fri, 27 Jan 2023 12:05:42 GMT</pubDate>
    <dc:creator>CheckPointerXL</dc:creator>
    <dc:date>2023-01-27T12:05:42Z</dc:date>
    <item>
      <title>VSX interface creation issue</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-interface-creation-issue/m-p/169070#M30625</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;We have 3 VSX appliances which work in VSLS mode. I created new regular VLAN interface (bond0.111) on one of the virtual systems. Everything on the management seemed fine, but after that I noticed that VLAN interface was created only on one of the VSX members and it's missing on the others. Hence currently we have only one Active VS and the others are in DOWN state, which is a normal behaviour after one of the VSs has more interfaces than the others. I didn't try to add the interface manually on the other two members, because we prefer to configure everything on the VSX cluster from the SmartConsole. We've never seen that issue on the previous version R80.30. It started when we upgraded to R81.10. I have tried cpstop/cpstart on the affected VS, but it didn't help. I know we can try to create the missing interface manually, but this is not the point. I want when I create something from the SmartConsole to be working properly.&lt;/P&gt;&lt;P&gt;The software version of the VSX appliances is R81.10 with JHF Take 45.&lt;/P&gt;&lt;P&gt;Have you ever seen similar issue on your environments? Ticket was opened also to TAC.&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Thu, 26 Jan 2023 01:44:17 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-interface-creation-issue/m-p/169070#M30625</guid>
      <dc:creator>mk1</dc:creator>
      <dc:date>2023-01-26T01:44:17Z</dc:date>
    </item>
    <item>
      <title>Re: VSX interface creation issue</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-interface-creation-issue/m-p/169403#M30659</link>
      <description>&lt;P&gt;Can you provide a screenshot that the VLAN is existing in one member and not in the other one?&lt;/P&gt;
&lt;DIV id="gtx-trans" style="position: absolute; left: 149px; top: 28px;"&gt;
&lt;DIV class="gtx-trans-icon"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Fri, 27 Jan 2023 11:37:41 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-interface-creation-issue/m-p/169403#M30659</guid>
      <dc:creator>CheckPointerXL</dc:creator>
      <dc:date>2023-01-27T11:37:41Z</dc:date>
    </item>
    <item>
      <title>Re: VSX interface creation issue</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-interface-creation-issue/m-p/169405#M30661</link>
      <description>&lt;P&gt;Sure. In the attached screenshots you can see the VLAN interface is created on both members, but by some reason it's not part of cluster interfaces. You can see that from cphaprob -a if output.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jan 2023 11:57:41 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-interface-creation-issue/m-p/169405#M30661</guid>
      <dc:creator>mk1</dc:creator>
      <dc:date>2023-01-27T11:57:41Z</dc:date>
    </item>
    <item>
      <title>Re: VSX interface creation issue</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-interface-creation-issue/m-p/169406#M30662</link>
      <description>&lt;P&gt;try to force fetching conf file by vsx fetch on affected vs&amp;nbsp;&lt;A href="https://sc1.checkpoint.com/documents/R81/WebAdminGuides/EN/CP_R81_VSX_AdminGuide/Topics-VSXG/CLI/vsx-fetch.htm" target="_blank"&gt;https://sc1.checkpoint.com/documents/R81/WebAdminGuides/EN/CP_R81_VSX_AdminGuide/Topics-VSXG/CLI/vsx-fetch.htm&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;please compare fwkern.conf files from both member&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jan 2023 12:05:42 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-interface-creation-issue/m-p/169406#M30662</guid>
      <dc:creator>CheckPointerXL</dc:creator>
      <dc:date>2023-01-27T12:05:42Z</dc:date>
    </item>
    <item>
      <title>Re: VSX interface creation issue</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-interface-creation-issue/m-p/169408#M30664</link>
      <description>&lt;P&gt;fwkern.conf is identical on all 3 members. I will try "vsx fetch" together with removing and adding the interface again, if vsx fetch doesn't help. This is the second time we face similar issue since we upgraded to R81.10 and I'm afraid we will face it again in future and won't be good if we have to run "vsx fetch" or another manual command every time. I'm waiting TAC for some&amp;nbsp;reasonable explanation.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jan 2023 12:14:01 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-interface-creation-issue/m-p/169408#M30664</guid>
      <dc:creator>mk1</dc:creator>
      <dc:date>2023-01-27T12:14:01Z</dc:date>
    </item>
    <item>
      <title>Re: VSX interface creation issue</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-interface-creation-issue/m-p/169409#M30665</link>
      <description>&lt;P&gt;ok, share the fix when TAC's job will be done &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;DIV id="gtx-trans" style="position: absolute; left: 2px; top: 28px;"&gt;
&lt;DIV class="gtx-trans-icon"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Fri, 27 Jan 2023 12:15:52 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-interface-creation-issue/m-p/169409#M30665</guid>
      <dc:creator>CheckPointerXL</dc:creator>
      <dc:date>2023-01-27T12:15:52Z</dc:date>
    </item>
    <item>
      <title>Re: VSX interface creation issue</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-interface-creation-issue/m-p/172608#M31367</link>
      <description>&lt;P&gt;&lt;SPAN&gt;sk92784 solved the issue.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Feb 2023 07:03:30 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-interface-creation-issue/m-p/172608#M31367</guid>
      <dc:creator>mk1</dc:creator>
      <dc:date>2023-02-24T07:03:30Z</dc:date>
    </item>
  </channel>
</rss>

