<?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 Adding configured standalone FTD 2140 to FMC? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/adding-configured-standalone-ftd-2140-to-fmc/m-p/4092859#M1070512</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hello All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have a remote office where we run a standalone FTD 2140 appliance. Now there is the need to add that appliance to an existing FMC.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The 2140 appliance has locally configured routing (inside &amp;amp; outside interfaces), several site-to-site VPNs, several local policies to support the site-to-site VPNs and internet access for the users there, NAT for the VPN and an extensive list of objects and object groups.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My question here is “simple”, can I register the specific FTD 2140 with our existing FMC, without breaking the FTD’s configuration and without disrupting the remote office?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;</description>
    <pubDate>Wed, 27 May 2020 14:36:23 GMT</pubDate>
    <dc:creator>AlexPi</dc:creator>
    <dc:date>2020-05-27T14:36:23Z</dc:date>
    <item>
      <title>Adding configured standalone FTD 2140 to FMC?</title>
      <link>https://community.cisco.com/t5/network-security/adding-configured-standalone-ftd-2140-to-fmc/m-p/4092859#M1070512</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hello All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have a remote office where we run a standalone FTD 2140 appliance. Now there is the need to add that appliance to an existing FMC.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The 2140 appliance has locally configured routing (inside &amp;amp; outside interfaces), several site-to-site VPNs, several local policies to support the site-to-site VPNs and internet access for the users there, NAT for the VPN and an extensive list of objects and object groups.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My question here is “simple”, can I register the specific FTD 2140 with our existing FMC, without breaking the FTD’s configuration and without disrupting the remote office?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Wed, 27 May 2020 14:36:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/adding-configured-standalone-ftd-2140-to-fmc/m-p/4092859#M1070512</guid>
      <dc:creator>AlexPi</dc:creator>
      <dc:date>2020-05-27T14:36:23Z</dc:date>
    </item>
    <item>
      <title>Re: Adding configured standalone FTD 2140 to FMC?</title>
      <link>https://community.cisco.com/t5/network-security/adding-configured-standalone-ftd-2140-to-fmc/m-p/4092869#M1070513</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;No unfortunately not, you will need to re-create the configuration in the FMC, there will be disruption.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;On the FTD run &lt;STRONG&gt;configure manage delete&lt;/STRONG&gt; to remove the current configuration, then define the FMC host, IP and key using &lt;STRONG&gt;configure manager add &amp;lt;IP addr&amp;gt; &amp;lt;key&amp;gt;,&lt;/STRONG&gt; finally regsiter the FTD within the FMC and apply the new configuration.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 27 May 2020 14:51:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/adding-configured-standalone-ftd-2140-to-fmc/m-p/4092869#M1070513</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2020-05-27T14:51:56Z</dc:date>
    </item>
  </channel>
</rss>

