<?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: Setting up ClusterXL in different DCs in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Setting-up-ClusterXL-in-different-DCs/m-p/264509#M51993</link>
    <description>&lt;P&gt;tbh i dunno. As both DC are at same provider, this is a service provided by them and we don't have to care, which technology they use. For us, it's just "stretched VLAN" &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 05 Dec 2025 13:39:26 GMT</pubDate>
    <dc:creator>Vincent_Bacher</dc:creator>
    <dc:date>2025-12-05T13:39:26Z</dc:date>
    <item>
      <title>Setting up ClusterXL in different DCs</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Setting-up-ClusterXL-in-different-DCs/m-p/264465#M51972</link>
      <description>&lt;P&gt;Hey everyone,&lt;/P&gt;
&lt;P&gt;Is it possible to set up a ClusterXL when both members are going to be located in different geographically separated data centers?&lt;/P&gt;
&lt;P&gt;My question is how this works in terms of IP addressing, knowing that both sites will have different ISPs and therefore different public IP address blocks.&lt;/P&gt;
&lt;P&gt;In such an environment, is it possible to set up ClusterXL?&lt;/P&gt;
&lt;P&gt;Because I assume that a VIP is needed for the external part, but in this scenario I have doubts about how the deployment would be done and whether it would actually be possible.&lt;/P&gt;
&lt;P&gt;Thank you for your comments&lt;/P&gt;</description>
      <pubDate>Fri, 05 Dec 2025 02:34:58 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Setting-up-ClusterXL-in-different-DCs/m-p/264465#M51972</guid>
      <dc:creator>Matlu</dc:creator>
      <dc:date>2025-12-05T02:34:58Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up ClusterXL in different DCs</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Setting-up-ClusterXL-in-different-DCs/m-p/264466#M51973</link>
      <description>&lt;P&gt;For best results, a ClusterXL cluster must share layer 2 spaces on every interface. So for situations like yours it's better to have a separate internet routing layer handle your two ISPs that can then integrate with the gateway cluster via a shared switching layer. This way internet failover is handled separately to firewall failover.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;An alternative is the Active-Active option outlined in the ClusterXL admin guide, where all interfaces are independent layer 3 scenarios and traffic path selection is handled at a routing layer, which functionally means you need dynamic routing happening at every interface. There are limitations here outlined in the admin guide to take careful note of.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Dec 2025 02:44:41 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Setting-up-ClusterXL-in-different-DCs/m-p/264466#M51973</guid>
      <dc:creator>emmap</dc:creator>
      <dc:date>2025-12-05T02:44:41Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up ClusterXL in different DCs</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Setting-up-ClusterXL-in-different-DCs/m-p/264467#M51974</link>
      <description>&lt;P&gt;Sounds like this would apply?&lt;/P&gt;
&lt;P&gt;&lt;A href="https://sc1.checkpoint.com/documents/R82/WebAdminGuides/EN/CP_R82_ClusterXL_AdminGuide/Content/Topics-CXLG/Example-of-cluster-IP-addresses-on-different-subnets.htm" target="_blank"&gt;https://sc1.checkpoint.com/documents/R82/WebAdminGuides/EN/CP_R82_ClusterXL_AdminGuide/Content/Topics-CXLG/Example-of-cluster-IP-addresses-on-different-subnets.htm&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Dec 2025 02:51:21 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Setting-up-ClusterXL-in-different-DCs/m-p/264467#M51974</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-12-05T02:51:21Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up ClusterXL in different DCs</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Setting-up-ClusterXL-in-different-DCs/m-p/264468#M51975</link>
      <description>&lt;P&gt;So far, I only have the comment that both sites will use "dark fiber" for communication.&lt;BR /&gt;My question is about the public (external) interface.&lt;BR /&gt;I understand from your comment that for scenarios like this, it is better to have the deployment mode set to ACTIVE-ACTIVE and use a separate ROUTING layer?&lt;/P&gt;
&lt;P&gt;Is there a practical example that could help me better understand this point?&lt;/P&gt;</description>
      <pubDate>Fri, 05 Dec 2025 03:04:59 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Setting-up-ClusterXL-in-different-DCs/m-p/264468#M51975</guid>
      <dc:creator>Matlu</dc:creator>
      <dc:date>2025-12-05T03:04:59Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up ClusterXL in different DCs</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Setting-up-ClusterXL-in-different-DCs/m-p/264469#M51976</link>
      <description>&lt;P&gt;Active/Active isn't necessarily the better idea here, as it affects how every interface works. If you want it to be a more familiar layer 2 next hop redundancy situation then you're better off with the separated routing layer for the ISPs.&lt;/P&gt;
