<?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: How to push same configuration to RMA'ed Unit in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/how-to-push-same-configuration-to-rma-ed-unit/m-p/4614867#M1090305</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1264907"&gt;@andry1234&lt;/a&gt;&amp;nbsp; This really depends on what you mean by add a new device.&amp;nbsp; You can take device specific backups and restore them to the failed / RMA'ed device.&amp;nbsp; The device backup backups up everything on the device including the management IP, gateway and FMC registration key.&lt;/P&gt;
&lt;P&gt;If you require further assistance please create a new post so the topic will be easier to find for others having the same issue.&lt;/P&gt;</description>
    <pubDate>Sun, 22 May 2022 06:04:40 GMT</pubDate>
    <dc:creator>Marius Gunnerud</dc:creator>
    <dc:date>2022-05-22T06:04:40Z</dc:date>
    <item>
      <title>How to push same configuration to RMA'ed Unit</title>
      <link>https://community.cisco.com/t5/network-security/how-to-push-same-configuration-to-rma-ed-unit/m-p/4404198#M1080836</link>
      <description>&lt;P&gt;In the process of RMAing a 5508 that was running FTD code and wondering what the best way to replace it would be.&amp;nbsp; The device was previously managed over a vpn tunnel and the management interface was used (used registration code and nat-id which I have documented).&amp;nbsp; I know the policies can be re-deployed once the device is in the FMC, but since the site has only a /30 putting the management interface on the WAN to get that connectivity isn't an option.&amp;nbsp; I was planning on doing the following:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1) Configuring the replacing device w/ a public ip and setup connectivity using the same registration code and nat-id if they'll work&lt;/P&gt;&lt;P&gt;2.) Go into the current device in the FMC, change the management ip address&lt;/P&gt;&lt;P&gt;3.) Confirm the device is registered, re-deploy the configuration/policies&lt;/P&gt;&lt;P&gt;4.) Once deployed, go back into the FMC and change the management ip back to what it currently is&lt;/P&gt;&lt;P&gt;5.) Go into the console of the device and change the management interface ip address back to the correct ip.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Will this work or will I need to delete the device from the FMC and re-add it and then setup the vpn and anything that might get lost during the removal of the device?&amp;nbsp; The FMC and FTD were both running&amp;nbsp;&lt;SPAN&gt;6.2.3.10.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 17 May 2021 17:07:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-push-same-configuration-to-rma-ed-unit/m-p/4404198#M1080836</guid>
      <dc:creator>mumbles202</dc:creator>
      <dc:date>2021-05-17T17:07:29Z</dc:date>
    </item>
    <item>
      <title>Re: How to push same configuration to RMA'ed Unit</title>
      <link>https://community.cisco.com/t5/network-security/how-to-push-same-configuration-to-rma-ed-unit/m-p/4405448#M1080900</link>
      <description>&lt;P&gt;I was able to add the device to the FMC by a public ip on a different segment, manually configure the interfaces and the static routing and then re-assign the same policies to RMA unit and push out the configuration.&amp;nbsp; I then went into the console and changed the management address to what should be the correct address across the vpn and updated the correct management address in the FMC.&amp;nbsp; Waiting on the device deployment today.&lt;/P&gt;</description>
      <pubDate>Wed, 19 May 2021 14:16:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-push-same-configuration-to-rma-ed-unit/m-p/4405448#M1080900</guid>
      <dc:creator>mumbles202</dc:creator>
      <dc:date>2021-05-19T14:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: How to push same configuration to RMA'ed Unit</title>
      <link>https://community.cisco.com/t5/network-security/how-to-push-same-configuration-to-rma-ed-unit/m-p/4530064#M1086349</link>
      <description>&lt;P&gt;Hi mumbles,&lt;/P&gt;&lt;P&gt;Potentially have an RMA situation on my hands.&amp;nbsp;&lt;BR /&gt;In addition to what you did above, did you also have to downgrade the FTD software on the replacement device?&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jan 2022 09:24:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-push-same-configuration-to-rma-ed-unit/m-p/4530064#M1086349</guid>
      <dc:creator>dtfletch83</dc:creator>
      <dc:date>2022-01-12T09:24:56Z</dc:date>
    </item>
    <item>
      <title>Re: How to push same configuration to RMA'ed Unit</title>
      <link>https://community.cisco.com/t5/network-security/how-to-push-same-configuration-to-rma-ed-unit/m-p/4530125#M1086357</link>
      <description>&lt;P&gt;If you are running FTD version 6.7 or higher you can follow the procedure that mumbles has described.&amp;nbsp; Prior to 6.7 you are not able to update the FMC IP on the FTD without unregistering it.&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jan 2022 10:55:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-push-same-configuration-to-rma-ed-unit/m-p/4530125#M1086357</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2022-01-12T10:55:59Z</dc:date>
    </item>
    <item>
      <title>Re: How to push same configuration to RMA'ed Unit</title>
      <link>https://community.cisco.com/t5/network-security/how-to-push-same-configuration-to-rma-ed-unit/m-p/4614716#M1090302</link>
      <description>&lt;P&gt;so if we add new device to fmc,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;we cannot have all config back like,&lt;/P&gt;
