<?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 (preemption on VS) in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/VSX-preemption-on-VS/m-p/82080#M16590</link>
    <description>&lt;P&gt;We would like the same feature. Do you have any update from Checkpoint if this will be implemented (or already is) in future relases?&lt;/P&gt;</description>
    <pubDate>Thu, 16 Apr 2020 09:02:48 GMT</pubDate>
    <dc:creator>Mattias_Jansson</dc:creator>
    <dc:date>2020-04-16T09:02:48Z</dc:date>
    <item>
      <title>VSX (preemption on VS)</title>
      <link>https://community.checkpoint.com/t5/General-Topics/VSX-preemption-on-VS/m-p/28295#M5737</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi mates,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any possibility of setting preemption (maintaining current active vs. switch to high priority) at VS level on VSX (VSLS) environment ? The goal is to avoid that a specific "critical" VS from switching back and forth in event of some problem. By design it returns to the cluster member where it should stand on recovery / normal condition.&lt;/P&gt;&lt;P&gt;I've been looking at the "vsx_util vsls" options but it doesn't seem to help in this way.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pedro Boavida&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Sep 2018 10:37:54 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/VSX-preemption-on-VS/m-p/28295#M5737</guid>
      <dc:creator>Pedro_Boavida</dc:creator>
      <dc:date>2018-09-20T10:37:54Z</dc:date>
    </item>
    <item>
      <title>Re: VSX (preemption on VS)</title>
      <link>https://community.checkpoint.com/t5/General-Topics/VSX-preemption-on-VS/m-p/28296#M5738</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This should be possible within the &lt;STRONG&gt;vsls_config vsls&lt;/STRONG&gt; main menu.&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://sc1.checkpoint.com/documents/R77/CP_R77_VSX_WebAdminGuide/html_frameset.htm?topic=documents/R77/CP_R77_VSX_WebAdminGuide/5997" title="https://sc1.checkpoint.com/documents/R77/CP_R77_VSX_WebAdminGuide/html_frameset.htm?topic=documents/R77/CP_R77_VSX_WebAdminGuide/5997"&gt;Check Point VSX R77 Versions Administration Guide&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Sep 2018 10:55:28 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/VSX-preemption-on-VS/m-p/28296#M5738</guid>
      <dc:creator>Danny</dc:creator>
      <dc:date>2018-09-20T10:55:28Z</dc:date>
    </item>
    <item>
      <title>Re: VSX (preemption on VS)</title>
      <link>https://community.checkpoint.com/t5/General-Topics/VSX-preemption-on-VS/m-p/28297#M5739</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"vsx_util&amp;nbsp;vsls" or "vsls_config vsls" are pretty much the same command and the kind of behavior I'm asking about is not available there.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Sep 2018 14:03:24 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/VSX-preemption-on-VS/m-p/28297#M5739</guid>
      <dc:creator>Pedro_Boavida</dc:creator>
      <dc:date>2018-09-20T14:03:24Z</dc:date>
    </item>
    <item>
      <title>Re: VSX (preemption on VS)</title>
      <link>https://community.checkpoint.com/t5/General-Topics/VSX-preemption-on-VS/m-p/82080#M16590</link>
      <description>&lt;P&gt;We would like the same feature. Do you have any update from Checkpoint if this will be implemented (or already is) in future relases?&lt;/P&gt;</description>
      <pubDate>Thu, 16 Apr 2020 09:02:48 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/VSX-preemption-on-VS/m-p/82080#M16590</guid>
      <dc:creator>Mattias_Jansson</dc:creator>
      <dc:date>2020-04-16T09:02:48Z</dc:date>
    </item>
    <item>
      <title>Re: VSX (preemption on VS)</title>
      <link>https://community.checkpoint.com/t5/General-Topics/VSX-preemption-on-VS/m-p/82100#M16592</link>
      <description>&lt;P&gt;Basically, what you are saying is, you do not want VS to fail over, even it is affected by connectivity issues? Or, do I miss something here?&lt;/P&gt;</description>
      <pubDate>Thu, 16 Apr 2020 10:39:04 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/VSX-preemption-on-VS/m-p/82100#M16592</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2020-04-16T10:39:04Z</dc:date>
    </item>
    <item>
      <title>Re: VSX (preemption on VS)</title>
      <link>https://community.checkpoint.com/t5/General-Topics/VSX-preemption-on-VS/m-p/82102#M16593</link>
      <description>&lt;P&gt;No i want to have the same feature as I can use on a "normal" security gateway cluster&lt;BR /&gt;In SmartConsole I have the option to:&lt;BR /&gt;Upon cluster member recovery:&lt;BR /&gt;- Maintain current active Cluster Member&lt;BR /&gt;- Switch to higher priority Cluster Member&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our problem is that when we suffer from connections (mostly nfs, pgqsl and sometimes ldaps) that doesnt survive the failover in case of a virtual server crash (coredump)&lt;BR /&gt;&lt;BR /&gt;It looks like the connections make the first failover to the standby node. But when it fails back again after the vs has restarted we loose the connections and we suffer from it alot.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ok?&lt;/P&gt;</description>
      <pubDate>Thu, 16 Apr 2020 10:50:37 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/VSX-preemption-on-VS/m-p/82102#M16593</guid>
      <dc:creator>Mattias_Jansson</dc:creator>
      <dc:date>2020-04-16T10:50:37Z</dc:date>
    </item>
    <item>
      <title>Re: VSX (preemption on VS)</title>
      <link>https://community.checkpoint.com/t5/General-Topics/VSX-preemption-on-VS/m-p/182337#M30391</link>
      <description>&lt;P&gt;Have you found the solution? we have the same problem&lt;/P&gt;</description>
      <pubDate>Sat, 27 May 2023 17:50:58 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/VSX-preemption-on-VS/m-p/182337#M30391</guid>
      <dc:creator>ClaudiuBadea</dc:creator>
      <dc:date>2023-05-27T17:50:58Z</dc:date>
    </item>
    <item>
      <title>Re: VSX (preemption on VS)</title>
      <link>https://community.checkpoint.com/t5/General-Topics/VSX-preemption-on-VS/m-p/182367#M30405</link>
      <description>&lt;P&gt;I think that the requested feature "Toggle VSLS mode between Active Up and Primary Up" was introduced in R81. Our issues (when I really needed it) was in R80.30. We are on R81.10 now and it is very stable. I have not tried this feature.&lt;/P&gt;</description>
      <pubDate>Mon, 29 May 2023 06:04:19 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/VSX-preemption-on-VS/m-p/182367#M30405</guid>
      <dc:creator>Mattias_Jansson</dc:creator>
      <dc:date>2023-05-29T06:04:19Z</dc:date>
    </item>
  </channel>
</rss>

