<?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: Reason for Firewall Failover in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Reason-for-Firewall-Failover/m-p/196437#M36660</link>
    <description>&lt;P&gt;Policy installation per:&amp;nbsp;&lt;A href="https://support.checkpoint.com/results/sk/sk125152" target="_blank"&gt;https://support.checkpoint.com/results/sk/sk125152&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 27 Oct 2023 17:01:50 GMT</pubDate>
    <dc:creator>PhoneBoy</dc:creator>
    <dc:date>2023-10-27T17:01:50Z</dc:date>
    <item>
      <title>Reason for Firewall Failover</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Reason-for-Firewall-Failover/m-p/157345#M27299</link>
      <description>&lt;P&gt;Can someone please explain what the&amp;nbsp;&amp;nbsp;FWD PNOTE means for failover and why it was triggered&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Details below&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;[Expert@pccfw1:0]# cphaprob state&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cluster Mode:&amp;nbsp; &amp;nbsp;High Availability (Active Up) with IGMP Membership&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ID&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Unique Address&amp;nbsp; Assigned Load&amp;nbsp; &amp;nbsp;State&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Name&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1 (local)&amp;nbsp; 169.254.22.1&amp;nbsp; &amp;nbsp; 0%&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; STANDBY&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; pccfw1&lt;/P&gt;&lt;P&gt;2&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 169.254.22.2&amp;nbsp; &amp;nbsp; 100%&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; ACTIVE&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;pccfw2&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Active PNOTEs: None&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Last member state change event:&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;Event Code:&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;CLUS-114802&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;State change:&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;DOWN -&amp;gt; STANDBY&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;Reason for state change:&amp;nbsp; &amp;nbsp; There is already an ACTIVE member in the cluster&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; (member 2)&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;Event time:&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Tue Sep 13 10:35:56 2022&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Last cluster failover event:&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;Transition to new ACTIVE:&amp;nbsp; &amp;nbsp;Member 1 -&amp;gt; Member 2&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;Reason:&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;FWD PNOTE&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;Event time:&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Tue Sep 13 10:35:26 2022&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cluster failover count:&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;Failover counter:&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;45&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;Time of counter reset:&amp;nbsp; &amp;nbsp; &amp;nbsp; Wed Aug 18 14:04:42 2021 (reboot)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;[Expert@pccfw1:0]# cphaprob show_failover&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Last cluster failover event:&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;Transition to new ACTIVE:&amp;nbsp; &amp;nbsp;Member 1 -&amp;gt; Member 2&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;Reason:&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;FWD PNOTE&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;Event time:&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Tue Sep 13 10:35:26 2022&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cluster failover count:&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;Failover counter:&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;45&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;Time of counter reset:&amp;nbsp; &amp;nbsp; &amp;nbsp; Wed Aug 18 14:04:42 2021 (reboot)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cluster failover history (last 20 failovers since reboot/reset on Wed Aug 18 14:04:42 2021):&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;No. Time:&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Transition:&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;CPU:&amp;nbsp; Reason:&lt;/P&gt;&lt;P&gt;&amp;nbsp;- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -&lt;/P&gt;&lt;P&gt;&amp;nbsp;1&amp;nbsp; &amp;nbsp;Tue Sep 13 10:35:26 2022&amp;nbsp; Member 1 -&amp;gt; Member 2&amp;nbsp; 22&amp;nbsp; &amp;nbsp; FWD PNOTE&lt;/P&gt;&lt;P&gt;&amp;nbsp;2&amp;nbsp; &amp;nbsp;Fri Sep&amp;nbsp; 2 15:08:50 2022&amp;nbsp; Member 2 -&amp;gt; Member 1&amp;nbsp; 13&amp;nbsp; &amp;nbsp; ADMIN_DOWN PNOTE&lt;/P&gt;&lt;P&gt;&amp;nbsp;3&amp;nbsp; &amp;nbsp;Tue Aug 30 19:54:20 2022&amp;nbsp; Member 1 -&amp;gt; Member 2&amp;nbsp; 05&amp;nbsp; &amp;nbsp; FWD PNOTE&lt;/P&gt;&lt;P&gt;&amp;nbsp;4&amp;nbsp; &amp;nbsp;Sat Jun 18 11:10:51 2022&amp;nbsp; Member 2 -&amp;gt; Member 1&amp;nbsp; 05&amp;nbsp; &amp;nbsp; ADMIN_DOWN PNOTE&lt;/P&gt;&lt;P&gt;&amp;nbsp;5&amp;nbsp; &amp;nbsp;Fri Jun 17 22:12:24 2022&amp;nbsp; Member 1 -&amp;gt; Member 2&amp;nbsp; 04&amp;nbsp; &amp;nbsp; Interface eth3.29 is down (disconnected / link down)&lt;/P&gt;&lt;P&gt;&amp;nbsp;6&amp;nbsp; &amp;nbsp;Wed May 25 09:17:41 2022&amp;nbsp; Member 2 -&amp;gt; Member 1&amp;nbsp; 30&amp;nbsp; &amp;nbsp; ADMIN_DOWN PNOTE&lt;/P&gt;&lt;P&gt;&amp;nbsp;7&amp;nbsp; &amp;nbsp;Wed May 25 09:05:01 2022&amp;nbsp; Member 1 -&amp;gt; Member 2&amp;nbsp; 18&amp;nbsp; &amp;nbsp; Interface eth1-03 is down (Cluster Control Protocol packets are not received)&lt;/P&gt;&lt;P&gt;&amp;nbsp;8&amp;nbsp; &amp;nbsp;Tue May 24 23:49:22 2022&amp;nbsp; Member 2 -&amp;gt; Member 1&amp;nbsp; 04&amp;nbsp; &amp;nbsp; ADMIN_DOWN PNOTE&lt;/P&gt;&lt;P&gt;&amp;nbsp;9&amp;nbsp; &amp;nbsp;Tue May 24 23:40:38 2022&amp;nbsp; Member 2 -&amp;gt; Member 1&amp;nbsp; 04&amp;nbsp; &amp;nbsp; Member state has been changed after returning from ACTIVE/ACTIVE scenario (remote cluster member 1 has higher priority)&lt;/P&gt;&lt;P&gt;&amp;nbsp;10&amp;nbsp; Tue May 24 23:30:05 2022&amp;nbsp; Member 2 -&amp;gt; Member 1&amp;nbsp; 03&amp;nbsp; &amp;nbsp; Member state has been changed after returning from ACTIVE/ACTIVE scenario (remote cluster member 1 has higher priority)&lt;/P&gt;&lt;P&gt;&amp;nbsp;11&amp;nbsp; Tue May 24 23:30:04 2022&amp;nbsp; Member 1 -&amp;gt; Member 2&amp;nbsp; 26&amp;nbsp; &amp;nbsp; Interface is down (disconnected / link down)&lt;/P&gt;&lt;P&gt;&amp;nbsp;12&amp;nbsp; Tue May 24 23:30:00 2022&amp;nbsp; Member 2 -&amp;gt; Member 1&amp;nbsp; 24&amp;nbsp; &amp;nbsp; Interface eth5 is down (disconnected / link down)&lt;/P&gt;&lt;P&gt;&amp;nbsp;13&amp;nbsp; Tue May 24 23:29:47 2022&amp;nbsp; Member 1 -&amp;gt; Member 2&amp;nbsp; 04&amp;nbsp; &amp;nbsp; Interface is down (disconnected / link down)&lt;/P&gt;&lt;P&gt;&amp;nbsp;14&amp;nbsp; Mon May&amp;nbsp; 9 16:34:47 2022&amp;nbsp; Member 1 -&amp;gt; Member 2&amp;nbsp; 10&amp;nbsp; &amp;nbsp; FWD PNOTE&lt;/P&gt;&lt;P&gt;&amp;nbsp;15&amp;nbsp; Sun Mar 20 19:13:59 2022&amp;nbsp; Member 2 -&amp;gt; Member 1&amp;nbsp; 02&amp;nbsp; &amp;nbsp; Interface is down (disconnected / link down)&lt;/P&gt;&lt;P&gt;&amp;nbsp;16&amp;nbsp; Sun Mar 20 18:22:48 2022&amp;nbsp; Member 1 -&amp;gt; Member 2&amp;nbsp; 03&amp;nbsp; &amp;nbsp; Interface eth1-02.814 is down (disconnected / link down)&lt;/P&gt;&lt;P&gt;&amp;nbsp;17&amp;nbsp; Tue Nov 30 18:00:45 2021&amp;nbsp; Member 2 -&amp;gt; Member 1&amp;nbsp; 03&amp;nbsp; &amp;nbsp; Interface is down (disconnected / link down)&lt;/P&gt;&lt;P&gt;&amp;nbsp;18&amp;nbsp; Tue Nov 30 17:55:39 2021&amp;nbsp; Member 1 -&amp;gt; Member 2&amp;nbsp; 04&amp;nbsp; &amp;nbsp; Interface eth5 is down (disconnected / link down)&lt;/P&gt;&lt;P&gt;&amp;nbsp;19&amp;nbsp; Tue Nov 30 17:11:01 2021&amp;nbsp; Member 2 -&amp;gt; Member 1&amp;nbsp; 33&amp;nbsp; &amp;nbsp; Interface is down (disconnected / link down)&lt;/P&gt;&lt;P&gt;&amp;nbsp;20&amp;nbsp; Tue Nov 30 17:10:47 2021&amp;nbsp; Member 1 -&amp;gt; Member 2&amp;nbsp; 02&amp;nbsp; &amp;nbsp; Interface eth5 is down (disconnected / link down)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;[Expert@pccfw1:0]#&lt;/P&gt;</description>
      <pubDate>Thu, 15 Sep 2022 16:15:16 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Reason-for-Firewall-Failover/m-p/157345#M27299</guid>
      <dc:creator>ESpataro</dc:creator>
      <dc:date>2022-09-15T16:15:16Z</dc:date>
    </item>
    <item>
      <title>Re: Reason for Firewall Failover</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Reason-for-Firewall-Failover/m-p/157346#M27300</link>
      <description>&lt;P&gt;&lt;A href="http://supportcontent.checkpoint.com/solutions?id=sk56202" target="_blank" rel="noopener"&gt;sk56202 - How to troubleshoot failovers in ClusterXL&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A class="cp_link sc_ellipsis" href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk62570&amp;amp;partition=Advanced&amp;amp;product=ClusterXL," target="_blank"&gt;sk62570: How to troubleshoot failovers in ClusterXL - Advanced Guide&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Sep 2022 16:24:08 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Reason-for-Firewall-Failover/m-p/157346#M27300</guid>
      <dc:creator>G_W_Albrecht</dc:creator>
      <dc:date>2022-09-15T16:24:08Z</dc:date>
    </item>
    <item>
      <title>Re: Reason for Firewall Failover</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Reason-for-Firewall-Failover/m-p/157348#M27301</link>
      <description>&lt;P&gt;It shows FWD pnote went down, that was the reason. So, from expert mode, run this command on both:&lt;/P&gt;
