<?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 VSLS no Standby in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-VSLS-no-Standby/m-p/258777#M50751</link>
    <description>&lt;P&gt;Maybe a dumb suggestion: But have you tried to install policy with non-accelerated install?&lt;/P&gt;</description>
    <pubDate>Thu, 02 Oct 2025 10:28:13 GMT</pubDate>
    <dc:creator>Oliver_Fink</dc:creator>
    <dc:date>2025-10-02T10:28:13Z</dc:date>
    <item>
      <title>VSX VSLS no Standby</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-VSLS-no-Standby/m-p/258770#M50749</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I have a strange issue that will most likely require a TAC case but I though that I would ask here as well if anyone has seen the issue before and might have a quick solution.&lt;/P&gt;&lt;P&gt;After upgrading a 9800 VSX VSLS cluster with 4 members to R81.20 JHF take 115 (recommended by TAC as we had several issues running the previous takes) one VS has some strange status issues in cphaprob stat.&lt;/P&gt;&lt;P&gt;This is the output from VS0:&lt;/P&gt;&lt;P&gt;9 | 10 | ACTIVE | BACKUP | BACKUP | BACKUP&lt;/P&gt;&lt;P&gt;This is the output from VS9 itself:&lt;/P&gt;&lt;P&gt;ID Unique Address Assigned Load State Name&lt;/P&gt;&lt;P&gt;1 x.x.x.x 100% ACTIVE xxx&lt;BR /&gt;2 y.y.y.y 0% BACKUP yyy&lt;BR /&gt;3 (local) z.z.z.z 0% BACKUP zzz&lt;BR /&gt;4 a.a.a.a 0% BACKUP aaa&lt;/P&gt;&lt;P&gt;I cannot understand why there is no Standby and only Backups.&lt;/P&gt;&lt;P&gt;Checking the connection table on all 4 members I can see sync is working correctly between member 1 and member 3, which is the member that should be standby according to the VSLS priority list. It also works to do a manual failover with intact state table and no network disruptions. So it is only cosmetic.&lt;/P&gt;&lt;P&gt;I have not tried to run reset_gw and reconfigure, only pushing the VSLS configuration again which did not solve it. Normal fw policy did nothing either.&lt;/P&gt;&lt;P&gt;So, any ideas as I wait for TAC?&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Lau&lt;/P&gt;</description>
      <pubDate>Thu, 02 Oct 2025 09:28:18 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-VSLS-no-Standby/m-p/258770#M50749</guid>
      <dc:creator>Lau</dc:creator>
      <dc:date>2025-10-02T09:28:18Z</dc:date>
    </item>
    <item>
      <title>Re: VSX VSLS no Standby</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-VSLS-no-Standby/m-p/258777#M50751</link>
      <description>&lt;P&gt;Maybe a dumb suggestion: But have you tried to install policy with non-accelerated install?&lt;/P&gt;</description>
      <pubDate>Thu, 02 Oct 2025 10:28:13 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-VSLS-no-Standby/m-p/258777#M50751</guid>
      <dc:creator>Oliver_Fink</dc:creator>
      <dc:date>2025-10-02T10:28:13Z</dc:date>
    </item>
    <item>
      <title>Re: VSX VSLS no Standby</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-VSLS-no-Standby/m-p/258778#M50752</link>
      <description>&lt;P&gt;I hadn't, but tried it now with no success. Thanks for the idea though.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Oct 2025 10:43:48 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-VSLS-no-Standby/m-p/258778#M50752</guid>
      <dc:creator>Lau</dc:creator>
      <dc:date>2025-10-02T10:43:48Z</dc:date>
    </item>
    <item>
      <title>Re: VSX VSLS no Standby</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-VSLS-no-Standby/m-p/258788#M50755</link>
      <description>&lt;P&gt;HA status was ok before the update?&lt;/P&gt;
&lt;P&gt;Anything special about the VS, any dynamic routing or bridge mode?&lt;/P&gt;</description>
      <pubDate>Thu, 02 Oct 2025 12:09:51 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-VSLS-no-Standby/m-p/258788#M50755</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2025-10-02T12:09:51Z</dc:date>
    </item>
    <item>
      <title>Re: VSX VSLS no Standby</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-VSLS-no-Standby/m-p/258858#M50772</link>
      <description>&lt;P&gt;Have you tried restarting that VS? Since the 3.1 kernel you can cpstop;cpstart per VS if you vsenv to it.&lt;/P&gt;</description>
      <pubDate>Fri, 03 Oct 2025 01:11:43 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-VSLS-no-Standby/m-p/258858#M50772</guid>
      <dc:creator>emmap</dc:creator>
      <dc:date>2025-10-03T01:11:43Z</dc:date>
    </item>
  </channel>
</rss>

