<?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 A few days turned into 9 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/dynamic-nat-rules-for-backup-isp-circuit/m-p/2431200#M268909</link>
    <description>&lt;P&gt;A few days turned into 9 months but got there in the end. &amp;nbsp;&lt;/P&gt;&lt;P&gt;WAN failover (when using multiple NAT rules and VPN Tunnels) only works properly on ASA5512x and higher when using version 9.2(1) that supports event manager. &amp;nbsp;configure a tracked route, SLA and Event manager actions that remove and add config when triggered.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Dentist55&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 10 Dec 2014 07:15:32 GMT</pubDate>
    <dc:creator>Paul Monteith</dc:creator>
    <dc:date>2014-12-10T07:15:32Z</dc:date>
    <item>
      <title>Dynamic NAT rules for backup ISP circuit</title>
      <link>https://community.cisco.com/t5/network-security/dynamic-nat-rules-for-backup-isp-circuit/m-p/2431197#M268898</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need to configure a backup circuit using IP SLA, routes with metrics, static nat rules for VPNS and so on, and that all makes perfect sense.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am however stuck on how I setup the dynamic NAT rules so that traffic from internal to Internet is natted to the backup ISP public IP addresses in the event of primary circuit outage.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The dynamic NAT rules are as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;object network XXX-CORP&lt;/P&gt;&lt;P&gt; nat (CORP_RANGE,PRIMARY_ISP) dynamic 8x.2xx.x.2xx&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;object network XXX-WIFI&lt;/P&gt;&lt;P&gt; nat (WIFI_RANGE,PRIMARY_ISP) dynamic 8x.2xx.x.2xx&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;object network XXX-PROD&lt;/P&gt;&lt;P&gt; nat (PROD_RANGE,PRIMARY_ISP) dynamic 8x.2xx.x.2xx&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;object network XXX-DMZ&lt;/P&gt;&lt;P&gt; nat (DMZ_RANGE,PRIMARY_ISP) dynamic 8x.2xx.x.2xx&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;object network XXX-OPS&lt;/P&gt;&lt;P&gt; nat (OPS_RANGE,PRIMARY_ISP) dynamic 8x.2xx.x.2xx&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am guessing there is a way to add something like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;object network XXX-OPS &lt;/P&gt;&lt;P&gt; nat (OPS_RANGE,PRIMARY_ISP) dynamic 8x.2xx.x.2xx&lt;/P&gt;&lt;P&gt; nat (OPS_RANGE,SECONDARY_ISP) dynamic 19x.1xx.3x.1xx secondary&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance, and of course I will provide more info if required.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dentist&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 03:51:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dynamic-nat-rules-for-backup-isp-circuit/m-p/2431197#M268898</guid>
      <dc:creator>Paul Monteith</dc:creator>
      <dc:date>2019-03-12T03:51:42Z</dc:date>
    </item>
    <item>
      <title>Dynamic NAT rules for backup ISP circuit</title>
      <link>https://community.cisco.com/t5/network-security/dynamic-nat-rules-for-backup-isp-circuit/m-p/2431198#M268901</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You essentially just add a new Dynamic PAT rule for each of the required local network towards the second ISP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Routing and SLA configurations handle which interface and which Dynamic PAT is used.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Notice that you can not configure 2 &lt;STRONG&gt;"nat"&lt;/STRONG&gt; configurations under a single &lt;STRONG&gt;"object"&lt;/STRONG&gt;. You will simply need to make 2 Dynamic PAT configurations for each of your internal networks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can naturally configure a single Dynamic PAT rule per ISP per ALL internal networks with the below configuration format&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;object-group network ISP1-PAT-SOURCE&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; network-object &lt;LAN1&gt; &lt;MASK&gt;&lt;/MASK&gt;&lt;/LAN1&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; network-object &lt;LAN2&gt; &lt;MASK&gt;&lt;/MASK&gt;&lt;/LAN2&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; network-object &lt;DMZ1&gt; &lt;MASK&gt;&lt;/MASK&gt;&lt;/DMZ1&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;nat (any,isp1) after-auto source dynamic ISP1-PAT-SOURCE interface&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;object-group network ISP2-PAT-SOURCE&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; network-object &lt;LAN1&gt; &lt;MASK&gt;&lt;/MASK&gt;&lt;/LAN1&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; network-object &lt;LAN2&gt; &lt;MASK&gt;&lt;/MASK&gt;&lt;/LAN2&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; network-object &lt;DMZ1&gt; &lt;MASK&gt;&lt;/MASK&gt;&lt;/DMZ1&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;nat (any,isp2) after-auto source dynamic ISP2-PAT-SOURCE interface&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So looking at the above configuraitons you could simply configure all the internal networks under an &lt;STRONG&gt;"object-group"&lt;/STRONG&gt; and then use that &lt;STRONG&gt;"object-group"&lt;/STRONG&gt; in a &lt;STRONG&gt;"nat"&lt;/STRONG&gt; configurations to do Dynamic PAT for all your internal networks towards one ISP. You could create the same type of configurations for the other ISP also.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And as I said before you can also simply configure Dynamic PAT with Auto NAT / Network Object NAT for each of the internal networks separately&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;object network WIFI-ISP2-PAT&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; subnet &lt;WIFI network=""&gt; &lt;MASK&gt;&lt;/MASK&gt;&lt;/WIFI&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; nat (WIFI_RANGE,SECONDARY_ISP) dynamic interface (or IP)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know how it goes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 02 Mar 2014 17:05:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dynamic-nat-rules-for-backup-isp-circuit/m-p/2431198#M268901</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2014-03-02T17:05:27Z</dc:date>
    </item>
    <item>
      <title>Dynamic NAT rules for backup ISP circuit</title>
      <link>https://community.cisco.com/t5/network-security/dynamic-nat-rules-for-backup-isp-circuit/m-p/2431199#M268905</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jouni&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your answer, I had come to a similar conclusion with the after-auto after reading another of your threads but as yet I have not tested it.&amp;nbsp; I will do in the next few days and will then update you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Paul&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Mar 2014 17:02:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dynamic-nat-rules-for-backup-isp-circuit/m-p/2431199#M268905</guid>
      <dc:creator>Paul Monteith</dc:creator>
      <dc:date>2014-03-03T17:02:26Z</dc:date>
    </item>
    <item>
      <title>A few days turned into 9</title>
      <link>https://community.cisco.com/t5/network-security/dynamic-nat-rules-for-backup-isp-circuit/m-p/2431200#M268909</link>
      <description>&lt;P&gt;A few days turned into 9 months but got there in the end. &amp;nbsp;&lt;/P&gt;&lt;P&gt;WAN failover (when using multiple NAT rules and VPN Tunnels) only works properly on ASA5512x and higher when using version 9.2(1) that supports event manager. &amp;nbsp;configure a tracked route, SLA and Event manager actions that remove and add config when triggered.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Dentist55&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 10 Dec 2014 07:15:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dynamic-nat-rules-for-backup-isp-circuit/m-p/2431200#M268909</guid>
      <dc:creator>Paul Monteith</dc:creator>
      <dc:date>2014-12-10T07:15:32Z</dc:date>
    </item>
  </channel>
</rss>

