<?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: Problemas restoring the 2nd node of a VSX cluster in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/Problemas-restoring-the-2nd-node-of-a-VSX-cluster/m-p/241594#M40340</link>
    <description>&lt;P&gt;Always configure Active UP before operation like this&lt;/P&gt;
&lt;P&gt;You cluster config was probably Primary UP&lt;/P&gt;</description>
    <pubDate>Tue, 18 Feb 2025 22:20:08 GMT</pubDate>
    <dc:creator>CheckPointerXL</dc:creator>
    <dc:date>2025-02-18T22:20:08Z</dc:date>
    <item>
      <title>Problemas restoring the 2nd node of a VSX cluster</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Problemas-restoring-the-2nd-node-of-a-VSX-cluster/m-p/239887#M40042</link>
      <description>&lt;P&gt;Hi all!&lt;/P&gt;&lt;P&gt;We had a full crash on both VSX gateways of a 2 node VSX cluster.&lt;BR /&gt;Versions (SMS R81.20 / VSX gateways R80.40)&lt;/P&gt;&lt;P&gt;We managed to restore the first node using vsx_util reconfigure getting a working cluster with a single working node.&lt;/P&gt;&lt;P&gt;Tried to restore the second one using the same method but just after the command vsx_util reconfigure command finished (so the gateway is set into VSX mode and received via push the configurations and virtual systems), many communications started to fail.&lt;/P&gt;&lt;P&gt;Checking the first node status with "cphaprob state" showed that 2 out of 4 virtual devices were in standby mode. So supposedly the 2nd node that was still in process of being restored (there were tasks still to be done: reboot, configure the license, configure local.arp, enable dynamic objects, install policies...) had 2 virtual devices in Active state.&lt;/P&gt;&lt;P&gt;Tried to "cphaprob state" and "clusterxl_admin down" to force failover but these commands did not show any output and nothing changed in the status of the virtual devices on the 1st node. Disconnecting interfaces on 2nd node didnt change anything either.&lt;BR /&gt;Shutting down this 2nd node made the first node be the active one for all virtual systems.&lt;/P&gt;&lt;P&gt;- why did the node become active for the virtual devices while still not fully restored?&lt;BR /&gt;- is there any way to avoid this behaviour?&lt;BR /&gt;- what would be the correct procedure?&lt;/P&gt;&lt;P&gt;Thanks all!&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2025 20:34:31 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Problemas-restoring-the-2nd-node-of-a-VSX-cluster/m-p/239887#M40042</guid>
      <dc:creator>Wipeout</dc:creator>
      <dc:date>2025-01-28T20:34:31Z</dc:date>
    </item>
    <item>
      <title>Re: Problemas restoring the 2nd node of a VSX cluster</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Problemas-restoring-the-2nd-node-of-a-VSX-cluster/m-p/239898#M40045</link>
      <description>&lt;P&gt;Sounds like you did everything right. Other than checking the logs to see if there is anything obvious, I would definitely open the TAC case to see if they can provide a reason.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2025 21:36:04 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Problemas-restoring-the-2nd-node-of-a-VSX-cluster/m-p/239898#M40045</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-01-28T21:36:04Z</dc:date>
    </item>
    <item>
      <title>Re: Problemas restoring the 2nd node of a VSX cluster</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Problemas-restoring-the-2nd-node-of-a-VSX-cluster/m-p/239900#M40046</link>
      <description>&lt;P&gt;Is the reason for the initial crash understood and resolved?&lt;/P&gt;
&lt;P&gt;Which JHF is the cluster using? (R80.40 is EOL)&lt;/P&gt;
&lt;P&gt;The VSX recovery procedure is outlined in&amp;nbsp;&lt;SPAN&gt;sk101515.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jan 2025 13:33:23 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Problemas-restoring-the-2nd-node-of-a-VSX-cluster/m-p/239900#M40046</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2025-01-29T13:33:23Z</dc:date>
    </item>
    <item>
      <title>Re: Problemas restoring the 2nd node of a VSX cluster</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Problemas-restoring-the-2nd-node-of-a-VSX-cluster/m-p/239923#M40048</link>
      <description>&lt;P&gt;Do you have VSLS in use? I can imagine that as soon as second member's VS is standby, VSLS will fire and make sure the load is 1:1 between nodes.&lt;/P&gt;
