<?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: Inbound ASA Traffic Failover in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/inbound-asa-traffic-failover/m-p/1458889#M634002</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just a wild configuration Idea (did not test it and i´m not sure if this is realy working)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You could provide for your VPN partner the second IP from your backup ISP and based on the VPN Keepalive settings the tunnel would be rebuild right after your partner router detected that the VPN line is down. Depending on the routers of your partners you could be able to tune this a bit by using SLAs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But as mentioned not sure if this realy works (fast)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers Michael&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 02 Jul 2010 20:21:30 GMT</pubDate>
    <dc:creator>Michael Dombek</dc:creator>
    <dc:date>2010-07-02T20:21:30Z</dc:date>
    <item>
      <title>Inbound ASA Traffic Failover</title>
      <link>https://community.cisco.com/t5/network-security/inbound-asa-traffic-failover/m-p/1458888#M634001</link>
      <description>&lt;P&gt;Our ASA5510 is dual-homed and directly connected to provider-controlled routers.&amp;nbsp; The primary ISP is 10 Mb fiber and the backup is a T3.&amp;nbsp; We've configured the outbound failover with SLA and that works fine.&amp;nbsp; What I'd like to know is how to ensure that our VPN clients (we have no access to their routers) can find our secondary ISP link when our primary link fails.&amp;nbsp; DNS is too slow and, therefore, unacceptable.&amp;nbsp; I'd considered pre-configuring a router with OSPF and providing it to them, but are there other options?&amp;nbsp; Thanx!&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 18:07:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inbound-asa-traffic-failover/m-p/1458888#M634001</guid>
      <dc:creator>pootboy69</dc:creator>
      <dc:date>2019-03-11T18:07:10Z</dc:date>
    </item>
    <item>
      <title>Re: Inbound ASA Traffic Failover</title>
      <link>https://community.cisco.com/t5/network-security/inbound-asa-traffic-failover/m-p/1458889#M634002</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just a wild configuration Idea (did not test it and i´m not sure if this is realy working)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You could provide for your VPN partner the second IP from your backup ISP and based on the VPN Keepalive settings the tunnel would be rebuild right after your partner router detected that the VPN line is down. Depending on the routers of your partners you could be able to tune this a bit by using SLAs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But as mentioned not sure if this realy works (fast)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers Michael&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Jul 2010 20:21:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inbound-asa-traffic-failover/m-p/1458889#M634002</guid>
      <dc:creator>Michael Dombek</dc:creator>
      <dc:date>2010-07-02T20:21:30Z</dc:date>
    </item>
  </channel>
</rss>

