<?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: Dual ISP failover on ASA in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/dual-isp-failover-on-asa/m-p/3701943#M12464</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Routing is done before NAT. What I have done is created the below object NAT statement, change names to suit yours. Note both guest and corporate would NAT to the outside interface IP address.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;object network NAT-BACKUP-ISP&lt;BR /&gt;subnet x.x.x.x x.x.x.x&lt;BR /&gt;&amp;nbsp;nat (inside,backup-isp) dynamic interface&lt;BR /&gt;object network NAT-PRIMARY-ISP&lt;BR /&gt;subnet x.x.x.x x.x.x.x&lt;BR /&gt;&amp;nbsp;nat (inside,primary-isp) dynamic interface&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If the subnets are vastly different between corporate and guest i.e. can't summarize. Duplicate the above i.e.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For Guest&lt;/P&gt;
&lt;P&gt;object network NAT-GUEST-BACKUP-ISP&lt;BR /&gt;subnet x.x.x.x x.x.x.x&lt;BR /&gt;&amp;nbsp;nat (guest,backup-isp) dynamic interface&lt;BR /&gt;object network NAT-GUEST-PRIMARY-ISP&lt;BR /&gt;subnet x.x.x.x x.x.x.x&lt;BR /&gt;&amp;nbsp;nat (guest,primary-isp) dynamic interface&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For Corporate&lt;/P&gt;
&lt;P&gt;object network NAT-CORPORATE-BACKUP-ISP&lt;BR /&gt;subnet x.x.x.x x.x.x.x&lt;BR /&gt;&amp;nbsp;nat (inside,backup-isp) dynamic interface&lt;BR /&gt;object network NAT-CORPORATE-PRIMARY-ISP&lt;BR /&gt;subnet x.x.x.x x.x.x.x&lt;/P&gt;
&lt;P&gt;&amp;nbsp;nat (inside,backup-isp) dynamic interface&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You cold probably get away with some manual NAT if the above doesn't suit, as its less configuration.&lt;/P&gt;
&lt;P&gt;nat (any,primary-isp) after-auto source dynamic any interface &lt;/P&gt;
&lt;P&gt;nat (any,backup-isp) after-auto source dynamic any interface&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Routing will determine which interface do send the traffic, then NAT will occur. You would need a mix of SLA and PBR to achieve what you want too. &lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Joel&lt;BR /&gt;&lt;BR /&gt;&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>Thu, 06 Sep 2018 11:11:59 GMT</pubDate>
    <dc:creator>Joel</dc:creator>
    <dc:date>2018-09-06T11:11:59Z</dc:date>
    <item>
      <title>Dual ISP failover on ASA</title>
      <link>https://community.cisco.com/t5/network-security/dual-isp-failover-on-asa/m-p/3700871#M12461</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have a client that has 2 ISPs and would like to use ISP1 for employees and ISP2 for guests.&amp;nbsp; At the same time, he would like to have internet failover for both employees and guests.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So, under normal conditions, employee's subnet should use ISP1 and guest's subnet should use ISP2.&amp;nbsp; In the case of a services interruption by ISP1, the employee's subnet will need to use ISP2.&amp;nbsp; In the case of a service interruption ISP2, the guest's subnet will need to use ISP1.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Below is the current design:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Employees&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; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;ISP1&lt;/P&gt;
