<?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 hardware upgrade from 5600 to 7000 in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-hardware-upgrade-from-5600-to-7000/m-p/212445#M40331</link>
    <description>&lt;P&gt;Im sure one of the VSX experts will confirm it for you, but to me, that all sounds logical.&lt;/P&gt;
&lt;P&gt;Best,&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
    <pubDate>Fri, 26 Apr 2024 22:19:23 GMT</pubDate>
    <dc:creator>the_rock</dc:creator>
    <dc:date>2024-04-26T22:19:23Z</dc:date>
    <item>
      <title>VSX hardware upgrade from 5600 to 7000</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-hardware-upgrade-from-5600-to-7000/m-p/212443#M40330</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;We are planning to change a VSX cluster running r81.10 on 2x5600 gateway with a new 7000 cluster running r81.20.&lt;/P&gt;&lt;P&gt;The actual cluster has only 3 VS (some IPSEC vpn) and some virtual switches.&lt;/P&gt;&lt;P&gt;The management server is already in r81 20.&lt;/P&gt;&lt;P&gt;We were thinking of building a new cluster in parallel with different IPs.&lt;/P&gt;&lt;P&gt;Then provisionning new VS with different names and dummy IPs the time to create them and to avoid conflict.&lt;/P&gt;&lt;P&gt;Finally attaching the existing policies to these new VS.&lt;/P&gt;&lt;P&gt;The migration would be to shutdown the interfaces on the legacy cluster, modify the IP addresses on the new VS with the ones of the older VS.&lt;/P&gt;&lt;P&gt;When migration is done, deleting the old cluster from the management&lt;/P&gt;&lt;P&gt;Does this look possible?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 26 Apr 2024 22:17:38 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-hardware-upgrade-from-5600-to-7000/m-p/212443#M40330</guid>
      <dc:creator>DR_74</dc:creator>
      <dc:date>2024-04-26T22:17:38Z</dc:date>
    </item>
    <item>
      <title>Re: VSX hardware upgrade from 5600 to 7000</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-hardware-upgrade-from-5600-to-7000/m-p/212445#M40331</link>
      <description>&lt;P&gt;Im sure one of the VSX experts will confirm it for you, but to me, that all sounds logical.&lt;/P&gt;
&lt;P&gt;Best,&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Fri, 26 Apr 2024 22:19:23 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-hardware-upgrade-from-5600-to-7000/m-p/212445#M40331</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2024-04-26T22:19:23Z</dc:date>
    </item>
    <item>
      <title>Re: VSX hardware upgrade from 5600 to 7000</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-hardware-upgrade-from-5600-to-7000/m-p/212455#M40334</link>
      <description>&lt;P&gt;I have been using that method too. Works fine. I use the real ip adresses on the new vs’s but have all interfaces in shutdown on the switch. Then I shutdown the old vsx gateways for gratuitous arp to work. (Sometimes it dont). Then enable the interfaces on the new machines&lt;/P&gt;</description>
      <pubDate>Sat, 27 Apr 2024 09:21:43 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-hardware-upgrade-from-5600-to-7000/m-p/212455#M40334</guid>
      <dc:creator>Mattias_Jansson</dc:creator>
      <dc:date>2024-04-27T09:21:43Z</dc:date>
    </item>
    <item>
      <title>Re: VSX hardware upgrade from 5600 to 7000</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-hardware-upgrade-from-5600-to-7000/m-p/212466#M40337</link>
      <description>&lt;P&gt;Just a quick note - you can "force" an arp update through the following commands:&lt;/P&gt;
&lt;P&gt;arping -c 4 -A -I eth1 1.2.3.4&lt;/P&gt;
&lt;P&gt;For Proxy ARP addresses you do it like so:&lt;/P&gt;
&lt;P&gt;Expert# echo 1 &amp;gt; /proc/sys/net/ipv4/ip_nonlocal_bind&lt;BR /&gt;Expert# arping -c 4 -A -I eth1 1.2.3.4&lt;/P&gt;
&lt;P&gt;For every address the gateway is proxy arping for:&lt;/P&gt;
&lt;P&gt;Expert# fw ctl arp | cut -d\( -f2 | cut -d\) -f1 | xargs -i -t arping -c 4 -A -I eth1 {}&lt;/P&gt;</description>
      <pubDate>Sat, 27 Apr 2024 14:38:54 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-hardware-upgrade-from-5600-to-7000/m-p/212466#M40337</guid>
      <dc:creator>Ruan_Kotze</dc:creator>
      <dc:date>2024-04-27T14:38:54Z</dc:date>
    </item>
    <item>
      <title>Re: VSX hardware upgrade from 5600 to 7000</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-hardware-upgrade-from-5600-to-7000/m-p/212470#M40338</link>
      <description>&lt;P&gt;If you add '-P 256' to the xargs invocation, it can run multiple instances (up to 256 with that exact string) of the called tool in parallel. In environments with a lot of proxy ARP entries, this can speed things up&amp;nbsp;&lt;STRONG&gt;&lt;EM&gt;substantially&lt;/EM&gt;&lt;/STRONG&gt;.&lt;/P&gt;</description>
      <pubDate>Sat, 27 Apr 2024 21:32:00 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-hardware-upgrade-from-5600-to-7000/m-p/212470#M40338</guid>
      <dc:creator>Bob_Zimmerman</dc:creator>
      <dc:date>2024-04-27T21:32:00Z</dc:date>
    </item>
    <item>
      <title>Re: VSX hardware upgrade from 5600 to 7000</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-hardware-upgrade-from-5600-to-7000/m-p/212505#M40356</link>
      <description>&lt;P&gt;Both provided solutions should do it.&lt;BR /&gt;We usually first setup hardware with different management IPs, configure them without VSes and then we prepare scripts to remove the VSes from one device and add them to the other devices.&lt;BR /&gt;But that effort would not be feasible running just few VSes.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Apr 2024 05:02:28 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-hardware-upgrade-from-5600-to-7000/m-p/212505#M40356</guid>
      <dc:creator>Vincent_Bacher</dc:creator>
      <dc:date>2024-04-29T05:02:28Z</dc:date>
    </item>
    <item>
      <title>Re: VSX hardware upgrade from 5600 to 7000</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-hardware-upgrade-from-5600-to-7000/m-p/212509#M40357</link>
      <description>&lt;P&gt;That's the long way, but it'll work. Alternatively, you can look at using 'vsx_util reconfigure' to reuse all the existing stuff and push it out to the new gateways.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Apr 2024 07:09:17 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-hardware-upgrade-from-5600-to-7000/m-p/212509#M40357</guid>
      <dc:creator>emmap</dc:creator>
      <dc:date>2024-04-29T07:09:17Z</dc:date>
    </item>
    <item>
      <title>Re: VSX hardware upgrade from 5600 to 7000</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-hardware-upgrade-from-5600-to-7000/m-p/212516#M40359</link>
      <description>&lt;P&gt;This is what we usually do in our scripts&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":thumbs_up:"&gt;👍&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 29 Apr 2024 08:08:08 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-hardware-upgrade-from-5600-to-7000/m-p/212516#M40359</guid>
      <dc:creator>Vincent_Bacher</dc:creator>
      <dc:date>2024-04-29T08:08:08Z</dc:date>
    </item>
  </channel>
</rss>