&lt;P&gt;Did you check output of "cphaprob -a if" ? Maybe one member had different number of required interfaces which in many cases trigger unplanned failover.&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jan 2025 06:41:56 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Problemas-restoring-the-2nd-node-of-a-VSX-cluster/m-p/239923#M40048</guid>
      <dc:creator>JozkoMrkvicka</dc:creator>
      <dc:date>2025-01-29T06:41:56Z</dc:date>
    </item>
    <item>
      <title>Re: Problemas restoring the 2nd node of a VSX cluster</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Problemas-restoring-the-2nd-node-of-a-VSX-cluster/m-p/239930#M40049</link>
      <description>&lt;P&gt;Is the reason for the initial crash understood and resolved? Which JHF is the cluster using?&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;It was when trying to recover a deleted virtual system. So supposedly it will not crash unless doing the same actions.&lt;/P&gt;&lt;P&gt;The VSX recovery procedure is outlined in&amp;nbsp;&lt;SPAN&gt;sk101515.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Thanks, that was just was i needed.&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Just a doubt, step 10 shows the way to prevent the cluster member from becoming active before the reconfig ends by using cphastop,cphaconf... After rebooting it requires any command to make it become active?&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Thanks!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jan 2025 08:02:39 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Problemas-restoring-the-2nd-node-of-a-VSX-cluster/m-p/239930#M40049</guid>
      <dc:creator>Wipeout_</dc:creator>
      <dc:date>2025-01-29T08:02:39Z</dc:date>
    </item>
    <item>
      <title>Re: Problemas restoring the 2nd node of a VSX cluster</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Problemas-restoring-the-2nd-node-of-a-VSX-cluster/m-p/239967#M40054</link>
      <description>&lt;P&gt;I would suggest to open a SR# with TAC to get the issue resolved ! You are aware of the fact that version&amp;nbsp;R80.40 is out of support since April 2024 ?&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jan 2025 13:25:18 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Problemas-restoring-the-2nd-node-of-a-VSX-cluster/m-p/239967#M40054</guid>
      <dc:creator>G_W_Albrecht</dc:creator>
      <dc:date>2025-01-29T13:25:18Z</dc:date>
    </item>
    <item>
      <title>Re: Problemas restoring the 2nd node of a VSX cluster</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Problemas-restoring-the-2nd-node-of-a-VSX-cluster/m-p/241594#M40340</link>
      <description>&lt;P&gt;Always configure Active UP before operation like this&lt;/P&gt;
&lt;P&gt;You cluster config was probably Primary UP&lt;/P&gt;</description>
      <pubDate>Tue, 18 Feb 2025 22:20:08 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Problemas-restoring-the-2nd-node-of-a-VSX-cluster/m-p/241594#M40340</guid>
      <dc:creator>CheckPointerXL</dc:creator>
      <dc:date>2025-02-18T22:20:08Z</dc:date>
    </item>
    <item>
      <title>Re: Problemas restoring the 2nd node of a VSX cluster</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Problemas-restoring-the-2nd-node-of-a-VSX-cluster/m-p/241623#M40347</link>
      <description>&lt;P&gt;Sorry for the late response.&lt;BR /&gt;Yes, i was aware. But first of all i wanted to restore the cluster with adding extra factors.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 19 Feb 2025 09:36:47 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Problemas-restoring-the-2nd-node-of-a-VSX-cluster/m-p/241623#M40347</guid>
      <dc:creator>Wipeout</dc:creator>
      <dc:date>2025-02-19T09:36:47Z</dc:date>
    </item>
    <item>
      <title>Re: Problemas restoring the 2nd node of a VSX cluster</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Problemas-restoring-the-2nd-node-of-a-VSX-cluster/m-p/241624#M40348</link>
      <description>&lt;P&gt;My cluster is active-standby.Not VSLS.&lt;BR /&gt;With the sk101515 Chris_Atkinson commented, everything went ok&lt;/P&gt;</description>
      <pubDate>Wed, 19 Feb 2025 09:39:08 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Problemas-restoring-the-2nd-node-of-a-VSX-cluster/m-p/241624#M40348</guid>
      <dc:creator>Wipeout</dc:creator>
      <dc:date>2025-02-19T09:39:08Z</dc:date>
    </item>
    <item>
      <title>Re: Problemas restoring the 2nd node of a VSX cluster</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Problemas-restoring-the-2nd-node-of-a-VSX-cluster/m-p/241626#M40349</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Finally the sk101515 gives steps to avoid the problem of the second node becoming active unexpectedly while installing&lt;BR /&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Feb 2025 09:40:57 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Problemas-restoring-the-2nd-node-of-a-VSX-cluster/m-p/241626#M40349</guid>
      <dc:creator>Wipeout</dc:creator>
      <dc:date>2025-02-19T09:40:57Z</dc:date>
    </item>
    <item>
      <title>Re: Problemas restoring the 2nd node of a VSX cluster</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Problemas-restoring-the-2nd-node-of-a-VSX-cluster/m-p/241627#M40350</link>
      <description>&lt;P&gt;Thanks Chris! Sorry for the late response.&lt;BR /&gt;The sk101515 went flawless.&amp;nbsp;&lt;BR /&gt;I would only add another step. After the vsx_util reconfigure and before the reboot, i would set virtual devices down (with persistence flag) using&amp;nbsp; clusterXL_admin.&lt;BR /&gt;Then reboot, add the cables, perform the pushes, install the required policies and perform configurations (f.e. for certain configurations, internet access is a prerequisite).&amp;nbsp;&lt;BR /&gt;After that the different Virtual Devices can be checked one by one via clusterXL_admin&lt;BR /&gt;&lt;BR /&gt;Thanks again!&lt;/P&gt;</description>
      <pubDate>Wed, 19 Feb 2025 09:46:23 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Problemas-restoring-the-2nd-node-of-a-VSX-cluster/m-p/241627#M40350</guid>
      <dc:creator>Wipeout</dc:creator>
      <dc:date>2025-02-19T09:46:23Z</dc:date>
    </item>
  </channel>
</rss>

