<?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 FTD deployment issues after upgrading to 6.6 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ftd-deployment-issues-after-upgrading-to-6-6/m-p/4165041#M1074629</link>
    <description>&lt;P&gt;I am in the process of upgrading a bunch of ASA 5508-X from FTD version 6.3 to 6.6.&lt;/P&gt;&lt;P&gt;They are all setup in failover pairs with a couple of sub interface.&lt;/P&gt;&lt;P&gt;All the configuration is basically the same except for the interface address configuration and ACPs.&amp;nbsp;&lt;/P&gt;&lt;P&gt;After the upgrade, I was able to successfully deploy the policy's to most of them, but two of them&lt;/P&gt;&lt;P&gt;return an error and wouldn't go through with the deploy.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is the output I can see in the detail deploy output.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;FMC &amp;gt;&amp;gt; failover mac address GigabitEthernet1/1 0E12.0105.0001 0E12.0105.0002&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;FRGRFW1a &amp;gt;&amp;gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;error&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;: ERROR: Configure nameif for the interface GigabitEthernet1/1 to configure failover mac&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Config Error -- failover mac address GigabitEthernet1/1 0E12.0105.0001 0E12.0105.0002&lt;/SPAN&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;U&gt;Other logs&lt;/U&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Lina config ROLLBACK failure log&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Lina configuration application failure. Error in lina apply phase due to Config Error response from LINA&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I suspect I need to create a TAC case, but I am curious if someone seen this error before?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;/Chess&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 12 Oct 2020 09:50:30 GMT</pubDate>
    <dc:creator>Chess Norris</dc:creator>
    <dc:date>2020-10-12T09:50:30Z</dc:date>
    <item>
      <title>FTD deployment issues after upgrading to 6.6</title>
      <link>https://community.cisco.com/t5/network-security/ftd-deployment-issues-after-upgrading-to-6-6/m-p/4165041#M1074629</link>
      <description>&lt;P&gt;I am in the process of upgrading a bunch of ASA 5508-X from FTD version 6.3 to 6.6.&lt;/P&gt;&lt;P&gt;They are all setup in failover pairs with a couple of sub interface.&lt;/P&gt;&lt;P&gt;All the configuration is basically the same except for the interface address configuration and ACPs.&amp;nbsp;&lt;/P&gt;&lt;P&gt;After the upgrade, I was able to successfully deploy the policy's to most of them, but two of them&lt;/P&gt;&lt;P&gt;return an error and wouldn't go through with the deploy.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is the output I can see in the detail deploy output.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;FMC &amp;gt;&amp;gt; failover mac address GigabitEthernet1/1 0E12.0105.0001 0E12.0105.0002&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;FRGRFW1a &amp;gt;&amp;gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;error&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;: ERROR: Configure nameif for the interface GigabitEthernet1/1 to configure failover mac&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Config Error -- failover mac address GigabitEthernet1/1 0E12.0105.0001 0E12.0105.0002&lt;/SPAN&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;U&gt;Other logs&lt;/U&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Lina config ROLLBACK failure log&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Lina configuration application failure. Error in lina apply phase due to Config Error response from LINA&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I suspect I need to create a TAC case, but I am curious if someone seen this error before?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;/Chess&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 12 Oct 2020 09:50:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-deployment-issues-after-upgrading-to-6-6/m-p/4165041#M1074629</guid>
      <dc:creator>Chess Norris</dc:creator>
      <dc:date>2020-10-12T09:50:30Z</dc:date>
    </item>
    <item>
      <title>Re: FTD deployment issues after upgrading to 6.6</title>
      <link>https://community.cisco.com/t5/network-security/ftd-deployment-issues-after-upgrading-to-6-6/m-p/4165047#M1074632</link>
      <description>&lt;P&gt;Looks like you might be hitting this bug (even though this bug states 6.5.0):&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Symptom:&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Firepower Management Center (FMC) deployment failure to managed devices recently upgraded to 6.5.0.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;FMC transcript shows the following error.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;FMC &amp;gt;&amp;gt; failover mac address Ethernet1/4 1234.1234.aabb 1234.1234.bbaa&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;FTDHA &amp;gt;&amp;gt; error : ERROR: Configure nameif for the interface Ethernet1/4 to configure failover mac&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Config Error -- failover mac address Ethernet1/4 1234.1234.aabb 1234.1234.bbaa&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The /nfw/var/log/ASAConsole.log file shows the following errors when the FTD boots up with the new version.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;2019-10-07 15:26:17 ERROR: Failover mac address cannot be configured when failoveris disabled&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2019-10-07 15:26:17 *** Output from config line 1218, "failover mac address Eth..."&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Conditions:&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;FTD on HA&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;FTD version 6.5.0&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;To have Interfaces MAC addresses configured for interfaces without a name.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Workaround:&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Removing the MAC addresses for interfaces that aren't named allows the deployments to complete. This workaround doesn't represent any behavior change as unnamed interfaces can't be used until a name is given to them.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvr57984/?rfs=iqvred" target="_blank"&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvr57984/?rfs=iqvred&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 12 Oct 2020 10:06:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-deployment-issues-after-upgrading-to-6-6/m-p/4165047#M1074632</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2020-10-12T10:06:20Z</dc:date>
    </item>
    <item>
      <title>Re: FTD deployment issues after upgrading to 6.6</title>
      <link>https://community.cisco.com/t5/network-security/ftd-deployment-issues-after-upgrading-to-6-6/m-p/4165064#M1074634</link>
      <description>&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I did remove the MAC and had no problem deploying. After the deploy was finished, I noticed that I didn't even had the choice anymore to select the physical interface. I will set up failover MAC addresses on the sub-interfaces instead.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;/Chess&lt;/P&gt;</description>
      <pubDate>Mon, 12 Oct 2020 10:31:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-deployment-issues-after-upgrading-to-6-6/m-p/4165064#M1074634</guid>
      <dc:creator>Chess Norris</dc:creator>
      <dc:date>2020-10-12T10:31:05Z</dc:date>
    </item>
  </channel>
</rss>

