<?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 losing Static route after failover in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ftd-losing-static-route-after-failover/m-p/5129607#M1113546</link>
    <description>&lt;P&gt;We've just setup 3105s in HA with a FMC&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When we failover the FW, and check the route table we cant see our default route on it. it takes over 20 seconds for the static route to be populated in the routing table.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The outside interface is up and connected, we have performed the failover back and forth multiple times and it exists on the standby as well.&lt;/P&gt;
&lt;P&gt;Anyone able to advise how we can investigate this?&lt;/P&gt;
&lt;P&gt;our FTDs are 7.4.1 and our FMC 7.4.1&lt;/P&gt;
&lt;P&gt;FTDs are connected CBs350 then onto the internet links&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 13 Jun 2024 13:33:28 GMT</pubDate>
    <dc:creator>PacketSpartan</dc:creator>
    <dc:date>2024-06-13T13:33:28Z</dc:date>
    <item>
      <title>FTD losing Static route after failover</title>
      <link>https://community.cisco.com/t5/network-security/ftd-losing-static-route-after-failover/m-p/5129607#M1113546</link>
      <description>&lt;P&gt;We've just setup 3105s in HA with a FMC&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When we failover the FW, and check the route table we cant see our default route on it. it takes over 20 seconds for the static route to be populated in the routing table.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The outside interface is up and connected, we have performed the failover back and forth multiple times and it exists on the standby as well.&lt;/P&gt;
&lt;P&gt;Anyone able to advise how we can investigate this?&lt;/P&gt;
&lt;P&gt;our FTDs are 7.4.1 and our FMC 7.4.1&lt;/P&gt;
&lt;P&gt;FTDs are connected CBs350 then onto the internet links&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jun 2024 13:33:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-losing-static-route-after-failover/m-p/5129607#M1113546</guid>
      <dc:creator>PacketSpartan</dc:creator>
      <dc:date>2024-06-13T13:33:28Z</dc:date>
    </item>
    <item>
      <title>Re: FTD losing Static route after failover</title>
      <link>https://community.cisco.com/t5/network-security/ftd-losing-static-route-after-failover/m-p/5129640#M1113547</link>
      <description>&lt;P&gt;If you use track then route will not add until track be UP&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jun 2024 14:25:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-losing-static-route-after-failover/m-p/5129640#M1113547</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-06-13T14:25:00Z</dc:date>
    </item>
    <item>
      <title>Re: FTD losing Static route after failover</title>
      <link>https://community.cisco.com/t5/network-security/ftd-losing-static-route-after-failover/m-p/5132577#M1113577</link>
      <description>&lt;P&gt;In addition to what &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1065752"&gt;@MHM Cisco World&lt;/a&gt; has said, have you verified that all cabling is exactly the same on both devices (same ports are connected to the network)?&lt;/P&gt;
&lt;P&gt;Also, if you log into the secondary device (while it is the standby) and issue the "show route" command, do you see then route there then?&lt;/P&gt;</description>
      <pubDate>Mon, 17 Jun 2024 13:06:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-losing-static-route-after-failover/m-p/5132577#M1113577</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2024-06-17T13:06:50Z</dc:date>
    </item>
  </channel>
</rss>

