<?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: MAESTRO Dual Single Site Configuration - bonding of interface and management ip address in Hyperscale Firewall (Maestro)</title>
    <link>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/MAESTRO-Dual-Single-Site-Configuration-bonding-of-interface-and/m-p/252340#M3493</link>
    <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;First of all, maestro is a solution composed by orchestrador and Security Gateway Modules SGM, so you have dual orchestrator, you manage each orchestrator via Mgmt1 and Mgmt2 rear panel. each orchestrator have their own ip-address it does mean orchestrator 1 IP 10.10.10.1/24 orchestrator 2 10.10.10.2/24.&lt;BR /&gt;Now for Security group, when you create the security Group you have add management interfaces eth1-Mgmt1 (orchestator1) and eth2-Mgmt1(ochestrator2) both should be in management bond no traffic bond. we recommend to bond them for redundancy. And yes you can use the same subnet like 10.10.10.3/24&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you have dual site, site 2 must be a mirror of site 1.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I recommend to check Jump Start videos&amp;nbsp;&lt;A href="https://community.checkpoint.com/t5/Check-Point-for-Beginners/Check-Point-Jump-Start-Course-Maestro/ba-p/153352#:~:text=This%20free%20training%20was%20developed%20for%20customers%20new,via%20the%20web%20user%20interface%20and%20SmartConsole%20features." target="_blank" rel="noopener"&gt;Check Point Jump Start Course: Maestro - Check Point CheckMates&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;and engage check Point IGS (Professional Services) contact your local SE&lt;/P&gt;</description>
    <pubDate>Tue, 01 Jul 2025 13:58:20 GMT</pubDate>
    <dc:creator>Dario_Perez</dc:creator>
    <dc:date>2025-07-01T13:58:20Z</dc:date>
    <item>
      <title>MAESTRO Dual Single Site Configuration - bonding of interface and management ip address</title>
      <link>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/MAESTRO-Dual-Single-Site-Configuration-bonding-of-interface-and/m-p/252314#M3492</link>
      <description>&lt;P&gt;Hi Checkmates.&lt;/P&gt;&lt;P&gt;Good day. I just wanted to clarify on the configuraiton settings of maestro (dual maestro in a single site);&lt;/P&gt;&lt;P&gt;-For the bonding of interfaces, Maestro-1 and Maestro-2 are already connected and can be adminitered via its management port ip (located at the back), what interfaces should be bonded;&lt;/P&gt;&lt;P&gt;Any sample interface assignments bonding?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, for the management interface ip, e.g for MNGT1- 10.10.10.10/24, can i assign same subnet to the Maestro -eth1-Mgmt1&lt;/P&gt;&lt;P&gt;thank you.&lt;/P&gt;&lt;P&gt;Leangf&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 01 Jul 2025 02:44:23 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/MAESTRO-Dual-Single-Site-Configuration-bonding-of-interface-and/m-p/252314#M3492</guid>
      <dc:creator>leangf_leangf1</dc:creator>
      <dc:date>2025-07-01T02:44:23Z</dc:date>
    </item>
    <item>
      <title>Re: MAESTRO Dual Single Site Configuration - bonding of interface and management ip address</title>
      <link>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/MAESTRO-Dual-Single-Site-Configuration-bonding-of-interface-and/m-p/252340#M3493</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;First of all, maestro is a solution composed by orchestrador and Security Gateway Modules SGM, so you have dual orchestrator, you manage each orchestrator via Mgmt1 and Mgmt2 rear panel. each orchestrator have their own ip-address it does mean orchestrator 1 IP 10.10.10.1/24 orchestrator 2 10.10.10.2/24.&lt;BR /&gt;Now for Security group, when you create the security Group you have add management interfaces eth1-Mgmt1 (orchestator1) and eth2-Mgmt1(ochestrator2) both should be in management bond no traffic bond. we recommend to bond them for redundancy. And yes you can use the same subnet like 10.10.10.3/24&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you have dual site, site 2 must be a mirror of site 1.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I recommend to check Jump Start videos&amp;nbsp;&lt;A href="https://community.checkpoint.com/t5/Check-Point-for-Beginners/Check-Point-Jump-Start-Course-Maestro/ba-p/153352#:~:text=This%20free%20training%20was%20developed%20for%20customers%20new,via%20the%20web%20user%20interface%20and%20SmartConsole%20features." target="_blank" rel="noopener"&gt;Check Point Jump Start Course: Maestro - Check Point CheckMates&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;and engage check Point IGS (Professional Services) contact your local SE&lt;/P&gt;</description>
      <pubDate>Tue, 01 Jul 2025 13:58:20 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/MAESTRO-Dual-Single-Site-Configuration-bonding-of-interface-and/m-p/252340#M3493</guid>
      <dc:creator>Dario_Perez</dc:creator>
      <dc:date>2025-07-01T13:58:20Z</dc:date>
    </item>
    <item>
      <title>Re: MAESTRO Dual Single Site Configuration - bonding of interface and management ip address</title>
      <link>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/MAESTRO-Dual-Single-Site-Configuration-bonding-of-interface-and/m-p/252343#M3494</link>
      <description>&lt;P&gt;Hi Dario, thank you for the information. Since the SGs were connected and detected by the Orchestrator1 and 2 via their downlink ports. This have to be bonded also as recommended?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;Leangf&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 01 Jul 2025 14:37:56 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/MAESTRO-Dual-Single-Site-Configuration-bonding-of-interface-and/m-p/252343#M3494</guid>
      <dc:creator>leangf_leangf1</dc:creator>
      <dc:date>2025-07-01T14:37:56Z</dc:date>
    </item>
    <item>
      <title>Re: MAESTRO Dual Single Site Configuration - bonding of interface and management ip address</title>
      <link>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/MAESTRO-Dual-Single-Site-Configuration-bonding-of-interface-and/m-p/252370#M3495</link>
      <description>&lt;P&gt;donwlink is bonded by default, don't need configure it. just cabling.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 01 Jul 2025 18:21:02 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/MAESTRO-Dual-Single-Site-Configuration-bonding-of-interface-and/m-p/252370#M3495</guid>
      <dc:creator>Dario_Perez</dc:creator>
      <dc:date>2025-07-01T18:21:02Z</dc:date>
    </item>
    <item>
      <title>Re: MAESTRO Dual Single Site Configuration - bonding of interface and management ip address</title>
      <link>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/MAESTRO-Dual-Single-Site-Configuration-bonding-of-interface-and/m-p/252392#M3496</link>
      <description>&lt;P&gt;Hello Dario,&lt;/P&gt;&lt;P&gt;Noted on this. For the revenue ports with corresponding ip addresses who will configured. eg. on orchestrator-1 (1/5/1] and on orchestrator-2 [2/5/1] needs to be bonded and assigned ip address (e.g: zone: Trust). and so on for the remaining interfaces that will participate in the network .&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jul 2025 01:58:59 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/MAESTRO-Dual-Single-Site-Configuration-bonding-of-interface-and/m-p/252392#M3496</guid>
      <dc:creator>leangf_leangf1</dc:creator>
      <dc:date>2025-07-02T01:58:59Z</dc:date>
    </item>
  </channel>
</rss>

