<?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 EIGRP over Stateful Failover Link in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/eigrp-over-stateful-failover-link/m-p/2308107#M344642</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well then all of the obvious solutions seem to be addressed. TAC time?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 15 Aug 2013 18:49:08 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2013-08-15T18:49:08Z</dc:date>
    <item>
      <title>EIGRP over Stateful Failover Link</title>
      <link>https://community.cisco.com/t5/network-security/eigrp-over-stateful-failover-link/m-p/2308102#M344629</link>
      <description>&lt;P&gt;We have two ASA's in Active/Standby mode.&amp;nbsp; We were using static routing on the ASA to reach the subnets off the inside interface but decided to switch over to EIGRP.&amp;nbsp;&amp;nbsp; I got EIGRP working on the active unit but when I removed the static routes from the firewall we lost connectivity to the standby unit.&amp;nbsp; I added the routes back so that I could access it and I noticed that the EIGRP routes were not being learned by the standby unit.&amp;nbsp; After researching this I found out this is due to us not having a stateful link configured in our failover.&amp;nbsp; After configuring this link the standby unit was now seeing dynamic routes so I again attempted to remove the static routes from the active unit.&amp;nbsp; Once again I lost connection to the standby because once the static was removed the standby did not populate it's routing table with the dynamic equivalent route.&amp;nbsp; Here is the process I had to go through to get it to work:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Add the static route back to the configuration.&lt;/P&gt;&lt;P&gt;2.Remove the stateful failover link&lt;/P&gt;&lt;P&gt;3. Delete the static route.&lt;/P&gt;&lt;P&gt;4. Add the stateful failover liink back.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I did this the dynamic route was in the routing table on the standby.&amp;nbsp; Why does the standby unit not update its routing table properly when a stateful link is configured?&amp;nbsp; If there is another static route we want to remove because of an equivalent dynamic route being in the topology table, we have to first remove the stateful link before we delete it.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 02:26:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/eigrp-over-stateful-failover-link/m-p/2308102#M344629</guid>
      <dc:creator>Mitchell Theriot</dc:creator>
      <dc:date>2019-03-12T02:26:06Z</dc:date>
    </item>
    <item>
      <title>EIGRP over Stateful Failover Link</title>
      <link>https://community.cisco.com/t5/network-security/eigrp-over-stateful-failover-link/m-p/2308103#M344632</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What ASA software version are you running? Stateful failover support for dynamic routing protocols was only introduced as of 8.4(1). (&lt;A href="http://www.cisco.com/en/US/docs/security/asa/roadmap/asa_new_features.html#wp43273"&gt;Release notes&lt;/A&gt;)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Aug 2013 16:46:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/eigrp-over-stateful-failover-link/m-p/2308103#M344632</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2013-08-15T16:46:31Z</dc:date>
    </item>
    <item>
      <title>EIGRP over Stateful Failover Link</title>
      <link>https://community.cisco.com/t5/network-security/eigrp-over-stateful-failover-link/m-p/2308104#M344635</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; We are running version 8.6 (1) 2&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Aug 2013 17:41:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/eigrp-over-stateful-failover-link/m-p/2308104#M344635</guid>
      <dc:creator>Mitchell Theriot</dc:creator>
      <dc:date>2013-08-15T17:41:09Z</dc:date>
    </item>
    <item>
      <title>EIGRP over Stateful Failover Link</title>
      <link>https://community.cisco.com/t5/network-security/eigrp-over-stateful-failover-link/m-p/2308105#M344638</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hmm, 8.6(1) is based off the feature set in 8.4(2) so it should be supported. I don't see any open caveats published in the release notes for later versions that would apply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I didn't ask earlier - are you running a single context?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Aug 2013 17:54:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/eigrp-over-stateful-failover-link/m-p/2308105#M344638</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2013-08-15T17:54:19Z</dc:date>
    </item>
    <item>
      <title>EIGRP over Stateful Failover Link</title>
      <link>https://community.cisco.com/t5/network-security/eigrp-over-stateful-failover-link/m-p/2308106#M344640</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Yes we are running single context mode&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Aug 2013 18:36:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/eigrp-over-stateful-failover-link/m-p/2308106#M344640</guid>
      <dc:creator>Mitchell Theriot</dc:creator>
      <dc:date>2013-08-15T18:36:39Z</dc:date>
    </item>
    <item>
      <title>EIGRP over Stateful Failover Link</title>
      <link>https://community.cisco.com/t5/network-security/eigrp-over-stateful-failover-link/m-p/2308107#M344642</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well then all of the obvious solutions seem to be addressed. TAC time?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Aug 2013 18:49:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/eigrp-over-stateful-failover-link/m-p/2308107#M344642</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2013-08-15T18:49:08Z</dc:date>
    </item>
  </channel>
</rss>