&lt;P&gt;grep -i FWD /var/log/messages* and see what you get.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Thu, 15 Sep 2022 16:56:32 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Reason-for-Firewall-Failover/m-p/157348#M27301</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2022-09-15T16:56:32Z</dc:date>
    </item>
    <item>
      <title>Re: Reason for Firewall Failover</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Reason-for-Firewall-Failover/m-p/196420#M36655</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Do you know what the description &lt;STRONG&gt;"Member state has been changed due to restart of the Cluster module"&lt;/STRONG&gt; refers to?&lt;/P&gt;
&lt;P&gt;I have a ClusterXL in Load Sharing mode, and there seems to have been a problem with the Cluster member, as apparently for a moment it stopped being part of the Cluster.&lt;/P&gt;
&lt;P&gt;What is the MODULE of a Cluster? Does it refer to a "daemon/process"?&lt;/P&gt;
&lt;P&gt;I share the output of the command "cphaprob show_failover".&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;[Expert@SG1:0]# cphaprob show_failover&lt;/P&gt;
&lt;P&gt;Last member failover event:&lt;BR /&gt;Member in failure: Member 1&lt;BR /&gt;Reason: Member state has been changed due to restart of the Cluster module&lt;BR /&gt;Event time: Fri Oct 27 06:46:18 2023&lt;/P&gt;
&lt;P&gt;Cluster failover count:&lt;BR /&gt;Failover counter: 1&lt;BR /&gt;Time of counter reset: Sun Jul 9 00:04:28 2023 (reboot)&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Cluster failover history (last 20 failovers since reboot/reset on Fri Sep 24 12:49:47 2021):&lt;/P&gt;
&lt;P&gt;No. Time: Transition: CPU: Reason:&lt;BR /&gt;- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -&lt;BR /&gt;1 Fri Oct 27 06:46:18 2023 Member 1 38 Member state has been changed due to restart of the Cluster module&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&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>Fri, 27 Oct 2023 15:18:17 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Reason-for-Firewall-Failover/m-p/196420#M36655</guid>
      <dc:creator>Matlu</dc:creator>
      <dc:date>2023-10-27T15:18:17Z</dc:date>
    </item>
    <item>
      <title>Re: Reason for Firewall Failover</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Reason-for-Firewall-Failover/m-p/196437#M36660</link>
      <description>&lt;P&gt;Policy installation per:&amp;nbsp;&lt;A href="https://support.checkpoint.com/results/sk/sk125152" target="_blank"&gt;https://support.checkpoint.com/results/sk/sk125152&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 27 Oct 2023 17:01:50 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Reason-for-Firewall-Failover/m-p/196437#M36660</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2023-10-27T17:01:50Z</dc:date>
    </item>
    <item>
      <title>Re: Reason for Firewall Failover</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Reason-for-Firewall-Failover/m-p/196439#M36661</link>
      <description>&lt;P&gt;&lt;A href="https://support.checkpoint.com/results/sk/sk125152" target="_blank"&gt;https://support.checkpoint.com/results/sk/sk125152&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;also run -&amp;gt; grep -i DPWN /var/log/messages* and look for any lines for that date/time&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Fri, 27 Oct 2023 17:55:22 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Reason-for-Firewall-Failover/m-p/196439#M36661</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2023-10-27T17:55:22Z</dc:date>
    </item>
    <item>
      <title>Re: Reason for Firewall Failover</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Reason-for-Firewall-Failover/m-p/196443#M36662</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/80263"&gt;@ESpataro&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;FWD pnote might be triggered only in case it was terminated or crashed, in general the failover will happen only after certain time post fwd termination, so my guess you probably have a core dump, since post crash the creation of core takes a bit time which passing the time for failover trigger.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Ilya&lt;/P&gt;</description>
      <pubDate>Fri, 27 Oct 2023 19:55:00 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Reason-for-Firewall-Failover/m-p/196443#M36662</guid>
      <dc:creator>Ilya_Yusupov</dc:creator>
      <dc:date>2023-10-27T19:55:00Z</dc:date>
    </item>
    <item>
      <title>Re: Reason for Firewall Failover</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Reason-for-Firewall-Failover/m-p/196444#M36663</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;If a Failover occurs, and as a result of this a &lt;STRONG&gt;"Core DUMP"&lt;/STRONG&gt; is "created", in which path is this type of files?&lt;/P&gt;
