<?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 Deploy ClusterXL with no/minimum downtime? in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/Deploy-ClusterXL-with-no-minimum-downtime/m-p/19864#M3691</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have an existing 12200 fw instance in place, and a new one I'd like to add to it. So, my question is could someone suggest a least service interruptive way to deploy a cluster which will assume the same IPs of the current instance as its VIPs?&lt;/P&gt;&lt;P&gt;Even if there's no other tricks other than following the official ClusterXL deployment guide I'd be interested to know if someone did something similar in the past and could provide a ballpark service outage duration?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 28 Dec 2018 15:32:22 GMT</pubDate>
    <dc:creator>Chckpnt_Charlie</dc:creator>
    <dc:date>2018-12-28T15:32:22Z</dc:date>
    <item>
      <title>Deploy ClusterXL with no/minimum downtime?</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Deploy-ClusterXL-with-no-minimum-downtime/m-p/19864#M3691</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have an existing 12200 fw instance in place, and a new one I'd like to add to it. So, my question is could someone suggest a least service interruptive way to deploy a cluster which will assume the same IPs of the current instance as its VIPs?&lt;/P&gt;&lt;P&gt;Even if there's no other tricks other than following the official ClusterXL deployment guide I'd be interested to know if someone did something similar in the past and could provide a ballpark service outage duration?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Dec 2018 15:32:22 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Deploy-ClusterXL-with-no-minimum-downtime/m-p/19864#M3691</guid>
      <dc:creator>Chckpnt_Charlie</dc:creator>
      <dc:date>2018-12-28T15:32:22Z</dc:date>
    </item>
    <item>
      <title>Re: Deploy ClusterXL with no/minimum downtime?</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Deploy-ClusterXL-with-no-minimum-downtime/m-p/19865#M3692</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please specify the version you are running, describe devices the 12000 unit is connected to presently and if it is involved in a dynamic routing.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Dec 2018 18:10:44 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Deploy-ClusterXL-with-no-minimum-downtime/m-p/19865#M3692</guid>
      <dc:creator>Vladimir</dc:creator>
      <dc:date>2018-12-28T18:10:44Z</dc:date>
    </item>
    <item>
      <title>Re: Deploy ClusterXL with no/minimum downtime?</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Deploy-ClusterXL-with-no-minimum-downtime/m-p/19866#M3693</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also, I would ask, what version are you running on your "current" gateways, and what version will you be running on the "new" hardware.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example, currently running R75.47 going to R77.30, or running R77.20 going to R77.30, or R80.10. Or will they be the same version?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've done this in the past going from Fujitsu;s to appliances as well as upgrading the version the gateways were on as the new hardware came into the cluster. Along with Vladimir's questions, I think some of these answers would determine a desired path.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Dec 2018 18:34:25 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Deploy-ClusterXL-with-no-minimum-downtime/m-p/19866#M3693</guid>
      <dc:creator>Mike_A</dc:creator>
      <dc:date>2018-12-28T18:34:25Z</dc:date>
    </item>
    <item>
      <title>Re: Deploy ClusterXL with no/minimum downtime?</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Deploy-ClusterXL-with-no-minimum-downtime/m-p/19867#M3694</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;running r80.10 on 12200 appliance which sits in between our WAN router and a core switch (no dynamic routing).&lt;/P&gt;&lt;P&gt;the second appliance matches the first one, so no upgrades or hw migrations. Just need to create a ClusterXl and add the current one and later on the second one to it in active/standby.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Dec 2018 19:51:32 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Deploy-ClusterXL-with-no-minimum-downtime/m-p/19867#M3694</guid>
      <dc:creator>Chckpnt_Charlie</dc:creator>
      <dc:date>2018-12-28T19:51:32Z</dc:date>
    </item>
    <item>
      <title>Re: Deploy ClusterXL with no/minimum downtime?</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Deploy-ClusterXL-with-no-minimum-downtime/m-p/19868#M3695</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also, the current appliance is distributed SMS/firewall. We have the fw license for the secondary FW appliance but not for the secondary SMS. Can I still build a ClusterXL with two appliances to achieve HA for firewalls but only run SMS on the active instance? Or do I positively need to migrate the SMS off of that appliance before I can ClusterXl the two?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Jan 2019 18:38:25 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Deploy-ClusterXL-with-no-minimum-downtime/m-p/19868#M3695</guid>
      <dc:creator>Chckpnt_Charlie</dc:creator>
      <dc:date>2019-01-04T18:38:25Z</dc:date>
    </item>
    <item>
      <title>Re: Deploy ClusterXL with no/minimum downtime?</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Deploy-ClusterXL-with-no-minimum-downtime/m-p/19869#M3696</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can only run management on both members of an HA cluster (a so-called Full HA setup).&lt;/P&gt;&lt;P&gt;Running management on one member of a cluster only is not supported.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Jan 2019 19:22:43 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Deploy-ClusterXL-with-no-minimum-downtime/m-p/19869#M3696</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2019-01-04T19:22:43Z</dc:date>
    </item>
    <item>
      <title>Re: Deploy ClusterXL with no/minimum downtime?</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Deploy-ClusterXL-with-no-minimum-downtime/m-p/19870#M3697</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not to mention that management on the box in HA is .... rather clumsy.&lt;/P&gt;&lt;P&gt;I suggest you create a seperate management system.&lt;/P&gt;&lt;P&gt;The migration might be a bit of a steep path if you haven't the experience. So unless you have plenty of time to tinker with it without someone clubbing you for a day long outage I suggest you hire someone to help you out there.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Jan 2019 11:47:49 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Deploy-ClusterXL-with-no-minimum-downtime/m-p/19870#M3697</guid>
      <dc:creator>Hugo_vd_Kooij</dc:creator>
      <dc:date>2019-01-09T11:47:49Z</dc:date>
    </item>
  </channel>
</rss>

