<?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: Cluster Node Failover/Switching Issue in Check Point Environment in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Cluster-Node-Failover-Switching-Issue-in-Check-Point-Environment/m-p/240261#M46611</link>
    <description>&lt;P&gt;Thank you so much&lt;/P&gt;</description>
    <pubDate>Mon, 03 Feb 2025 10:59:01 GMT</pubDate>
    <dc:creator>Nstreltsov</dc:creator>
    <dc:date>2025-02-03T10:59:01Z</dc:date>
    <item>
      <title>Cluster Node Failover/Switching Issue in Check Point Environment</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Cluster-Node-Failover-Switching-Issue-in-Check-Point-Environment/m-p/240240#M46603</link>
      <description>&lt;P&gt;Hello everyone!&lt;/P&gt;&lt;P&gt;We are facing an issue where changes to routing settings or interface configurations cause the cluster node to switch from active to passive (High Availability cluster). This results in user sessions being dropped. It has been clearly observed that RDP sessions are affected. In other words, seamless failover is not occurring, which is critical for us. Is there any way to address this issue so that node switching does not occur when modifying routing settings or interface configurations?&lt;/P&gt;&lt;P&gt;As a last resort, a list of sensitive settings that would definitively trigger a switch from active to passive would be helpful. For example, when changing DNS settings, no switching occurs. However, I have not been able to find an explicit list of settings that would cause such a switch.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Feb 2025 07:25:07 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Cluster-Node-Failover-Switching-Issue-in-Check-Point-Environment/m-p/240240#M46603</guid>
      <dc:creator>Nstreltsov</dc:creator>
      <dc:date>2025-02-03T07:25:07Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Node Failover/Switching Issue in Check Point Environment</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Cluster-Node-Failover-Switching-Issue-in-Check-Point-Environment/m-p/240259#M46609</link>
      <description>&lt;P&gt;ClusterXL monitors all interfaces unless you configure a specific interface as unmonitored.&lt;BR /&gt;Any changes to interface configuration needs to be done in a maintenance window.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Feb 2025 10:26:13 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Cluster-Node-Failover-Switching-Issue-in-Check-Point-Environment/m-p/240259#M46609</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2025-02-03T10:26:13Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Node Failover/Switching Issue in Check Point Environment</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Cluster-Node-Failover-Switching-Issue-in-Check-Point-Environment/m-p/240261#M46611</link>
      <description>&lt;P&gt;Thank you so much&lt;/P&gt;</description>
      <pubDate>Mon, 03 Feb 2025 10:59:01 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Cluster-Node-Failover-Switching-Issue-in-Check-Point-Environment/m-p/240261#M46611</guid>
      <dc:creator>Nstreltsov</dc:creator>
      <dc:date>2025-02-03T10:59:01Z</dc:date>
    </item>
  </channel>
</rss>

