<?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: R80.40 Cluster on Hyper-V in Cloud Firewall</title>
    <link>https://community.checkpoint.com/t5/Cloud-Firewall/R80-40-Cluster-on-Hyper-V/m-p/155432#M953</link>
    <description>&lt;P&gt;Did you configure it like below or something else?&lt;/P&gt;
&lt;P&gt;fwha_cluster_hide_active_only=0&lt;/P&gt;</description>
    <pubDate>Mon, 22 Aug 2022 13:50:57 GMT</pubDate>
    <dc:creator>Chris_Atkinson</dc:creator>
    <dc:date>2022-08-22T13:50:57Z</dc:date>
    <item>
      <title>R80.40 Cluster on Hyper-V</title>
      <link>https://community.checkpoint.com/t5/Cloud-Firewall/R80-40-Cluster-on-Hyper-V/m-p/155314#M950</link>
      <description>&lt;P&gt;Has anyone see issues with the standby firewall communicating through active as it should when installedin Hyper-V.&amp;nbsp; I have seen this in at least 3 different clusters so far.&amp;nbsp; Traffic is seen leaving standby on sync interface, but never appears to never arrive at the active firewall.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Corey&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 19 Aug 2022 20:16:45 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Cloud-Firewall/R80-40-Cluster-on-Hyper-V/m-p/155314#M950</guid>
      <dc:creator>Corey_Clark</dc:creator>
      <dc:date>2022-08-19T20:16:45Z</dc:date>
    </item>
    <item>
      <title>Re: R80.40 Cluster on Hyper-V</title>
      <link>https://community.checkpoint.com/t5/Cloud-Firewall/R80-40-Cluster-on-Hyper-V/m-p/155316#M951</link>
      <description>&lt;P&gt;Hi Corey,&lt;/P&gt;
&lt;P&gt;Not aware of a Hyper-V specific behaviour myself but that doesn't mean there isn't something unique there.&lt;/P&gt;
&lt;P&gt;Meanwhile take a look at&amp;nbsp;&lt;SPAN&gt;sk169154 and see if it assists with your situation (may also require a CCP tweak in consultation with TAC).&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Refer also: sk167453&lt;/P&gt;</description>
      <pubDate>Sat, 20 Aug 2022 07:31:40 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Cloud-Firewall/R80-40-Cluster-on-Hyper-V/m-p/155316#M951</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2022-08-20T07:31:40Z</dc:date>
    </item>
    <item>
      <title>Re: R80.40 Cluster on Hyper-V</title>
      <link>https://community.checkpoint.com/t5/Cloud-Firewall/R80-40-Cluster-on-Hyper-V/m-p/155431#M952</link>
      <description>&lt;P&gt;I think this is due to hyper-V rejecting forged transmits. For a work around running&amp;nbsp;fw ctl set int fwha_cluster_hide_active_only 0 per sk169154 does send the traffic out of the ext interface instead of the sync and with a no NAT rule for the cluster members traffic from the secondary now works. How can this be set to survive a reboot, fwkern.conf file with&amp;nbsp;fw ctl set int fwha_cluster_hide_active_only 0 does not apply this parameter upon a reboot.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Aug 2022 13:32:22 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Cloud-Firewall/R80-40-Cluster-on-Hyper-V/m-p/155431#M952</guid>
      <dc:creator>Gary_Scott</dc:creator>
      <dc:date>2022-08-22T13:32:22Z</dc:date>
    </item>
    <item>
      <title>Re: R80.40 Cluster on Hyper-V</title>
      <link>https://community.checkpoint.com/t5/Cloud-Firewall/R80-40-Cluster-on-Hyper-V/m-p/155432#M953</link>
      <description>&lt;P&gt;Did you configure it like below or something else?&lt;/P&gt;
&lt;P&gt;fwha_cluster_hide_active_only=0&lt;/P&gt;</description>
      <pubDate>Mon, 22 Aug 2022 13:50:57 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Cloud-Firewall/R80-40-Cluster-on-Hyper-V/m-p/155432#M953</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2022-08-22T13:50:57Z</dc:date>
    </item>
    <item>
      <title>Re: R80.40 Cluster on Hyper-V</title>
      <link>https://community.checkpoint.com/t5/Cloud-Firewall/R80-40-Cluster-on-Hyper-V/m-p/155433#M954</link>
      <description>&lt;P&gt;That would be my next step, just wanted to see if anyone else had experienced this behavior on hyper-v installations.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Aug 2022 13:56:27 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Cloud-Firewall/R80-40-Cluster-on-Hyper-V/m-p/155433#M954</guid>
      <dc:creator>Corey_Clark</dc:creator>
      <dc:date>2022-08-22T13:56:27Z</dc:date>
    </item>
    <item>
      <title>Re: R80.40 Cluster on Hyper-V</title>
      <link>https://community.checkpoint.com/t5/Cloud-Firewall/R80-40-Cluster-on-Hyper-V/m-p/155434#M955</link>
      <description>&lt;P&gt;Something else,&amp;nbsp; "fw ctl set -f int fwha_cluster_hide_active_only 0" used sk16202 as a reference. Just tried "&lt;SPAN&gt;fwha_cluster_hide_active_only=0" and that worked. Thank you!&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Aug 2022 14:01:37 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Cloud-Firewall/R80-40-Cluster-on-Hyper-V/m-p/155434#M955</guid>
      <dc:creator>Gary_Scott</dc:creator>
      <dc:date>2022-08-22T14:01:37Z</dc:date>
    </item>
    <item>
      <title>Re: R80.40 Cluster on Hyper-V</title>
      <link>https://community.checkpoint.com/t5/Cloud-Firewall/R80-40-Cluster-on-Hyper-V/m-p/155435#M956</link>
      <description>&lt;P&gt;Understood, seems Gary is testing for you. &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Aug 2022 14:10:35 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Cloud-Firewall/R80-40-Cluster-on-Hyper-V/m-p/155435#M956</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2022-08-22T14:10:35Z</dc:date>
    </item>
  </channel>
</rss>