&lt;P&gt;These files are "understandable" for common users like us,&lt;STRONG&gt; or they must be checked by Check Point TAC&lt;/STRONG&gt;?&lt;/P&gt;
&lt;P&gt;Greetings.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Oct 2023 20:08:20 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Reason-for-Firewall-Failover/m-p/196444#M36663</guid>
      <dc:creator>Matlu</dc:creator>
      <dc:date>2023-10-27T20:08:20Z</dc:date>
    </item>
    <item>
      <title>Re: Reason for Firewall Failover</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Reason-for-Firewall-Failover/m-p/196448#M36665</link>
      <description>&lt;P&gt;Usermode processes should dump core in&amp;nbsp;&lt;SPAN&gt;/var/log/dump/usermode&lt;BR /&gt;If the kernel crashes, it should be in /var/log/crash&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;To analyze a core dump of either kind, you will most likely need unstripped binaries and/or libraries.&lt;BR /&gt;These are not made available outside of R&amp;amp;D and TAC CFG.&amp;nbsp;&lt;BR /&gt;Even if you have access to these things, you're going to have to involve TAC to get the underlying issue resolved with R&amp;amp;D.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Oct 2023 23:26:22 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Reason-for-Firewall-Failover/m-p/196448#M36665</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2023-10-27T23:26:22Z</dc:date>
    </item>
    <item>
      <title>Re: Reason for Firewall Failover</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Reason-for-Firewall-Failover/m-p/196471#M36669</link>
      <description>&lt;P&gt;As others have said, fwd probably crashed.&amp;nbsp; Look in $FWDIR/log/fwd.elg for clues and run &lt;STRONG&gt;cpwd_admin list&lt;/STRONG&gt; to confirm that the fwd process was automatically restarted and when it occurred.&lt;/P&gt;</description>
      <pubDate>Sat, 28 Oct 2023 14:44:16 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Reason-for-Firewall-Failover/m-p/196471#M36669</guid>
      <dc:creator>Timothy_Hall</dc:creator>
      <dc:date>2023-10-28T14:44:16Z</dc:date>
    </item>
  </channel>
</rss>

