<?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 Maestro Dual Site - From one to two orchestrator per site in Hyperscale Firewall (Maestro)</title>
    <link>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/Maestro-Dual-Site-From-one-to-two-orchestrator-per-site/m-p/256125#M3598</link>
    <description>&lt;P&gt;As title says, the plan is to go from a single MHO per site to two. MHO-175 in this case.&lt;/P&gt;
&lt;P&gt;Uplinks and downlinks will be spread between the two MHO's.&lt;/P&gt;
&lt;P&gt;Is it recommended to use one management port from the first MHO or connect both port and create a aggregation for management?&lt;/P&gt;
&lt;P&gt;We're OK to rebuild the SG if needed, but since there are 2 MHO in both sites, each with management uplink for now, there is also the question of whether it's best practice and recommended from experience.&lt;/P&gt;</description>
    <pubDate>Thu, 28 Aug 2025 11:49:26 GMT</pubDate>
    <dc:creator>Alex-</dc:creator>
    <dc:date>2025-08-28T11:49:26Z</dc:date>
    <item>
      <title>Maestro Dual Site - From one to two orchestrator per site</title>
      <link>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/Maestro-Dual-Site-From-one-to-two-orchestrator-per-site/m-p/256125#M3598</link>
      <description>&lt;P&gt;As title says, the plan is to go from a single MHO per site to two. MHO-175 in this case.&lt;/P&gt;
&lt;P&gt;Uplinks and downlinks will be spread between the two MHO's.&lt;/P&gt;
&lt;P&gt;Is it recommended to use one management port from the first MHO or connect both port and create a aggregation for management?&lt;/P&gt;
&lt;P&gt;We're OK to rebuild the SG if needed, but since there are 2 MHO in both sites, each with management uplink for now, there is also the question of whether it's best practice and recommended from experience.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Aug 2025 11:49:26 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/Maestro-Dual-Site-From-one-to-two-orchestrator-per-site/m-p/256125#M3598</guid>
      <dc:creator>Alex-</dc:creator>
      <dc:date>2025-08-28T11:49:26Z</dc:date>
    </item>
    <item>
      <title>Re: Maestro Dual Site - From one to two orchestrator per site</title>
      <link>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/Maestro-Dual-Site-From-one-to-two-orchestrator-per-site/m-p/256126#M3599</link>
      <description>&lt;P&gt;When working with two MHO's per site (the recommended deployment) each port , data or management, is bonded with at least two ports from each MHO.&lt;/P&gt;
&lt;P&gt;This way you have full HA between them.&lt;/P&gt;
&lt;P&gt;Regarding the move from 1 MHO to 2 MHO's . This procedure is a bit complicated and involves a lot of manual changes in configuration files.&lt;/P&gt;
&lt;P&gt;I would recommend working with our Professional Services to do such a change.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Aug 2025 11:51:39 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/Maestro-Dual-Site-From-one-to-two-orchestrator-per-site/m-p/256126#M3599</guid>
      <dc:creator>Nir_Shamir</dc:creator>
      <dc:date>2025-08-28T11:51:39Z</dc:date>
    </item>
    <item>
      <title>Re: Maestro Dual Site - From one to two orchestrator per site</title>
      <link>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/Maestro-Dual-Site-From-one-to-two-orchestrator-per-site/m-p/256264#M3600</link>
      <description>&lt;P&gt;Thank you for the quick reply.&lt;/P&gt;
&lt;P&gt;We are OK with recreating the SG from scratch, as the project is on the launchpad and the current cluster still manages traffic.&lt;/P&gt;
&lt;P&gt;Since there are external parties in charge of the network infrastructure to which we will need to make demands, we'd like to clarify the following points to explore all options:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Can we work with dual uplinks/downlinks but keep only one Management port (1) on the MHO-175? Current tests show the policy installs and failovers work&lt;/LI&gt;
&lt;LI&gt;Can we delete the SG, create a MAGG with just one port on the first MHO, recreate the SG and in the future connect the port 1 of the second MHO which will then join the MAGG?&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 31 Aug 2025 17:15:58 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/Maestro-Dual-Site-From-one-to-two-orchestrator-per-site/m-p/256264#M3600</guid>
      <dc:creator>Alex-</dc:creator>
      <dc:date>2025-08-31T17:15:58Z</dc:date>
    </item>
    <item>
      <title>Re: Maestro Dual Site - From one to two orchestrator per site</title>
      <link>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/Maestro-Dual-Site-From-one-to-two-orchestrator-per-site/m-p/256342#M3604</link>
      <description>&lt;P&gt;Yes and yes.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 02 Sep 2025 01:13:20 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/Maestro-Dual-Site-From-one-to-two-orchestrator-per-site/m-p/256342#M3604</guid>
      <dc:creator>emmap</dc:creator>
      <dc:date>2025-09-02T01:13:20Z</dc:date>
    </item>
  </channel>
</rss>

