<?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 Route Tracking in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-route-tracking/m-p/1092829#M895618</link>
    <description>&lt;P&gt;Would route tracking work in the following scenario?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DSL and T1 links connected to the same ASA.  The t1 will be used for a site to site VPN tunnel using dynamic routing over the tunnel.  The tunnel should only be used to reach those destination networks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The dsl should be used for all outbound/inbound Internet access.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Should the DSL fail, the T1 will be used for both VPN traffic and general inbound/outbound access.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My thinking was that since a combination of dynamic and static routes were being used and only one static (default) is being tracked, this should work fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any thoughts?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
    <pubDate>Tue, 26 Mar 2019 00:41:09 GMT</pubDate>
    <dc:creator>jason.edelman</dc:creator>
    <dc:date>2019-03-26T00:41:09Z</dc:date>
    <item>
      <title>ASA Route Tracking</title>
      <link>https://community.cisco.com/t5/network-security/asa-route-tracking/m-p/1092829#M895618</link>
      <description>&lt;P&gt;Would route tracking work in the following scenario?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DSL and T1 links connected to the same ASA.  The t1 will be used for a site to site VPN tunnel using dynamic routing over the tunnel.  The tunnel should only be used to reach those destination networks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The dsl should be used for all outbound/inbound Internet access.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Should the DSL fail, the T1 will be used for both VPN traffic and general inbound/outbound access.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My thinking was that since a combination of dynamic and static routes were being used and only one static (default) is being tracked, this should work fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any thoughts?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 26 Mar 2019 00:41:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-route-tracking/m-p/1092829#M895618</guid>
      <dc:creator>jason.edelman</dc:creator>
      <dc:date>2019-03-26T00:41:09Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Route Tracking</title>
      <link>https://community.cisco.com/t5/network-security/asa-route-tracking/m-p/1092830#M895619</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.I feel you can do without route tracking&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.As your static default route would be pointing to DSL as primary route, add one more default route which will point via T1 ,make it as floating static by increasing administrative distance&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH..rate if helpful..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Oct 2008 13:47:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-route-tracking/m-p/1092830#M895619</guid>
      <dc:creator>satish_zanjurne</dc:creator>
      <dc:date>2008-10-01T13:47:38Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Route Tracking</title>
      <link>https://community.cisco.com/t5/network-security/asa-route-tracking/m-p/1092831#M895620</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That wouldn't work.  The ASA would see the DSL being up if the last mile connection into the dsl modem goes bad.  ASA would never switch over to use the T1.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Oct 2008 13:50:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-route-tracking/m-p/1092831#M895620</guid>
      <dc:creator>jason.edelman</dc:creator>
      <dc:date>2008-10-01T13:50:14Z</dc:date>
    </item>
  </channel>
</rss>

