<?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: Replace Cisco FTD cluster in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/replace-cisco-ftd-cluster/m-p/4664533#M1092455</link>
    <description>&lt;P&gt;Thanks for reply Marvin! really appreciate that.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I completely understands that all software and policy configuration needs to match but only thing I'm not sure about is how its going to behave when I will failover to standby and break the cluster in order to bring new hardware and switch the traffic over to new hardware without impacting outage.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 05 Aug 2022 18:06:56 GMT</pubDate>
    <dc:creator>noman0058</dc:creator>
    <dc:date>2022-08-05T18:06:56Z</dc:date>
    <item>
      <title>Replace Cisco FTD cluster</title>
      <link>https://community.cisco.com/t5/network-security/replace-cisco-ftd-cluster/m-p/4663913#M1092439</link>
      <description>&lt;P&gt;Can someone share steps and things to watch out for when replacing of Cisco FTD 4110 to new 4120 in cluster mode.&lt;/P&gt;</description>
      <pubDate>Thu, 04 Aug 2022 19:32:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/replace-cisco-ftd-cluster/m-p/4663913#M1092439</guid>
      <dc:creator>noman0058</dc:creator>
      <dc:date>2022-08-04T19:32:37Z</dc:date>
    </item>
    <item>
      <title>Re: Replace Cisco FTD cluster</title>
      <link>https://community.cisco.com/t5/network-security/replace-cisco-ftd-cluster/m-p/4664118#M1092442</link>
      <description>&lt;P&gt;If you are changing models then you are replacing the entire cluster since all models must be the same in a given cluster.&lt;/P&gt;
&lt;P&gt;That's quite a significant undertaking and requires careful planning to ensure it goes smoothly. Each member of the new cluster would have to be bootstrapped and joined into the cluster. Software version, patch level, SRU, VDB and Geolocation would all have to be brought up to date. Interfaces to match the old cluster would have to be configured in shutdown mode in preparation for the actual cutover. The various policies (Access Control, NAT, Platform etc.) associated with the existing cluster would also need to be applied to the new cluster.&lt;/P&gt;
&lt;P&gt;Those are just the highlights off the top of my head. If you aren't working with an experienced field engineer for this, you should be.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Aug 2022 07:59:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/replace-cisco-ftd-cluster/m-p/4664118#M1092442</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2022-08-05T07:59:02Z</dc:date>
    </item>
    <item>
      <title>Re: Replace Cisco FTD cluster</title>
      <link>https://community.cisco.com/t5/network-security/replace-cisco-ftd-cluster/m-p/4664533#M1092455</link>
      <description>&lt;P&gt;Thanks for reply Marvin! really appreciate that.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I completely understands that all software and policy configuration needs to match but only thing I'm not sure about is how its going to behave when I will failover to standby and break the cluster in order to bring new hardware and switch the traffic over to new hardware without impacting outage.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Aug 2022 18:06:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/replace-cisco-ftd-cluster/m-p/4664533#M1092455</guid>
      <dc:creator>noman0058</dc:creator>
      <dc:date>2022-08-05T18:06:56Z</dc:date>
    </item>
    <item>
      <title>Re: Replace Cisco FTD cluster</title>
      <link>https://community.cisco.com/t5/network-security/replace-cisco-ftd-cluster/m-p/4664556#M1092456</link>
      <description>&lt;P&gt;So from your latest reply it seems you are talking about a high availability pair and not a cluster. In either case, you are essentially taking the existing firewall services completely offline and replacing them with another higher capacity set.&lt;/P&gt;
&lt;P&gt;There will be a planned outage - that's unavoidable.&lt;/P&gt;
&lt;P&gt;The primary things external to the firewall to ensure is that the upstream and downstream next hop devices clear their arp caches to account for the old IP addresses now being on new hosts.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Aug 2022 18:35:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/replace-cisco-ftd-cluster/m-p/4664556#M1092456</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2022-08-05T18:35:30Z</dc:date>
    </item>
  </channel>
</rss>

