<?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 R80.30 (VSLS cluster)  with 4 members question in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-R80-30-VSLS-cluster-with-4-members-question/m-p/134391#M20130</link>
    <description>&lt;P&gt;At a fundamental level, the impact would be that some VSs can only handle traffic on some members, but that seems like what you're trying to do.&lt;/P&gt;
&lt;P&gt;What exactly is your goal? I would consider a cluster with an active/standby/down/down VS to be broken.&lt;/P&gt;</description>
    <pubDate>Thu, 18 Nov 2021 14:00:41 GMT</pubDate>
    <dc:creator>Bob_Zimmerman</dc:creator>
    <dc:date>2021-11-18T14:00:41Z</dc:date>
    <item>
      <title>VSX R80.30 (VSLS cluster)  with 4 members question</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-R80-30-VSLS-cluster-with-4-members-question/m-p/134373#M20129</link>
      <description>&lt;P&gt;Hello community&lt;/P&gt;&lt;P&gt;On my lab I have a cluster VSX R80.30 (VSLS cluster) with 4 members.&lt;/P&gt;&lt;P&gt;Also i have configured a Virtual System that is Active on VSX A , Standby on VSX B and Backup on VSX C and Backup on VSX D.&lt;/P&gt;&lt;P&gt;What is the recommended way to stop the VS from being even backup on VSXC and on VSXD and instead being on DOWN state.&lt;/P&gt;&lt;P&gt;From skes i have read that the recommended way to failover is through vsx_util vsls but the above is something different.&lt;/P&gt;&lt;P&gt;The other way i have thought is to login on Virtual System on VSXC and on VSXD and execute clusterXL_admin down.&lt;/P&gt;&lt;P&gt;After that when i want the VS to be in BACKUP state again execute clusterXL_admin up on VS on VSXC and VSXD.&lt;/P&gt;&lt;P&gt;Do you see any impact on the above steps?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;Kostas&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;&amp;nbsp;&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;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Nov 2021 11:37:34 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-R80-30-VSLS-cluster-with-4-members-question/m-p/134373#M20129</guid>
      <dc:creator>KostasGR</dc:creator>
      <dc:date>2021-11-18T11:37:34Z</dc:date>
    </item>
    <item>
      <title>Re: VSX R80.30 (VSLS cluster)  with 4 members question</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-R80-30-VSLS-cluster-with-4-members-question/m-p/134391#M20130</link>
      <description>&lt;P&gt;At a fundamental level, the impact would be that some VSs can only handle traffic on some members, but that seems like what you're trying to do.&lt;/P&gt;
&lt;P&gt;What exactly is your goal? I would consider a cluster with an active/standby/down/down VS to be broken.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Nov 2021 14:00:41 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-R80-30-VSLS-cluster-with-4-members-question/m-p/134391#M20130</guid>
      <dc:creator>Bob_Zimmerman</dc:creator>
      <dc:date>2021-11-18T14:00:41Z</dc:date>
    </item>
    <item>
      <title>Re: VSX R80.30 (VSLS cluster)  with 4 members question</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-R80-30-VSLS-cluster-with-4-members-question/m-p/134400#M20132</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/27871"&gt;@Bob_Zimmerman&lt;/a&gt;&lt;/P&gt;&lt;P&gt;Consider a scenario that VSX sync interface between Site A (VSXA VSXB) and Site B (VSXC and VSXD) is lost on layer 2.&lt;/P&gt;&lt;P&gt;So i want the active /standby VS on site A not been impacted at all.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;BR,&lt;BR /&gt;Kostas&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Nov 2021 14:29:28 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-R80-30-VSLS-cluster-with-4-members-question/m-p/134400#M20132</guid>
      <dc:creator>KostasGR</dc:creator>
      <dc:date>2021-11-18T14:29:28Z</dc:date>
    </item>
    <item>
      <title>Re: VSX R80.30 (VSLS cluster)  with 4 members question</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-R80-30-VSLS-cluster-with-4-members-question/m-p/134405#M20135</link>
      <description>&lt;P&gt;At that point, why have VSXC and VSXD in the same cluster? Just make two clusters and run the same policies on both.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Nov 2021 14:45:17 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-R80-30-VSLS-cluster-with-4-members-question/m-p/134405#M20135</guid>
      <dc:creator>Bob_Zimmerman</dc:creator>
      <dc:date>2021-11-18T14:45:17Z</dc:date>
    </item>
    <item>
      <title>Re: VSX R80.30 (VSLS cluster)  with 4 members question</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-R80-30-VSLS-cluster-with-4-members-question/m-p/134446#M20143</link>
      <description>&lt;P&gt;I agree.&lt;/P&gt;
&lt;P&gt;Not really used this but weights could be explored, but in all cases I would not purposely leave a VS in a down state on a VSX appliance.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Nov 2021 20:47:29 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-R80-30-VSLS-cluster-with-4-members-question/m-p/134446#M20143</guid>
      <dc:creator>genisis__</dc:creator>
      <dc:date>2021-11-18T20:47:29Z</dc:date>
    </item>
  </channel>
</rss>

