<?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 ASA 5505 ISP Failover in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-5505-isp-failover/m-p/2192171#M361825</link>
    <description>&lt;P&gt;So we currently have a T1 connection at our location. We were looking to add a high speed cable internet and add an ASA 5505 with Security plus license to do failover between the two. I have found a few examples on how this would work but curious about a couple things.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We would want the Cable to be the primary, T1 as a backup.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Currently the IAD that handles our T1 does dhcp, dns, and NAT.. Who/what would handle these items with the setup above?&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 01:02:10 GMT</pubDate>
    <dc:creator>bwillford</dc:creator>
    <dc:date>2019-03-12T01:02:10Z</dc:date>
    <item>
      <title>ASA 5505 ISP Failover</title>
      <link>https://community.cisco.com/t5/network-security/asa-5505-isp-failover/m-p/2192171#M361825</link>
      <description>&lt;P&gt;So we currently have a T1 connection at our location. We were looking to add a high speed cable internet and add an ASA 5505 with Security plus license to do failover between the two. I have found a few examples on how this would work but curious about a couple things.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We would want the Cable to be the primary, T1 as a backup.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Currently the IAD that handles our T1 does dhcp, dns, and NAT.. Who/what would handle these items with the setup above?&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 01:02:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5505-isp-failover/m-p/2192171#M361825</guid>
      <dc:creator>bwillford</dc:creator>
      <dc:date>2019-03-12T01:02:10Z</dc:date>
    </item>
    <item>
      <title>ASA 5505 ISP Failover</title>
      <link>https://community.cisco.com/t5/network-security/asa-5505-isp-failover/m-p/2192172#M361826</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I this case Nat will be done by your ASA&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;U will DO PBR for Primary / Backup.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ur GW will be UR ASA Inside Interface u will need to change GW in DHCP for all clients.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Feb 2013 20:43:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5505-isp-failover/m-p/2192172#M361826</guid>
      <dc:creator>jawad-mukhtar</dc:creator>
      <dc:date>2013-02-18T20:43:17Z</dc:date>
    </item>
    <item>
      <title>ASA 5505 ISP Failover</title>
      <link>https://community.cisco.com/t5/network-security/asa-5505-isp-failover/m-p/2192173#M361827</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Since the ASA will be replacing the IAD it will have to do all what the IAD was previously doing, that includes DHCP, DNS and NAT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As you might now, after configuring SLA monitoring on the ASA to manage the two lines, you have to make sure that the backup line is ready to take over when the time comes, that means nat translations, routes and access rules have to be in place; at least for a basic setup.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Feb 2013 22:49:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5505-isp-failover/m-p/2192173#M361827</guid>
      <dc:creator>jocamare</dc:creator>
      <dc:date>2013-02-18T22:49:25Z</dc:date>
    </item>
    <item>
      <title>ASA 5505 ISP Failover</title>
      <link>https://community.cisco.com/t5/network-security/asa-5505-isp-failover/m-p/2192174#M361828</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So the ASA has to replace the IAD? the IAD is managed by the ISP I was wanting to put the ASA behind the IAD.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2013 13:34:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5505-isp-failover/m-p/2192174#M361828</guid>
      <dc:creator>bwillford</dc:creator>
      <dc:date>2013-02-19T13:34:19Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 5505 ISP Failover</title>
      <link>https://community.cisco.com/t5/network-security/asa-5505-isp-failover/m-p/2192175#M361829</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ASA doesn't have to replace IAD. ASA can just have one of the default routes pointint to the IAD. &lt;/P&gt;&lt;P&gt;dhcp: ASA can take this role, and if you have some kind of small environment it'll be ok. But, ip-to-mac binding, if you require this function, can't be done on ASA internal dhcp server.&lt;/P&gt;&lt;P&gt;dhs: U can use some public well-known dns-server (say 4.2.2.2) to resolve external names. If it's not sufficient for you, you can install your own dns-server somewhere inside your lan.&lt;/P&gt;&lt;P&gt;nat: for yor t1 line you can leave nat-function on IAD, while for new high-speed link asa will do nat.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2013 16:44:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5505-isp-failover/m-p/2192175#M361829</guid>
      <dc:creator>Andrew Phirsov</dc:creator>
      <dc:date>2013-02-19T16:44:15Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 5505 ISP Failover</title>
      <link>https://community.cisco.com/t5/network-security/asa-5505-isp-failover/m-p/2192176#M361830</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So the IAD stays, and the ASA behind it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If i were you i would ask my ISP to let me configure the ASA with the configuration the IAD had, that way i would save 1 hop, 1 failure point and will have 1 device doing what 2 were previously doing.&lt;/P&gt;&lt;P&gt;If getting rid of the IAD is not an option, i would consider running it on bridge/transparent mode. It will become a L2 hub and let the ASA handle the rest.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2013 17:15:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5505-isp-failover/m-p/2192176#M361830</guid>
      <dc:creator>jocamare</dc:creator>
      <dc:date>2013-02-19T17:15:45Z</dc:date>
    </item>
  </channel>
</rss>

