<?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: VSX Cluster update and hardware migration in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Cluster-update-and-hardware-migration/m-p/128562#M18732</link>
    <description>&lt;P&gt;I have done that in the past with vsx provisioning util (&lt;SPAN&gt;sk100645). In effect, there are two ways of migrating:&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;&lt;SPAN&gt;If you can afford different names of VSX cluster:&amp;nbsp;&lt;/SPAN&gt;
&lt;OL&gt;
&lt;LI&gt;&lt;SPAN&gt;setup new vsx cluster,&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;capture topology&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;modify text files to reflect interface names change&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;build the same topology for all new VSs&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;apply same policies&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;swap old and new systems during the service window planned for this op&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;If you have to keep the same names, replicate MDS in a lab, do all steps but 6 in the lab, then swap both MDS and VSX clusters. This requires much longer service window and also mgmt freeze.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&lt;SPAN&gt;Option 1 allows gradual migration of per VS from old to new (assuming the topology allows that)&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 01 Sep 2021 13:44:49 GMT</pubDate>
    <dc:creator>_Val_</dc:creator>
    <dc:date>2021-09-01T13:44:49Z</dc:date>
    <item>
      <title>VSX Cluster update and hardware migration</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Cluster-update-and-hardware-migration/m-p/128561#M18731</link>
      <description>&lt;P&gt;Dear folks,&lt;/P&gt;&lt;P&gt;I need to update an vsx cluster from R80.30 to R80.40 and also replace the hardware. The hardware is now an appliance 5900 and will be 26000. Furthermore, my "bond3" should become "bond1" and the interfaces of the 5900 have a different naming than the one on the 26000.&lt;/P&gt;&lt;P&gt;The new 26000 appliances will get different managmenet IPs, so both clusters can be online at the same (when taking care about duplicate. IPs &lt;span class="lia-unicode-emoji" title=":grinning_face:"&gt;😀&lt;/span&gt;).&lt;/P&gt;&lt;P&gt;MDM is running on R80.40&lt;/P&gt;&lt;P&gt;Does anyone has an idea how to do it?&lt;/P&gt;&lt;P&gt;Best regards,&lt;BR /&gt;Christian&lt;/P&gt;</description>
      <pubDate>Wed, 01 Sep 2021 13:23:41 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Cluster-update-and-hardware-migration/m-p/128561#M18731</guid>
      <dc:creator>Christian_Koehl</dc:creator>
      <dc:date>2021-09-01T13:23:41Z</dc:date>
    </item>
    <item>
      <title>Re: VSX Cluster update and hardware migration</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Cluster-update-and-hardware-migration/m-p/128562#M18732</link>
      <description>&lt;P&gt;I have done that in the past with vsx provisioning util (&lt;SPAN&gt;sk100645). In effect, there are two ways of migrating:&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;&lt;SPAN&gt;If you can afford different names of VSX cluster:&amp;nbsp;&lt;/SPAN&gt;
&lt;OL&gt;
&lt;LI&gt;&lt;SPAN&gt;setup new vsx cluster,&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;capture topology&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;modify text files to reflect interface names change&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;build the same topology for all new VSs&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;apply same policies&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;swap old and new systems during the service window planned for this op&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;If you have to keep the same names, replicate MDS in a lab, do all steps but 6 in the lab, then swap both MDS and VSX clusters. This requires much longer service window and also mgmt freeze.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&lt;SPAN&gt;Option 1 allows gradual migration of per VS from old to new (assuming the topology allows that)&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 01 Sep 2021 13:44:49 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Cluster-update-and-hardware-migration/m-p/128562#M18732</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2021-09-01T13:44:49Z</dc:date>
    </item>
  </channel>
</rss>

