<?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: smo priority in Hyperscale Firewall (Maestro)</title>
    <link>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/smo-priority/m-p/245994#M3306</link>
    <description>&lt;P&gt;I encountered a major problem recently with jumbo update.&amp;nbsp; at the time only 3 SGMs were functional.&amp;nbsp; the bad one was removed from the SG.&amp;nbsp; I patched SGM 1_2-1_3.&amp;nbsp; asg_monitor show all 3 were Active before I proceed to update smo master.&amp;nbsp; upon reboot of 1_1, the SG was completely down.&amp;nbsp; I dont know if I will ever run into this situation again.&amp;nbsp; it would be nice if i could promote 1_2 to smo permanently after it was patched before i tackle 1_1.&lt;/P&gt;&lt;P&gt;my SR is still under investigation.&amp;nbsp; TAC believes I ran into a problem as mentioned in&amp;nbsp;&lt;SPAN&gt;sk183181.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;for future jumbo patching, what can you recommend so I dont run into this problem?&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 08 Apr 2025 16:04:51 GMT</pubDate>
    <dc:creator>wsitu</dc:creator>
    <dc:date>2025-04-08T16:04:51Z</dc:date>
    <item>
      <title>smo priority</title>
      <link>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/smo-priority/m-p/245916#M3302</link>
      <description>&lt;P&gt;r81.20 dual orchestrators with 4 SGM&lt;/P&gt;&lt;P&gt;i understand by default the SGM with the lowest id would be smo master.&amp;nbsp; is it possible to change it such that another SGM take over as smo master?&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Apr 2025 04:28:41 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/smo-priority/m-p/245916#M3302</guid>
      <dc:creator>wsitu</dc:creator>
      <dc:date>2025-04-08T04:28:41Z</dc:date>
    </item>
    <item>
      <title>Re: smo priority</title>
      <link>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/smo-priority/m-p/245920#M3303</link>
      <description>&lt;P&gt;the only option is to stop the current SMO so another SGM will take its place using cpstop / clusterXL_admin down / shutdown&lt;/P&gt;</description>
      <pubDate>Tue, 08 Apr 2025 05:48:13 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/smo-priority/m-p/245920#M3303</guid>
      <dc:creator>Nir_Shamir</dc:creator>
      <dc:date>2025-04-08T05:48:13Z</dc:date>
    </item>
    <item>
      <title>Re: smo priority</title>
      <link>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/smo-priority/m-p/245923#M3304</link>
      <description>&lt;P&gt;Yea the SMO master is always the SGM with the lowest ID that is active, so it should ideally always be SGM 1 (on the active site in a dual-site security group). If SGM1 is rebooted, SGM2 takes over the SMO role. When SGM1 is finished booting and returns back into the security group as an Active member, it's back once again as the SMO master.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Apr 2025 06:40:17 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/smo-priority/m-p/245923#M3304</guid>
      <dc:creator>emmap</dc:creator>
      <dc:date>2025-04-08T06:40:17Z</dc:date>
    </item>
    <item>
      <title>Re: smo priority</title>
      <link>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/smo-priority/m-p/245994#M3306</link>
      <description>&lt;P&gt;I encountered a major problem recently with jumbo update.&amp;nbsp; at the time only 3 SGMs were functional.&amp;nbsp; the bad one was removed from the SG.&amp;nbsp; I patched SGM 1_2-1_3.&amp;nbsp; asg_monitor show all 3 were Active before I proceed to update smo master.&amp;nbsp; upon reboot of 1_1, the SG was completely down.&amp;nbsp; I dont know if I will ever run into this situation again.&amp;nbsp; it would be nice if i could promote 1_2 to smo permanently after it was patched before i tackle 1_1.&lt;/P&gt;&lt;P&gt;my SR is still under investigation.&amp;nbsp; TAC believes I ran into a problem as mentioned in&amp;nbsp;&lt;SPAN&gt;sk183181.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;for future jumbo patching, what can you recommend so I dont run into this problem?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Apr 2025 16:04:51 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/smo-priority/m-p/245994#M3306</guid>
      <dc:creator>wsitu</dc:creator>
      <dc:date>2025-04-08T16:04:51Z</dc:date>
    </item>
    <item>
      <title>Re: smo priority</title>
      <link>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/smo-priority/m-p/246017#M3307</link>
      <description>&lt;P&gt;It depends on what the issue was but changing the SMO master role is unlikely to have resolved the issue. If all the SGMs were down, there was no SMO available.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 09 Apr 2025 01:58:05 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/smo-priority/m-p/246017#M3307</guid>
      <dc:creator>emmap</dc:creator>
      <dc:date>2025-04-09T01:58:05Z</dc:date>
    </item>
  </channel>
</rss>

