<?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: change priority (ID) on a VSX VSLS Gateway in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/change-priority-ID-on-a-VSX-VSLS-Gateway/m-p/202434#M38099</link>
    <description>&lt;P&gt;An alternative solution would be to rename the physical appliances and swap 001 and 002 in their names.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;VPX internal naming is automatic, and there is no any graceful way to rename the internal elements without re-configuring them from scratch, as far as I know.&lt;/P&gt;</description>
    <pubDate>Mon, 08 Jan 2024 08:41:12 GMT</pubDate>
    <dc:creator>_Val_</dc:creator>
    <dc:date>2024-01-08T08:41:12Z</dc:date>
    <item>
      <title>change priority (ID) on a VSX VSLS Gateway</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/change-priority-ID-on-a-VSX-VSLS-Gateway/m-p/202433#M38098</link>
      <description>&lt;P&gt;Hi Community&lt;/P&gt;&lt;P&gt;I made a mistake during the creation of the VSX cluster and added the "second" cluster member first. The devices have names like ... 001 and ...002.&amp;nbsp; As a result the 001 has ID 2, the 002 has ID 1.&lt;BR /&gt;&lt;SPAN&gt;This is only a cosmetic detail but my customer likes to have the first device the primary....&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I am able to define all VS higher than 0 on the 001 member (even if this one has ID2) with the vsx_util. But I am not able to change the ID / the priority of the cluster member (this is possible in a traditional cluster by changing the priority).&lt;BR /&gt;&lt;SPAN&gt;Is there any way to change the priority (the ID) of a cluster member without rebuilding the whole cluster again from scratch?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The mode is "VSLS (Primary up)"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-left" image-alt="image.png" style="width: 400px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/24001i6B38C5E2696E7517/image-size/medium?v=v2&amp;amp;px=400" role="button" title="image.png" alt="image.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-left" image-alt="image.png" style="width: 200px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/24000iFA69332B9596902F/image-size/small?v=v2&amp;amp;px=200" role="button" title="image.png" alt="image.png" /&gt;&lt;/span&gt;&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;any ideas?&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jan 2024 08:37:00 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/change-priority-ID-on-a-VSX-VSLS-Gateway/m-p/202433#M38098</guid>
      <dc:creator>Daniel_Fischler</dc:creator>
      <dc:date>2024-01-08T08:37:00Z</dc:date>
    </item>
    <item>
      <title>Re: change priority (ID) on a VSX VSLS Gateway</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/change-priority-ID-on-a-VSX-VSLS-Gateway/m-p/202434#M38099</link>
      <description>&lt;P&gt;An alternative solution would be to rename the physical appliances and swap 001 and 002 in their names.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;VPX internal naming is automatic, and there is no any graceful way to rename the internal elements without re-configuring them from scratch, as far as I know.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jan 2024 08:41:12 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/change-priority-ID-on-a-VSX-VSLS-Gateway/m-p/202434#M38099</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2024-01-08T08:41:12Z</dc:date>
    </item>
  </channel>
</rss>

