<?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: FTD Failover Issue post Version Upgrade in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ftd-failover-issue-post-version-upgrade/m-p/4193938#M1076442</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/890979"&gt;@NeWGuy1109&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Are you able to push policy to both FTD's?&lt;/P&gt;
&lt;P&gt;Please provide the output of "show failover"&lt;/P&gt;</description>
    <pubDate>Sat, 05 Dec 2020 15:22:36 GMT</pubDate>
    <dc:creator>Rob Ingram</dc:creator>
    <dc:date>2020-12-05T15:22:36Z</dc:date>
    <item>
      <title>FTD Failover Issue post Version Upgrade</title>
      <link>https://community.cisco.com/t5/network-security/ftd-failover-issue-post-version-upgrade/m-p/4193914#M1076441</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I ran an upgrade on my FTDs which are in HA(Active/Standby) from 6.4.0 to 6.6.1 version via FMC.. the entire procedure was completed successfully however both the members became active/active once the upgrade finished and the traffic is now fluctuating between the two firewalls.. this is causing loss of service as these are supposed to work in Active/Standby Mode.. the failover link is up and reachable from both the Firewalls and manual demotion on any member is also not working..it is giving the message " peer link is not active and switch is not possible"&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please help here.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sat, 05 Dec 2020 14:48:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-failover-issue-post-version-upgrade/m-p/4193914#M1076441</guid>
      <dc:creator>NeWGuy1109</dc:creator>
      <dc:date>2020-12-05T14:48:44Z</dc:date>
    </item>
    <item>
      <title>Re: FTD Failover Issue post Version Upgrade</title>
      <link>https://community.cisco.com/t5/network-security/ftd-failover-issue-post-version-upgrade/m-p/4193938#M1076442</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/890979"&gt;@NeWGuy1109&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Are you able to push policy to both FTD's?&lt;/P&gt;
&lt;P&gt;Please provide the output of "show failover"&lt;/P&gt;</description>
      <pubDate>Sat, 05 Dec 2020 15:22:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-failover-issue-post-version-upgrade/m-p/4193938#M1076442</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2020-12-05T15:22:36Z</dc:date>
    </item>
    <item>
      <title>Re: FTD Failover Issue post Version Upgrade</title>
      <link>https://community.cisco.com/t5/network-security/ftd-failover-issue-post-version-upgrade/m-p/4194030#M1076447</link>
      <description>&lt;P&gt;There is something gone wrong, check the HA Link, Looks like in the network, they are not able to see each other that is the reason it becomes active/active - so check the HA/synch Link between FTD- is this appliance what model or VM?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For now to make it stable - shutdown ( Standby one originally configured)&amp;nbsp; one of them, and investigate the if any physical and failover history show you more information.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 05 Dec 2020 20:33:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-failover-issue-post-version-upgrade/m-p/4194030#M1076447</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2020-12-05T20:33:06Z</dc:date>
    </item>
    <item>
      <title>Re: FTD Failover Issue post Version Upgrade</title>
      <link>https://community.cisco.com/t5/network-security/ftd-failover-issue-post-version-upgrade/m-p/4194082#M1076451</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;It seems that the upgrade broke the failover config. If you are able to&lt;BR /&gt;ping the failover interface from each firewall then your failover config is&lt;BR /&gt;broken.&lt;BR /&gt;&lt;BR /&gt;Next steps for easy service restoration:&lt;BR /&gt;&lt;BR /&gt;1. On one of the units, shutdown all interfaces from the connected&lt;BR /&gt;switches except the MGMT interface and the failover interface (or easier&lt;BR /&gt;unplug the cables from the FTD if you have physical access).&lt;BR /&gt;2. Take device backup for the active unit (managed backup)&lt;BR /&gt;3. Delete both units from FMC (this won't cause any service interruption).&lt;BR /&gt;4. Schedule a downtime to wipe the active unit and restore the backup using&lt;BR /&gt;FMC (this will take around 30 mins to restore the config assuming that you&lt;BR /&gt;completed the image upgrade already).&lt;BR /&gt;5. Wipe the secondary unit and add it to FMC.&lt;BR /&gt;6. Create an HA to sync the config from active to standby unit&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;If you manage to restore the peer link, then it g8 otherwise this what you&lt;BR /&gt;need to do.&lt;BR /&gt;&lt;BR /&gt;On a side note, 6.4.0.x is the worst image I used and I always recommend to&lt;BR /&gt;jump away from it before starting any config.&lt;BR /&gt;&lt;BR /&gt;Here is the link for backup and restore.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/firepower/630/configuration/guide/fpmc-config-guide-v63/backup_and_restore.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/firepower/630/configuration/guide/fpmc-config-guide-v63/backup_and_restore.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;***** please remember to rate useful posts&lt;BR /&gt;</description>
      <pubDate>Sun, 06 Dec 2020 07:45:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-failover-issue-post-version-upgrade/m-p/4194082#M1076451</guid>
      <dc:creator>Mohammed al Baqari</dc:creator>
      <dc:date>2020-12-06T07:45:43Z</dc:date>
    </item>
    <item>
      <title>Re: FTD Failover Issue post Version Upgrade</title>
      <link>https://community.cisco.com/t5/network-security/ftd-failover-issue-post-version-upgrade/m-p/4260200#M1076751</link>
      <description>&lt;P&gt;Had to involve TAC for it.. they are still looking into it.&lt;/P&gt;&lt;P&gt;However, it seems something went wrong during the upgrade itself which is unexplained at this point of time&lt;/P&gt;</description>
      <pubDate>Thu, 17 Dec 2020 16:23:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-failover-issue-post-version-upgrade/m-p/4260200#M1076751</guid>
      <dc:creator>NeWGuy1109</dc:creator>
      <dc:date>2020-12-17T16:23:47Z</dc:date>
    </item>
  </channel>
</rss>

