<?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: Replacing a faulty FTD with a new one on FMC in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/replacing-a-faulty-ftd-with-a-new-one-on-fmc/m-p/5334772#M1122977</link>
    <description>&lt;P&gt;It's only possible to restore completely from FMC if you had a device backup saved. However the NAT, ACP, prefilter and platform settings are saved in FMC and can be re-associated once you register the replacement device. You would have to reconfigure the settings for interfaces, routing etc. that are all under the Device Configuration menus.&lt;/P&gt;</description>
    <pubDate>Tue, 30 Sep 2025 15:54:06 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2025-09-30T15:54:06Z</dc:date>
    <item>
      <title>Replacing a faulty FTD with a new one on FMC</title>
      <link>https://community.cisco.com/t5/network-security/replacing-a-faulty-ftd-with-a-new-one-on-fmc/m-p/5334700#M1122971</link>
      <description>&lt;P&gt;Due to an error, an IT staff factory resetted a working FTD.&lt;/P&gt;
&lt;P&gt;The FTD was registered to a FMC with a valid licenze subscription.&lt;/P&gt;
&lt;P&gt;I have to reassociate my resetted FTD to FMC. Is there a way to do this without making again all configuration?&lt;/P&gt;
&lt;P&gt;I'd like to configure my new FTD with the old management address and reassociate it to my FMC with the existing policies (pre filter, nat, interfaces and so on)&lt;/P&gt;
&lt;P&gt;My firepower is a FPR-1010 associated to a vFMC. FW version is 7.0.6.3&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Many tks&lt;/P&gt;
&lt;P&gt;Johnny&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Sep 2025 11:21:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/replacing-a-faulty-ftd-with-a-new-one-on-fmc/m-p/5334700#M1122971</guid>
      <dc:creator>l.buschi</dc:creator>
      <dc:date>2025-09-30T11:21:08Z</dc:date>
    </item>
    <item>
      <title>Re: Replacing a faulty FTD with a new one on FMC</title>
      <link>https://community.cisco.com/t5/network-security/replacing-a-faulty-ftd-with-a-new-one-on-fmc/m-p/5334712#M1122973</link>
      <description>&lt;P&gt;If the same model and same Code of the device, follow RMA and restore config and once rebooted check the FMC can see the new FW&amp;nbsp; :&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/firepower/hw/getting-started/fmc-1000-2500-4500/fmc-1000-2500-4500.html#Cisco_Concept.dita_d88eb4c6-88f2-4fb2-b3d2-60d46d3bb461" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/firepower/hw/getting-started/fmc-1000-2500-4500/fmc-1000-2500-4500.html#Cisco_Concept.dita_d88eb4c6-88f2-4fb2-b3d2-60d46d3bb461&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.defenseorchestrator.com/cdfmc/t-restore-threat-defense-from-backup.html#!t-restore-threat-defense-from-backup.html" target="_blank" rel="noopener"&gt;https://docs.defenseorchestrator.com/cdfmc/t-restore-threat-defense-from-backup.html#!t-restore-threat-defense-from-backup.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Sep 2025 12:14:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/replacing-a-faulty-ftd-with-a-new-one-on-fmc/m-p/5334712#M1122973</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2025-09-30T12:14:49Z</dc:date>
    </item>
    <item>
      <title>Re: Replacing a faulty FTD with a new one on FMC</title>
      <link>https://community.cisco.com/t5/network-security/replacing-a-faulty-ftd-with-a-new-one-on-fmc/m-p/5334772#M1122977</link>
      <description>&lt;P&gt;It's only possible to restore completely from FMC if you had a device backup saved. However the NAT, ACP, prefilter and platform settings are saved in FMC and can be re-associated once you register the replacement device. You would have to reconfigure the settings for interfaces, routing etc. that are all under the Device Configuration menus.&lt;/P&gt;</description>
      <pubDate>Tue, 30 Sep 2025 15:54:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/replacing-a-faulty-ftd-with-a-new-one-on-fmc/m-p/5334772#M1122977</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2025-09-30T15:54:06Z</dc:date>
    </item>
    <item>
      <title>Re: Replacing a faulty FTD with a new one on FMC</title>
      <link>https://community.cisco.com/t5/network-security/replacing-a-faulty-ftd-with-a-new-one-on-fmc/m-p/5334782#M1122979</link>
      <description>&lt;P&gt;Unfortunately I don't have a saved device backup.&lt;/P&gt;
&lt;P&gt;So will I need to delete the original FTD and reassociate it configuring interfaces, routing and other device parameters?&lt;/P&gt;
&lt;P&gt;Tks&lt;/P&gt;
&lt;P&gt;Johnny&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Sep 2025 16:03:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/replacing-a-faulty-ftd-with-a-new-one-on-fmc/m-p/5334782#M1122979</guid>
      <dc:creator>l.buschi</dc:creator>
      <dc:date>2025-09-30T16:03:22Z</dc:date>
    </item>
    <item>
      <title>Re: Replacing a faulty FTD with a new one on FMC</title>
      <link>https://community.cisco.com/t5/network-security/replacing-a-faulty-ftd-with-a-new-one-on-fmc/m-p/5334793#M1122981</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/323069"&gt;@l.buschi&lt;/a&gt;&amp;nbsp;yes, that is correct.&lt;/P&gt;</description>
      <pubDate>Tue, 30 Sep 2025 16:19:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/replacing-a-faulty-ftd-with-a-new-one-on-fmc/m-p/5334793#M1122981</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2025-09-30T16:19:30Z</dc:date>
    </item>
    <item>
      <title>Re: Replacing a faulty FTD with a new one on FMC</title>
      <link>https://community.cisco.com/t5/network-security/replacing-a-faulty-ftd-with-a-new-one-on-fmc/m-p/5336430#M1123064</link>
      <description>&lt;P&gt;What about when the failing FTD is a membe of a active/standby HA pair? I presume the steps are as follows:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Break HA&lt;/LI&gt;&lt;LI&gt;Unregister device from FMC&lt;/LI&gt;&lt;LI&gt;Replace device&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;Register new device with same IP/name to FMC&lt;/LI&gt;&lt;LI&gt;Update to same software version than active FMC&lt;/LI&gt;&lt;LI&gt;Configure port-channel for failover link&lt;/LI&gt;&lt;LI&gt;Configure HA.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;We might do this soon as one of our four Firepower 2120 running FTD&amp;nbsp;&lt;SPAN&gt;7.4.2.4-9 is randomly crashing multiple times a day.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Oct 2025 08:14:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/replacing-a-faulty-ftd-with-a-new-one-on-fmc/m-p/5336430#M1123064</guid>
      <dc:creator>Network Diver</dc:creator>
      <dc:date>2025-10-07T08:14:45Z</dc:date>
    </item>
  </channel>
</rss>

