<?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: Replacement of a VRRP Cluster in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Replacement-of-a-VRRP-Cluster/m-p/198481#M37157</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Management is done through a MDSM already running R81.10.&lt;/P&gt;</description>
    <pubDate>Tue, 21 Nov 2023 09:08:31 GMT</pubDate>
    <dc:creator>Josh28</dc:creator>
    <dc:date>2023-11-21T09:08:31Z</dc:date>
    <item>
      <title>Replacement of a VRRP Cluster</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Replacement-of-a-VRRP-Cluster/m-p/198468#M37155</link>
      <description>&lt;P&gt;Dear mates,&lt;/P&gt;&lt;P&gt;I’m in charge of replacing a cluster of 12600 configured in VRRP and running R80.20 to a new cluster of 6600 running R81.10. From experience of hardware replacement, and after reading some posts here, I think of doing the following:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Install the new gateways using the clish configuration of the old ones by keeping the same IP address configurations, proxy arp / mcvr configs, static routes etc, fwkern.conf file etc...&lt;/LI&gt;&lt;LI&gt;Power off the 12600 standby member and connect to R81.10 new standby member&lt;/LI&gt;&lt;LI&gt;On the 6600, from the CMA, redo SIC, change cluster version and hardware model, fix topology as some interfaces name changed and install the policy in the gateway&lt;/LI&gt;&lt;LI&gt;Power off the 12600 primary unit to force traffic on the new 6600&lt;/LI&gt;&lt;LI&gt;Repeat the operation with the second R81.10 member etc…&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Usually I don’t really think of ARP issue because of the VMAC feature of ClusterXL but being new to VRRP, I’m having seconds thoughts.&lt;/P&gt;&lt;P&gt;On the router side, on the PortChannel of the 12600 I see the following mac addresses :&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Mac addresses declared on the MCVR configuration: to the best of my knowledge, those shouldn’t be impacted by the replacement as I’ll configure them on the new devices&lt;/LI&gt;&lt;LI&gt;Physical mac address associated to the bonding interfaces (50+ Vlans): this mac address will change and therefore require a G-ARP to update the mac address table of the router ? Easiest way would be to clear the arp cache on the Port-channel to force the update&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Am I wrong on the analysis ? Is there some things I should verify before/after the switch of the cluster ?&lt;/P&gt;&lt;P&gt;Any tips will be appreciated.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Nov 2023 08:47:52 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Replacement-of-a-VRRP-Cluster/m-p/198468#M37155</guid>
      <dc:creator>Josh28</dc:creator>
      <dc:date>2023-11-21T08:47:52Z</dc:date>
    </item>
    <item>
      <title>Re: Replacement of a VRRP Cluster</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Replacement-of-a-VRRP-Cluster/m-p/198472#M37156</link>
      <description>&lt;P&gt;What about the SMS ?&lt;/P&gt;</description>
      <pubDate>Tue, 21 Nov 2023 08:56:03 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Replacement-of-a-VRRP-Cluster/m-p/198472#M37156</guid>
      <dc:creator>G_W_Albrecht</dc:creator>
      <dc:date>2023-11-21T08:56:03Z</dc:date>
    </item>
    <item>
      <title>Re: Replacement of a VRRP Cluster</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Replacement-of-a-VRRP-Cluster/m-p/198481#M37157</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Management is done through a MDSM already running R81.10.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Nov 2023 09:08:31 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Replacement-of-a-VRRP-Cluster/m-p/198481#M37157</guid>
      <dc:creator>Josh28</dc:creator>
      <dc:date>2023-11-21T09:08:31Z</dc:date>
    </item>
    <item>
      <title>Re: Replacement of a VRRP Cluster</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Replacement-of-a-VRRP-Cluster/m-p/198489#M37159</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;So the new cluster will also be VRRP or are you going for ClusterXL on the new setup?&lt;/P&gt;
&lt;P&gt;If you stay with VRRP and use the same VRRP router ID, the virtual MAC for the virtual IP's should not change.&lt;BR /&gt;ClusterXL by default uses the MAC of the active member, but with VMAC you can change this if you like.&lt;BR /&gt;&lt;BR /&gt;Yes, the MAC of the bonding group will change, but if you are going for VRRP or VMAC that should not be a problem for the virtual IP's. But in these cases it is always good to know how to send a G-ARP to clear ARP tables. Just in case. Or have access to routers to clear the ARP table on those devices.&lt;BR /&gt;&lt;BR /&gt;Note the current MAC for virtual IP's and compare them after the change.&lt;BR /&gt;&lt;BR /&gt;And with hardware swap, check if local.arp files are created for static NAT.&lt;BR /&gt;&lt;BR /&gt;Martijn&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Nov 2023 10:02:40 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Replacement-of-a-VRRP-Cluster/m-p/198489#M37159</guid>
      <dc:creator>Martijn</dc:creator>
      <dc:date>2023-11-21T10:02:40Z</dc:date>
    </item>
    <item>
      <title>Re: Replacement of a VRRP Cluster</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Replacement-of-a-VRRP-Cluster/m-p/198493#M37161</link>
      <description>&lt;P&gt;Hi Martijn,&lt;/P&gt;&lt;P&gt;Thanks for your reply.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I’ll Keep VRRP as it’s a customer’s request, with the same configuration so VRIDs will be the same.&lt;/P&gt;&lt;P&gt;I found this post about sending garp from the Check Point &lt;A href="https://community.checkpoint.com/t5/Security-Gateways/How-to-send-G-ARP-manually/td-p/69895" target="_blank"&gt;https://community.checkpoint.com/t5/Security-Gateways/How-to-send-G-ARP-manually/td-p/69895&lt;/A&gt; seems usefull, but I might just do it from the router side.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Nov 2023 10:59:02 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Replacement-of-a-VRRP-Cluster/m-p/198493#M37161</guid>
      <dc:creator>Josh28</dc:creator>
      <dc:date>2023-11-21T10:59:02Z</dc:date>
    </item>
    <item>
      <title>Re: Replacement of a VRRP Cluster</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Replacement-of-a-VRRP-Cluster/m-p/198497#M37163</link>
      <description>&lt;P&gt;I really believe below process would be best for you.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.checkpoint.com/t5/Security-Gateways/Replace-Upgrade-Cluster/td-p/69216" target="_blank"&gt;https://community.checkpoint.com/t5/Security-Gateways/Replace-Upgrade-Cluster/td-p/69216&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Nov 2023 12:14:00 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Replacement-of-a-VRRP-Cluster/m-p/198497#M37163</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2023-11-21T12:14:00Z</dc:date>
    </item>
  </channel>
</rss>