&lt;P&gt;&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; &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;
&lt;P&gt;&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; &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;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;lt;ASA&amp;gt;=====&amp;lt;Edge Router&amp;gt;&lt;/P&gt;
&lt;P&gt;&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; &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;
&lt;P&gt;&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; &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;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;Guests&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; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; ISP2&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm wondering if there is a way to use tacking to tell the ASA to which public IP address it should translate, ISP1 or ISP2?&amp;nbsp; How could I be able to achieve these requirements?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any help will be greatly appreciated!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 16:11:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dual-isp-failover-on-asa/m-p/3700871#M12461</guid>
      <dc:creator>lukecr-01</dc:creator>
      <dc:date>2020-02-21T16:11:50Z</dc:date>
    </item>
    <item>
      <title>Re: Dual ISP failover on ASA</title>
      <link>https://community.cisco.com/t5/network-security/dual-isp-failover-on-asa/m-p/3700900#M12462</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you are running one of the supported versions i.e. 9.4.x and above, you can use PBR feature to route the traffic based on source subnet/ip.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/asa/asa94/config-guides/cli/general/asa-94-general-config/route-policy-based.pdf" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/asa/asa94/config-guides/cli/general/asa-94-general-config/route-policy-based.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For your second condition for ISP interruption, you can use the sla tracking option which is again discussed in the document. Basically, it means ASA is going to track the particular ISP before sending the packets over. Multiple "set ip next-hop verify-availability" commands can be added. Please test it out before rolling in production, if its not currently.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;AJ&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Sep 2018 03:47:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dual-isp-failover-on-asa/m-p/3700900#M12462</guid>
      <dc:creator>Ajay Saini</dc:creator>
      <dc:date>2018-09-05T03:47:46Z</dc:date>
    </item>
    <item>
      <title>Re: Dual ISP failover on ASA</title>
      <link>https://community.cisco.com/t5/network-security/dual-isp-failover-on-asa/m-p/3701329#M12463</link>
      <description>&lt;P&gt;Hi AJ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for your quick response.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The part that I'm having a hard time wrapping my head around is NAT.&amp;nbsp; Under normal conditions the employee's subnet would need to be translated to ISP1 (AT&amp;amp;T) public IP address, and the guest's subnet to ISP2 (Cox) public IP.&amp;nbsp; If either ISP fails, let's say ISP1, the employee's subnet then needs to get translated to ISP2 public address.&amp;nbsp; How is the NATing handled when either ISP fails?&amp;nbsp; If inside traffic is not translated to the public IP address of the ISP that is still operational, packets will be dropped by the ISP.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The current design the client has in place does not provide failover.&amp;nbsp; It simply routes guest traffic though ISP2.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Attached is a network diagram for lab testing purposes.&amp;nbsp; So the IP addresses are different than the real ones.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Again, I really appreciate the help!&lt;/P&gt;</description>
      <pubDate>Wed, 05 Sep 2018 16:01:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dual-isp-failover-on-asa/m-p/3701329#M12463</guid>
      <dc:creator>lukecr-01</dc:creator>
      <dc:date>2018-09-05T16:01:58Z</dc:date>
    </item>
    <item>
      <title>Re: Dual ISP failover on ASA</title>
      <link>https://community.cisco.com/t5/network-security/dual-isp-failover-on-asa/m-p/3701943#M12464</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Routing is done before NAT. What I have done is created the below object NAT statement, change names to suit yours. Note both guest and corporate would NAT to the outside interface IP address.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;object network NAT-BACKUP-ISP&lt;BR /&gt;subnet x.x.x.x x.x.x.x&lt;BR /&gt;&amp;nbsp;nat (inside,backup-isp) dynamic interface&lt;BR /&gt;object network NAT-PRIMARY-ISP&lt;BR /&gt;subnet x.x.x.x x.x.x.x&lt;BR /&gt;&amp;nbsp;nat (inside,primary-isp) dynamic interface&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If the subnets are vastly different between corporate and guest i.e. can't summarize. Duplicate the above i.e.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For Guest&lt;/P&gt;
&lt;P&gt;object network NAT-GUEST-BACKUP-ISP&lt;BR /&gt;subnet x.x.x.x x.x.x.x&lt;BR /&gt;&amp;nbsp;nat (guest,backup-isp) dynamic interface&lt;BR /&gt;object network NAT-GUEST-PRIMARY-ISP&lt;BR /&gt;subnet x.x.x.x x.x.x.x&lt;BR /&gt;&amp;nbsp;nat (guest,primary-isp) dynamic interface&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For Corporate&lt;/P&gt;
&lt;P&gt;object network NAT-CORPORATE-BACKUP-ISP&lt;BR /&gt;subnet x.x.x.x x.x.x.x&lt;BR /&gt;&amp;nbsp;nat (inside,backup-isp) dynamic interface&lt;BR /&gt;object network NAT-CORPORATE-PRIMARY-ISP&lt;BR /&gt;subnet x.x.x.x x.x.x.x&lt;/P&gt;
&lt;P&gt;&amp;nbsp;nat (inside,backup-isp) dynamic interface&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You cold probably get away with some manual NAT if the above doesn't suit, as its less configuration.&lt;/P&gt;
&lt;P&gt;nat (any,primary-isp) after-auto source dynamic any interface &lt;/P&gt;
&lt;P&gt;nat (any,backup-isp) after-auto source dynamic any interface&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Routing will determine which interface do send the traffic, then NAT will occur. You would need a mix of SLA and PBR to achieve what you want too. &lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Joel&lt;BR /&gt;&lt;BR /&gt;&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>Thu, 06 Sep 2018 11:11:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dual-isp-failover-on-asa/m-p/3701943#M12464</guid>
      <dc:creator>Joel</dc:creator>
      <dc:date>2018-09-06T11:11:59Z</dc:date>
    </item>
  </channel>
</rss>

