<?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: Multiple connections to ONE ISP in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/multiple-connections-to-one-isp/m-p/1359746#M748362</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;Should not be any problem, but you can track an IP avaiable to that path (instead of tracking the default gateway).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For instance, let's say you create a route:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;route outside 4.2.2.1 255.255.255.255 gateway1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can track 4.2.2.1 via interface outside (since that specific IP is always going to be reachable via that interface).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if the problem persists.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Federico.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 07 Mar 2010 16:41:35 GMT</pubDate>
    <dc:creator>Federico Coto Fajardo</dc:creator>
    <dc:date>2010-03-07T16:41:35Z</dc:date>
    <item>
      <title>Multiple connections to ONE ISP</title>
      <link>https://community.cisco.com/t5/network-security/multiple-connections-to-one-isp/m-p/1359745#M748348</link>
      <description>&lt;P&gt;I have two connections to one ISP (one is over Radio channel the other is on-ground) who provides me with pool of public IP addresses. On my border routers (3825) I have BGP which announces this pool of addresses via one or another router (depending which channel is available. On-ground&amp;nbsp; has higher priority.) On ASA I configured SLA:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #808080;"&gt;route outside 0.0.0.0 0.0.0.0 x.x.x.3 1 track 1&lt;BR /&gt;route outside 0.0.0.0 0.0.0.0 x.x.x.4 250&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #008080;"&gt;&lt;SPAN style="color: #808080;"&gt;sla monitor 10&lt;BR /&gt;type echo protocol ipIcmpEcho &lt;EM&gt;[on-ground default-gateway]&lt;/EM&gt; interface outside&lt;BR /&gt;num-packets 3&lt;BR /&gt;timeout 1000&lt;BR /&gt;frequency 3&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #808080;"&gt;sla monitor schedule 10 life forever start-time now&lt;/SPAN&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000;"&gt;I have tested the SLA by shutting down the primary (on-ground) Internet channel. Everything worked fine: the default gateway switched to the Radio channel and back when I turned the on-ground channel back on.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000;"&gt;&lt;STRONG style="color: #ff0000; "&gt;The problem is:&lt;/STRONG&gt; After some time (5 - 10 hours) ASA looses the default gateway and all services behind ASA become unavailable. After I reaply the SLA configuration provided above everything work fine for the next 5 - 10 hours and then it looses the default-gateway again.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #ff0000;"&gt;&lt;STRONG&gt;Question: &lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;SPAN style="color: #000000;"&gt;Does SLA on ASA work correct if the next hop for both DG are in one subnet. Technically there should be no problem but In all examples I have seen, never have I met that situation (next hops were always on different subnets)?&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;If not first. What could be the problem?&lt;/LI&gt;&lt;LI&gt;Are there any better ways to provide switching between two Internet channels in my situation?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help is appreciated!&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 17:18:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/multiple-connections-to-one-isp/m-p/1359745#M748348</guid>
      <dc:creator>CCOintIPS</dc:creator>
      <dc:date>2019-03-11T17:18:17Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple connections to ONE ISP</title>
      <link>https://community.cisco.com/t5/network-security/multiple-connections-to-one-isp/m-p/1359746#M748362</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;Should not be any problem, but you can track an IP avaiable to that path (instead of tracking the default gateway).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For instance, let's say you create a route:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;route outside 4.2.2.1 255.255.255.255 gateway1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can track 4.2.2.1 via interface outside (since that specific IP is always going to be reachable via that interface).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if the problem persists.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Federico.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 07 Mar 2010 16:41:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/multiple-connections-to-one-isp/m-p/1359746#M748362</guid>
      <dc:creator>Federico Coto Fajardo</dc:creator>
      <dc:date>2010-03-07T16:41:35Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple connections to ONE ISP</title>
      <link>https://community.cisco.com/t5/network-security/multiple-connections-to-one-isp/m-p/1359747#M748376</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for your suggestion! I`ll try applying this configuration on Friday evening and let you know wether it helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Mar 2010 06:46:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/multiple-connections-to-one-isp/m-p/1359747#M748376</guid>
      <dc:creator>CCOintIPS</dc:creator>
      <dc:date>2010-03-09T06:46:07Z</dc:date>
    </item>
  </channel>
</rss>

