<?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 Firepower FTD HA issues in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firepower-ftd-ha-issues/m-p/4791659#M1098581</link>
    <description>&lt;P&gt;I&amp;nbsp; Have 2 ftds in High availability Managed by FMC.&amp;nbsp;&lt;/P&gt;&lt;P&gt;PROBLEM When there is flap on the network. Both FTDs become the active (FTD 1- Active&amp;nbsp; and FTD 2 - Active) INSTEAD of being FTDs being in FTD Active-Standby (FTD 1 -Active and FTD 2 - Standby)&amp;nbsp; and no services pass through the FTDs , until you login and force one FTD to standby Manually. How can we monitor resolve . Or how better how automate&amp;nbsp; and monitor this process. Firepower 2130 series ver 7.04.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 10 Mar 2023 20:17:20 GMT</pubDate>
    <dc:creator>cm</dc:creator>
    <dc:date>2023-03-10T20:17:20Z</dc:date>
    <item>
      <title>Firepower FTD HA issues</title>
      <link>https://community.cisco.com/t5/network-security/firepower-ftd-ha-issues/m-p/4791659#M1098581</link>
      <description>&lt;P&gt;I&amp;nbsp; Have 2 ftds in High availability Managed by FMC.&amp;nbsp;&lt;/P&gt;&lt;P&gt;PROBLEM When there is flap on the network. Both FTDs become the active (FTD 1- Active&amp;nbsp; and FTD 2 - Active) INSTEAD of being FTDs being in FTD Active-Standby (FTD 1 -Active and FTD 2 - Standby)&amp;nbsp; and no services pass through the FTDs , until you login and force one FTD to standby Manually. How can we monitor resolve . Or how better how automate&amp;nbsp; and monitor this process. Firepower 2130 series ver 7.04.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Mar 2023 20:17:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-ftd-ha-issues/m-p/4791659#M1098581</guid>
      <dc:creator>cm</dc:creator>
      <dc:date>2023-03-10T20:17:20Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower FTD HA issues</title>
      <link>https://community.cisco.com/t5/network-security/firepower-ftd-ha-issues/m-p/4791660#M1098582</link>
      <description>&lt;P&gt;assign manual MAC to active and standby FTD and check the result.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/security/firepower-management-center/212699-configure-ftd-high-availability-on-firep.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/security/firepower-management-center/212699-configure-ftd-high-availability-on-firep.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Mar 2023 20:22:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-ftd-ha-issues/m-p/4791660#M1098582</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-03-10T20:22:26Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower FTD HA issues</title>
      <link>https://community.cisco.com/t5/network-security/firepower-ftd-ha-issues/m-p/4791810#M1098592</link>
      <description>&lt;P&gt;First you need check HA connectivity and parameters,&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 11 Mar 2023 09:49:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-ftd-ha-issues/m-p/4791810#M1098592</guid>
      <dc:creator>Mohammad Ahmadvand</dc:creator>
      <dc:date>2023-03-11T09:49:45Z</dc:date>
    </item>
  </channel>
</rss>

