<?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: Policy issue after HA event in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Policy-issue-after-HA-event/m-p/211563#M40114</link>
    <description>&lt;P&gt;I'm not aware of that issue specifically, but that is a very old JHF take. I would suggest updating it to the current recommended release and testing again, and if the issue still occurs then we'll need TAC to investigate.&lt;/P&gt;</description>
    <pubDate>Wed, 17 Apr 2024 09:23:06 GMT</pubDate>
    <dc:creator>emmap</dc:creator>
    <dc:date>2024-04-17T09:23:06Z</dc:date>
    <item>
      <title>Policy issue after HA event</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Policy-issue-after-HA-event/m-p/211531#M40101</link>
      <description>&lt;P&gt;Hi guys, strange issue that we have now seen twice on two different clusters. After an HA failover, the standby firewall picked up and was allowing traffic, but then when it failed back (we have revert to higher priority set) the gateway then dropped the traffic against the clean-up rule. It wasn't first packet isn't syn or anything like that, it was new connections (we had testers trying) and the drop reason was hitting the drop all rule in last position the policy. The fix was to install policy and it started working immediately again.&lt;/P&gt;
&lt;P&gt;The rules that were impacted were simple IP to IP rules. Anyone seen this before?&lt;/P&gt;
&lt;P&gt;Gateways are R81.10 T45&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;&amp;nbsp;&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;</description>
      <pubDate>Wed, 17 Apr 2024 01:55:53 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Policy-issue-after-HA-event/m-p/211531#M40101</guid>
      <dc:creator>Ryan_Ryan</dc:creator>
      <dc:date>2024-04-17T01:55:53Z</dc:date>
    </item>
    <item>
      <title>Re: Policy issue after HA event</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Policy-issue-after-HA-event/m-p/211563#M40114</link>
      <description>&lt;P&gt;I'm not aware of that issue specifically, but that is a very old JHF take. I would suggest updating it to the current recommended release and testing again, and if the issue still occurs then we'll need TAC to investigate.&lt;/P&gt;</description>
      <pubDate>Wed, 17 Apr 2024 09:23:06 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Policy-issue-after-HA-event/m-p/211563#M40114</guid>
      <dc:creator>emmap</dc:creator>
      <dc:date>2024-04-17T09:23:06Z</dc:date>
    </item>
  </channel>
</rss>

