<?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: Failover root-cause detection in ClusterXL HA in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Failover-root-cause-detection-in-ClusterXL-HA/m-p/194595#M36233</link>
    <description>&lt;P&gt;I do use it lol, but you should check if customer does hehe.&lt;/P&gt;
&lt;P&gt;Anyway, you can verify via web UI, ospf and bgp tabs or from clish, just run show ospf and show bgp and when you hit tab, gives all the options.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
    <pubDate>Tue, 10 Oct 2023 00:54:20 GMT</pubDate>
    <dc:creator>the_rock</dc:creator>
    <dc:date>2023-10-10T00:54:20Z</dc:date>
    <item>
      <title>Failover root-cause detection in ClusterXL HA</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Failover-root-cause-detection-in-ClusterXL-HA/m-p/194591#M36230</link>
      <description>&lt;P&gt;Hello everyone.&lt;/P&gt;
&lt;P&gt;Today our ClusterXL HA, had a FAILOVER from "one moment to another", without any intervention from the administrators.&lt;/P&gt;
&lt;P&gt;We would like to detect if the root-cause of this FAILOVER is the responsibility of the GW (I would say no).&lt;/P&gt;
&lt;P&gt;I have reviewed the following, and I would like to know the opinion of people more experienced with these diagnoses.&lt;/P&gt;
&lt;P&gt;I get the impression that at the time of the FAILOVER, there was an error with the VLAN that was being monitored, but possibly the root-cause is in a different equipment than the GW Check Point.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="FO1.png" style="width: 999px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/22720iCA0418C0D833A807/image-size/large?v=v2&amp;amp;px=999" role="button" title="FO1.png" alt="FO1.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="FO2.png" style="width: 999px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/22721iCC68097A18C75D22/image-size/large?v=v2&amp;amp;px=999" role="button" title="FO2.png" alt="FO2.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Cheers . &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 10 Oct 2023 00:07:18 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Failover-root-cause-detection-in-ClusterXL-HA/m-p/194591#M36230</guid>
      <dc:creator>Matlu</dc:creator>
      <dc:date>2023-10-10T00:07:18Z</dc:date>
    </item>
    <item>
      <title>Re: Failover root-cause detection in ClusterXL HA</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Failover-root-cause-detection-in-ClusterXL-HA/m-p/194592#M36231</link>
      <description>&lt;P&gt;Bro, as I stated in my email, best is to review routed.log and messages file, but based on what you show, it apears issue was with interface bond12.62&lt;/P&gt;
&lt;P&gt;Is customer using ospf/bgp? MAKE SURE below value is set to 0 and not 1&lt;/P&gt;
&lt;P&gt;fw ctl get int fwha_monitor_all_vlan&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Tue, 10 Oct 2023 00:43:19 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Failover-root-cause-detection-in-ClusterXL-HA/m-p/194592#M36231</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2023-10-10T00:43:19Z</dc:date>
    </item>
    <item>
      <title>Re: Failover root-cause detection in ClusterXL HA</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Failover-root-cause-detection-in-ClusterXL-HA/m-p/194594#M36232</link>
      <description>&lt;P&gt;Hey,&lt;/P&gt;
&lt;P&gt;I'm not sure yet, if you use "dynamic routing".&lt;/P&gt;
&lt;P&gt;The command you share with me, shows me the following.&lt;/P&gt;
&lt;P&gt;[Expert@SG1:0]# fw ctl get int fwha_monitor_all_vlan&lt;BR /&gt;fwha_monitor_all_vlan = 0&lt;BR /&gt;[Expert@SG1:0]#&lt;/P&gt;
&lt;P&gt;Cheers. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 10 Oct 2023 00:48:25 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Failover-root-cause-detection-in-ClusterXL-HA/m-p/194594#M36232</guid>
      <dc:creator>Matlu</dc:creator>
      <dc:date>2023-10-10T00:48:25Z</dc:date>
    </item>
    <item>
      <title>Re: Failover root-cause detection in ClusterXL HA</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Failover-root-cause-detection-in-ClusterXL-HA/m-p/194595#M36233</link>
      <description>&lt;P&gt;I do use it lol, but you should check if customer does hehe.&lt;/P&gt;
&lt;P&gt;Anyway, you can verify via web UI, ospf and bgp tabs or from clish, just run show ospf and show bgp and when you hit tab, gives all the options.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Tue, 10 Oct 2023 00:54:20 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Failover-root-cause-detection-in-ClusterXL-HA/m-p/194595#M36233</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2023-10-10T00:54:20Z</dc:date>
    </item>
    <item>
      <title>Re: Failover root-cause detection in ClusterXL HA</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Failover-root-cause-detection-in-ClusterXL-HA/m-p/194598#M36234</link>
      <description>&lt;P&gt;I checked, and no, it does not use either of the 2 protocols.&lt;BR /&gt;&lt;BR /&gt;LOL&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":rolling_on_the_floor_laughing:"&gt;🤣&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="FO3.png" style="width: 488px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/22722i6D3867A283B93720/image-size/large?v=v2&amp;amp;px=999" role="button" title="FO3.png" alt="FO3.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I suspect it may also be a problem with "other equipment" on the network, perhaps the switches.&lt;/P&gt;
&lt;P&gt;What do you think?&lt;/P&gt;</description>
      <pubDate>Tue, 10 Oct 2023 00:59:27 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Failover-root-cause-detection-in-ClusterXL-HA/m-p/194598#M36234</guid>
      <dc:creator>Matlu</dc:creator>
      <dc:date>2023-10-10T00:59:27Z</dc:date>
    </item>
    <item>
      <title>Re: Failover root-cause detection in ClusterXL HA</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Failover-root-cause-detection-in-ClusterXL-HA/m-p/194599#M36235</link>
      <description>&lt;P&gt;Its possible, but you would need them to check the switches.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Tue, 10 Oct 2023 01:05:24 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Failover-root-cause-detection-in-ClusterXL-HA/m-p/194599#M36235</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2023-10-10T01:05:24Z</dc:date>
    </item>
  </channel>
</rss>

