<?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: Check Point ElasticXL integration with FortiGate firewall in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Check-Point-ElasticXL-integration-with-FortiGate-firewall/m-p/276959#M105394</link>
    <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;You are correct. CPSG01 ETH2 and CPSG02 ETH2 need to be connected to access ports on a switch. You cannot create a LACP bond across two appliances unless you are using Maestro.&lt;/P&gt;
&lt;P&gt;A active/backup configuration for the links on Fortigate will not work. Both Check Point appliances need to send and receive CCP packets on the interface so they can 'see' each other.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;ClusterXL and ElasticXL require a layer 2 path between the appliances. So unless you can configure port 1 and port 2 on the Fortigate as a switch, you need separate switch to connect both Check Point appliances to the Fortigate.&lt;BR /&gt;&lt;BR /&gt;Martijn&lt;/P&gt;</description>
    <pubDate>Fri, 15 May 2026 06:45:06 GMT</pubDate>
    <dc:creator>Martijn</dc:creator>
    <dc:date>2026-05-15T06:45:06Z</dc:date>
    <item>
      <title>Check Point ElasticXL integration with FortiGate firewall</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Check-Point-ElasticXL-integration-with-FortiGate-firewall/m-p/276818#M105336</link>
      <description>&lt;P&gt;Hi, I am new to Check Point and I am currently planning for the deployment of two Check Point Quantum Force 9700 Plus Security Gateways running R82 with ElasticXL.&lt;/P&gt;&lt;P&gt;The two Security Gateways will be connected, each by a single link, to a FortiGate 101F firewall. So like:&lt;/P&gt;&lt;P&gt;FG port 1 -&amp;gt; CPSG01 eth2&lt;/P&gt;&lt;P&gt;FG port 2 -&amp;gt; CPSG02 eth2&lt;/P&gt;&lt;P&gt;However I am having difficulties understanding how the interfaces are supposed to be configured.&lt;/P&gt;&lt;P&gt;Based on my understanding, combining the two FortiGate links into a Layer 3 LACP bond is not viable because the two CP links are considered separate (based on this post I read&amp;nbsp;&lt;A href="https://community.checkpoint.com/t5/Firewall-and-Security-Management/ElasticXL-Bond-Aggregate-Behavior/td-p/249556" target="_blank" rel="noopener"&gt;https://community.checkpoint.com/t5/Firewall-and-Security-Management/ElasticXL-Bond-Aggregate-Behavior/td-p/249556&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;However, I'm not sure if I can configure the two FortiGate links as a redundant interface (active/backup) either because the SMO might choose the non-pivot member to forward traffic, which means both links on the FortiGate will need to be up. In that case, would ElasticXL detect the active interface automatically and forward traffic over it accordingly?&lt;/P&gt;&lt;P&gt;Would appreciate if anyone has insights into how I could go about configuring the interfaces.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 May 2026 05:25:44 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Check-Point-ElasticXL-integration-with-FortiGate-firewall/m-p/276818#M105336</guid>
      <dc:creator>Phianne_C133188</dc:creator>
      <dc:date>2026-05-12T05:25:44Z</dc:date>
    </item>
    <item>
      <title>Re: Check Point ElasticXL integration with FortiGate firewall</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Check-Point-ElasticXL-integration-with-FortiGate-firewall/m-p/276823#M105338</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;
&lt;P&gt;on my side, is not clear the reason why you want to connect the two check point directly to the Fortigate; you need to put a couple of switches L2 between Fortigate and Check Point.&lt;/P&gt;</description>
      <pubDate>Tue, 12 May 2026 07:03:17 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Check-Point-ElasticXL-integration-with-FortiGate-firewall/m-p/276823#M105338</guid>
      <dc:creator>simonemantovani</dc:creator>
      <dc:date>2026-05-12T07:03:17Z</dc:date>
    </item>
    <item>
      <title>Re: Check Point ElasticXL integration with FortiGate firewall</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Check-Point-ElasticXL-integration-with-FortiGate-firewall/m-p/276959#M105394</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;You are correct. CPSG01 ETH2 and CPSG02 ETH2 need to be connected to access ports on a switch. You cannot create a LACP bond across two appliances unless you are using Maestro.&lt;/P&gt;
&lt;P&gt;A active/backup configuration for the links on Fortigate will not work. Both Check Point appliances need to send and receive CCP packets on the interface so they can 'see' each other.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;ClusterXL and ElasticXL require a layer 2 path between the appliances. So unless you can configure port 1 and port 2 on the Fortigate as a switch, you need separate switch to connect both Check Point appliances to the Fortigate.&lt;BR /&gt;&lt;BR /&gt;Martijn&lt;/P&gt;</description>
      <pubDate>Fri, 15 May 2026 06:45:06 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Check-Point-ElasticXL-integration-with-FortiGate-firewall/m-p/276959#M105394</guid>
      <dc:creator>Martijn</dc:creator>
      <dc:date>2026-05-15T06:45:06Z</dc:date>
    </item>
  </channel>
</rss>