&lt;P&gt;The way to think of the Active/Active situation is as if it is two entirely separate gateways that you want to manage with dynamic routing.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Dec 2025 03:46:25 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Setting-up-ClusterXL-in-different-DCs/m-p/264469#M51976</guid>
      <dc:creator>emmap</dc:creator>
      <dc:date>2025-12-05T03:46:25Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up ClusterXL in different DCs</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Setting-up-ClusterXL-in-different-DCs/m-p/264493#M51984</link>
      <description>&lt;P&gt;As mentioned earlier, this is generally not a problem at all.&lt;BR /&gt;For example, in my hometown we operate a cluster across two data centers that are about 20 km apart.&lt;/P&gt;&lt;P&gt;The important requirement is (as already stated as well) to use&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;stretched Layer-2 networks (stretched VLANs)&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;so that the same VLAN IDs are available in both data centers.&lt;/P&gt;&lt;P&gt;In the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;sync VLAN&lt;/STRONG&gt;, latency between both cluster nodes must remain&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;below 100 ms&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;to ensure reliable state/session synchronization.&lt;/P&gt;&lt;P&gt;Because a stretched VLAN is used, the internet routers also have an internal interface in the same VLAN.&lt;/P&gt;&lt;P&gt;We additionally run&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;VSX with VSLS&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;to distribute the virtual systems efficiently across both sites.&lt;/P&gt;&lt;P&gt;Everything else comes down to proper routing, both inside the LAN and towards the internet.&lt;/P&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;</description>
      <pubDate>Fri, 05 Dec 2025 11:02:43 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Setting-up-ClusterXL-in-different-DCs/m-p/264493#M51984</guid>
      <dc:creator>Vincent_Bacher</dc:creator>
      <dc:date>2025-12-05T11:02:43Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up ClusterXL in different DCs</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Setting-up-ClusterXL-in-different-DCs/m-p/264500#M51987</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;So, does this involve VXLAN?&lt;BR /&gt;I understand that it does, at least to achieve L2 connectivity.&lt;/P&gt;
&lt;P&gt;I understand that having two different ISPs at each site is not a problem?&lt;/P&gt;
&lt;P&gt;We are not going to use VSX; we simply want to use the traditional ClusterXL modes but in geographically distant areas.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Dec 2025 12:38:02 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Setting-up-ClusterXL-in-different-DCs/m-p/264500#M51987</guid>
      <dc:creator>Matlu</dc:creator>
      <dc:date>2025-12-05T12:38:02Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up ClusterXL in different DCs</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Setting-up-ClusterXL-in-different-DCs/m-p/264509#M51993</link>
      <description>&lt;P&gt;tbh i dunno. As both DC are at same provider, this is a service provided by them and we don't have to care, which technology they use. For us, it's just "stretched VLAN" &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Dec 2025 13:39:26 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Setting-up-ClusterXL-in-different-DCs/m-p/264509#M51993</guid>
      <dc:creator>Vincent_Bacher</dc:creator>
      <dc:date>2025-12-05T13:39:26Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up ClusterXL in different DCs</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Setting-up-ClusterXL-in-different-DCs/m-p/264512#M51995</link>
      <description>&lt;P&gt;I LOVE that term...stretched VLAN lol&lt;/P&gt;</description>
      <pubDate>Fri, 05 Dec 2025 14:08:59 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Setting-up-ClusterXL-in-different-DCs/m-p/264512#M51995</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-12-05T14:08:59Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up ClusterXL in different DCs</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Setting-up-ClusterXL-in-different-DCs/m-p/264516#M51997</link>
      <description>&lt;P&gt;I don't even know if there's an “official” term for it, and frankly, I don't care. The provider has a name for it. And I didn't remember that either.&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":thinking_face:"&gt;🤔&lt;/span&gt;&lt;/P&gt;&lt;P&gt;I could also call it a chewing gum VLAN or a rubber band VLAN. Whatever.&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":rolling_on_the_floor_laughing:"&gt;🤣&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Dec 2025 14:20:59 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Setting-up-ClusterXL-in-different-DCs/m-p/264516#M51997</guid>
      <dc:creator>Vincent_Bacher</dc:creator>
      <dc:date>2025-12-05T14:20:59Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up ClusterXL in different DCs</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Setting-up-ClusterXL-in-different-DCs/m-p/264519#M51998</link>
      <description>&lt;P&gt;Copilot agrees &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot_1.png" style="width: 400px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/32318iF36032A6338E1F70/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Screenshot_1.png" alt="Screenshot_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt; &lt;/P&gt;</description>
      <pubDate>Fri, 05 Dec 2025 14:24:11 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Setting-up-ClusterXL-in-different-DCs/m-p/264519#M51998</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-12-05T14:24:11Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up ClusterXL in different DCs</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Setting-up-ClusterXL-in-different-DCs/m-p/264684#M52040</link>
      <description>&lt;P&gt;Hey brother,&lt;/P&gt;
&lt;P&gt;Just for a context, though we provided best options, happen to have basic network diagram?&lt;/P&gt;</description>
      <pubDate>Sun, 07 Dec 2025 19:10:47 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Setting-up-ClusterXL-in-different-DCs/m-p/264684#M52040</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-12-07T19:10:47Z</dc:date>
    </item>
  </channel>
</rss>

