<?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: Firepower Migration Tool Can't Recognize ASA's Version in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firepower-migration-tool-can-t-recognize-asa-s-version/m-p/4527324#M1086209</link>
    <description>&lt;P&gt;Is it possible for you to select the source and connect via ssh vs. uploading the config file manually? I prefer that method when converting as it is more full-featured.&lt;/P&gt;</description>
    <pubDate>Thu, 06 Jan 2022 08:11:14 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2022-01-06T08:11:14Z</dc:date>
    <item>
      <title>Firepower Migration Tool Can't Recognize ASA's Version</title>
      <link>https://community.cisco.com/t5/network-security/firepower-migration-tool-can-t-recognize-asa-s-version/m-p/4527217#M1086204</link>
      <description>&lt;P&gt;Hi, team.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope that you're right.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a situation with migration Cisco Firepower Chassis with ASA Software to Migrate Cisco Firepower Threat Defense with FMC.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The point is the following, I have Cisco ASA in Firepower Chassis and its version is 9.14(1). I need to migrate the configurations and I's using Firepower Migration Tool to complete that process, but when I upload the configuration file, the FMT say me &lt;STRONG&gt;"ASA Software Version not found, kindly upload 'show running-config' collected from ASA".&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm uploading the TXT configuration's file that contain the "show running-config".&lt;/P&gt;&lt;P&gt;I don't find the cause about that, and are the any solutions for that?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="FMT-IMG.png" style="width: 580px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/140638i993150BB37C857A6/image-dimensions/580x304?v=v2" width="580" height="304" role="button" title="FMT-IMG.png" alt="FMT-IMG.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jan 2022 00:45:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-migration-tool-can-t-recognize-asa-s-version/m-p/4527217#M1086204</guid>
      <dc:creator>DarlynDiaz2948</dc:creator>
      <dc:date>2022-01-06T00:45:43Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower Migration Tool Can't Recognize ASA's Version</title>
      <link>https://community.cisco.com/t5/network-security/firepower-migration-tool-can-t-recognize-asa-s-version/m-p/4527324#M1086209</link>
      <description>&lt;P&gt;Is it possible for you to select the source and connect via ssh vs. uploading the config file manually? I prefer that method when converting as it is more full-featured.&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jan 2022 08:11:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-migration-tool-can-t-recognize-asa-s-version/m-p/4527324#M1086209</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2022-01-06T08:11:14Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower Migration Tool Can't Recognize ASA's Version</title>
      <link>https://community.cisco.com/t5/network-security/firepower-migration-tool-can-t-recognize-asa-s-version/m-p/4527379#M1086215</link>
      <description>&lt;P&gt;It's not possible because I'm going to migrate ASA to FTD software to connect with the FMC, So that mean, when I will migrate the ASA to FTD, I won't have connection with ASA.&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jan 2022 11:10:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-migration-tool-can-t-recognize-asa-s-version/m-p/4527379#M1086215</guid>
      <dc:creator>DarlynDiaz2948</dc:creator>
      <dc:date>2022-01-06T11:10:00Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower Migration Tool Can't Recognize ASA's Version</title>
      <link>https://community.cisco.com/t5/network-security/firepower-migration-tool-can-t-recognize-asa-s-version/m-p/4527619#M1086226</link>
      <description>&lt;P&gt;You run the migration tool while the old ASA and new FMC are online. Only after you have pushed the config to the FMC and validated it would you need to take the ASA offline in anticipation of replacing it with the FTD device.&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jan 2022 20:30:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-migration-tool-can-t-recognize-asa-s-version/m-p/4527619#M1086226</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2022-01-06T20:30:11Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower Migration Tool Can't Recognize ASA's Version</title>
      <link>https://community.cisco.com/t5/network-security/firepower-migration-tool-can-t-recognize-asa-s-version/m-p/4527633#M1086228</link>
      <description>&lt;P&gt;Yes, I'm understanding that you said me, but the devices that has ASA OS will be the same same devices that will have FTD OS. So if I pass the configuration to FMC without FTD device, a lot of configuration wii not to pass to the FMC, for example the VPN tunneling s2s.&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jan 2022 20:49:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-migration-tool-can-t-recognize-asa-s-version/m-p/4527633#M1086228</guid>
      <dc:creator>DarlynDiaz2948</dc:creator>
      <dc:date>2022-01-06T20:49:50Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower Migration Tool Can't Recognize ASA's Version</title>
      <link>https://community.cisco.com/t5/network-security/firepower-migration-tool-can-t-recognize-asa-s-version/m-p/4528419#M1086268</link>
      <description>&lt;P&gt;Most of the configuration will transfer even without a target FTD device to assign the policies. For instance, Access Control Policy and NAT Policy will transfer completely.&lt;/P&gt;
&lt;P&gt;One possible work around is that if you are moving from one HA pair to another you could break the HA and use the standby unit as the target device and thus migrate all of the bits that might be omitted without having a live target.&lt;/P&gt;
&lt;P&gt;In any case, you can still connect to the live source device.&lt;/P&gt;</description>
      <pubDate>Sun, 09 Jan 2022 03:05:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-migration-tool-can-t-recognize-asa-s-version/m-p/4528419#M1086268</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2022-01-09T03:05:53Z</dc:date>
    </item>
  </channel>
</rss>