&lt;P&gt;- Interface config&lt;/P&gt;
&lt;P&gt;- routing&amp;nbsp;&lt;/P&gt;
&lt;P&gt;- zone interface&lt;/P&gt;
&lt;P&gt;- nat&lt;/P&gt;
&lt;P&gt;- vpn&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;can we simple have it back by doing option *Push Configuration*&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;im running ftd version 6.2 and FMC 6.4&lt;/P&gt;
&lt;P&gt;thank you&lt;/P&gt;</description>
      <pubDate>Sat, 21 May 2022 22:53:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-push-same-configuration-to-rma-ed-unit/m-p/4614716#M1090302</guid>
      <dc:creator>andry1234</dc:creator>
      <dc:date>2022-05-21T22:53:44Z</dc:date>
    </item>
    <item>
      <title>Re: How to push same configuration to RMA'ed Unit</title>
      <link>https://community.cisco.com/t5/network-security/how-to-push-same-configuration-to-rma-ed-unit/m-p/4614867#M1090305</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1264907"&gt;@andry1234&lt;/a&gt;&amp;nbsp; This really depends on what you mean by add a new device.&amp;nbsp; You can take device specific backups and restore them to the failed / RMA'ed device.&amp;nbsp; The device backup backups up everything on the device including the management IP, gateway and FMC registration key.&lt;/P&gt;
&lt;P&gt;If you require further assistance please create a new post so the topic will be easier to find for others having the same issue.&lt;/P&gt;</description>
      <pubDate>Sun, 22 May 2022 06:04:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-push-same-configuration-to-rma-ed-unit/m-p/4614867#M1090305</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2022-05-22T06:04:40Z</dc:date>
    </item>
    <item>
      <title>Re: How to push same configuration to RMA'ed Unit</title>
      <link>https://community.cisco.com/t5/network-security/how-to-push-same-configuration-to-rma-ed-unit/m-p/4614912#M1090308</link>
      <description>&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="296514D3-2D8F-4789-8CC6-52A7FCB36140.jpeg" style="width: 1125px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/151733i90AED2D2CCD2C257/image-size/medium?v=v2&amp;amp;px=400" role="button" title="296514D3-2D8F-4789-8CC6-52A7FCB36140.jpeg" alt="296514D3-2D8F-4789-8CC6-52A7FCB36140.jpeg" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt; thi my actual config &amp;nbsp;broken device from fmc, if i did push config option to new register device on fmc, will all my old config move to new device instantly?&lt;/P&gt;</description>
      <pubDate>Sun, 22 May 2022 09:59:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-push-same-configuration-to-rma-ed-unit/m-p/4614912#M1090308</guid>
      <dc:creator>andry1234</dc:creator>
      <dc:date>2022-05-22T09:59:47Z</dc:date>
    </item>
    <item>
      <title>Re: How to push same configuration to RMA'ed Unit</title>
      <link>https://community.cisco.com/t5/network-security/how-to-push-same-configuration-to-rma-ed-unit/m-p/4617854#M1090416</link>
      <description>&lt;P&gt;To replace a device with an RMA device, you can follow this guide:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/firepower/640/configuration/guide/fpmc-config-guide-v64/backup_and_restore.html#Cisco_Task.dita_a44c742a-9670-4b54-b792-6ba3a3133133" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/firepower/640/configuration/guide/fpmc-config-guide-v64/backup_and_restore.html#Cisco_Task.dita_a44c742a-9670-4b54-b792-6ba3a3133133&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 25 May 2022 21:46:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-push-same-configuration-to-rma-ed-unit/m-p/4617854#M1090416</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2022-05-25T21:46:38Z</dc:date>
    </item>
  </channel>
</rss>

