<?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 Ok thanks that makes sense, in Routing and SD-WAN</title>
    <link>https://community.cisco.com/t5/routing-and-sd-wan/route-maps-and-interface-tracking/m-p/2722808#M253739</link>
    <description>&lt;P&gt;Ok thanks that makes sense, provided that I know what the next hop is and hoping that it doesn't change unexpectedly&lt;/P&gt;</description>
    <pubDate>Wed, 07 Oct 2015 11:25:14 GMT</pubDate>
    <dc:creator>NeilGouws</dc:creator>
    <dc:date>2015-10-07T11:25:14Z</dc:date>
    <item>
      <title>Route-Maps and interface Tracking</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/route-maps-and-interface-tracking/m-p/2722800#M253731</link>
      <description>&lt;P&gt;Hoping to find a better solution with the implementation of Route-Maps, any advice will be appreciated&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is the scenario&lt;/P&gt;&lt;P&gt;I am running Cisco 887VAG routers, which gives you an ADSL connection &amp;amp;&amp;nbsp;a&amp;nbsp;Cellular (3G) connection.&lt;/P&gt;&lt;P&gt;In my scenario the ADSL connection is the preferred connection &amp;amp;&amp;nbsp;the 3G is the backup connection.&lt;/P&gt;&lt;P&gt;PBR allows for Office365 traffic to break out "locally" on the above interfaces, while WAN traffic goes over DMVPN tunnels.&lt;/P&gt;&lt;P&gt;There are no default routes.&lt;/P&gt;&lt;P&gt;Both the ADSL and 3G get dynamically assigned IPs by the respective ISPs, based on that, I don't know what the next hop will be.&lt;/P&gt;&lt;P&gt;If i knew what the next hop would be I could do tracking, &amp;amp;&amp;nbsp;based on availiblilty I could set the next hop.&lt;/P&gt;&lt;P&gt;NAT is configured and working, for both the Dialer (ADSL) and Cellular interface&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Because I don't know what the next hop is, I have to set the interface to send traffic to&lt;/P&gt;&lt;P&gt;So here's the other config option :&lt;/P&gt;&lt;P&gt;&lt;EM&gt;!&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;interface Vlan1&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&amp;nbsp;ip policy route-map LOCAL-BREAK-OUT&lt;BR /&gt;!&lt;BR /&gt;route-map LOCAL-BREAK-OUT permit 10&lt;BR /&gt;&amp;nbsp;match ip address O365traffic&lt;BR /&gt;&amp;nbsp;set interface Dialer1&amp;nbsp;Cellular0&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now this is all good &amp;amp;&amp;nbsp;well, it works 100% while the ADSL connection is UP.&lt;/P&gt;&lt;P&gt;in theory, if Dialer1 goes down then the next interface that will be used is Cellular)&lt;/P&gt;&lt;P&gt;1 thing to note, the Dialer interface is Virtual, so even if the ADSL connection goes down, the Dialer interface is still up. So the route-map will continue to try and forward tracking to the Dialer interface, even if the ADSL is down.&lt;/P&gt;&lt;P&gt;I thought about applying tracking to the Dialer interface in the route-map, but for some reason (REALLY CISCO ???) you can't apply tracking when you set the interface (and not the next hop)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So here is what I did to get the router to do what I need it to do.&lt;/P&gt;&lt;P&gt;This is not what I prefer, but it's the only way I could find,&lt;STRONG&gt; if you have any advice I am very open to suggestions&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So below I don't&amp;nbsp;track the interface status, I track the routability of the Dailer interface, this works very well.&lt;/P&gt;&lt;P&gt;With EEM i get the router router to do what I need, but like I said, it's not the way I want to do it.&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;&lt;EM&gt;track 1 interface Dialer1 ip routing&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;!&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;interface Vlan1&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&amp;nbsp;ip policy route-map LOCAL-BREAK-OUT&lt;BR /&gt;!&lt;BR /&gt;route-map LOCAL-BREAK-OUT permit 10&lt;BR /&gt;&amp;nbsp;match ip address O365traffic&lt;BR /&gt;&amp;nbsp;set interface Dialer1&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;!&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;event manager applet Track_Dialer1_Down&lt;BR /&gt;&amp;nbsp;description **--ADSL interface Tracking Down--**&lt;BR /&gt;&amp;nbsp;event track 1 state down&lt;BR /&gt;&amp;nbsp;action 1.0 syslog msg "**--EEM-Track_Dialer1_DOWN---PBR-moved-to-Cellular0--**"&lt;BR /&gt;&amp;nbsp;action 1.1 cli command "enable"&lt;BR /&gt;&amp;nbsp;action 1.2 cli command "configure term"&lt;BR /&gt;&amp;nbsp;action 1.3 cli command "route-map LOCAL-BREAK-OUT permit 10"&lt;BR /&gt;&amp;nbsp;action 1.4 cli command "no set interface Dialer 1"&lt;BR /&gt;&amp;nbsp;action 1.5 cli command "set interface Cellular 0"&lt;BR /&gt;&amp;nbsp;action 1.6&amp;nbsp;cli command "end"&lt;BR /&gt;event manager applet Track_Dialer1_Up&lt;BR /&gt;&amp;nbsp;description **--ADSL interface Tracking Up--**&lt;BR /&gt;&amp;nbsp;event track 1 state up&lt;BR /&gt;&amp;nbsp;action 1.0 syslog msg "**--EEM-Track_Dialer1_UP---PBR-moved-back-to-Dialer1--**"&lt;BR /&gt;&amp;nbsp;action 1.1 cli command "enable"&lt;BR /&gt;&amp;nbsp;action 1.2 cli command "configure term"&lt;BR /&gt;&amp;nbsp;action 1.3 cli command "route-map LOCAL-BREAK-OUT permit 10"&lt;BR /&gt;&amp;nbsp;action 1.4 cli command "no set interface Cellular 0"&lt;BR /&gt;&amp;nbsp;action 1.5 cli command "set interface Dialer 1"&lt;BR /&gt;&amp;nbsp;action 1.6&amp;nbsp;cli command "end"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 05 Mar 2019 10:28:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/route-maps-and-interface-tracking/m-p/2722800#M253731</guid>
      <dc:creator>NeilGouws</dc:creator>
      <dc:date>2019-03-05T10:28:01Z</dc:date>
    </item>
    <item>
      <title>Can you not run a trace from</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/route-maps-and-interface-tracking/m-p/2722801#M253732</link>
      <description>&lt;P&gt;Can you not run a trace from local device to see what the next-hop is then you can use tracking in pbr there ip is unlikely going to be dynamic on there side upstream&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2015 12:22:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/route-maps-and-interface-tracking/m-p/2722801#M253732</guid>
      <dc:creator>Mark Malone</dc:creator>
      <dc:date>2015-10-06T12:22:14Z</dc:date>
    </item>
    <item>
      <title>Hi MarkI will give that a go,</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/route-maps-and-interface-tracking/m-p/2722802#M253733</link>
      <description>&lt;P&gt;Hi Mark&lt;/P&gt;&lt;P&gt;I will give that a go, will test with traces over a few days and see if the IP stays the same&lt;/P&gt;&lt;P&gt;thanks for the advice&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2015 12:35:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/route-maps-and-interface-tracking/m-p/2722802#M253733</guid>
      <dc:creator>NeilGouws</dc:creator>
      <dc:date>2015-10-06T12:35:47Z</dc:date>
    </item>
    <item>
      <title>Another option would be to</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/route-maps-and-interface-tracking/m-p/2722803#M253734</link>
      <description>&lt;P&gt;Another option would be to set&amp;nbsp;to a dummy next-hop instead of the dialer interface.&amp;nbsp;This next hop would point to the dialer interface doing tracking in the static route to reach this dummy next hop:&lt;/P&gt;&lt;P&gt;ip route x.x.x.x y.y.y.y.y dialer1 track 1&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2015 15:38:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/route-maps-and-interface-tracking/m-p/2722803#M253734</guid>
      <dc:creator>Jose Jara</dc:creator>
      <dc:date>2015-10-06T15:38:48Z</dc:date>
    </item>
    <item>
      <title>Hi Josehow will the route</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/route-maps-and-interface-tracking/m-p/2722804#M253735</link>
      <description>&lt;P&gt;Hi Jose&lt;/P&gt;&lt;P&gt;how will the route with tracking work with the route-map that sets to either the Dialer or Cellular interface ?&lt;/P&gt;&lt;P&gt;with your example the "dummy route" will not be added if the dialer interface is down, but that won't make any difference in the route-map&lt;/P&gt;&lt;P&gt;Am I understanding you wrong ?&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2015 19:48:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/route-maps-and-interface-tracking/m-p/2722804#M253735</guid>
      <dc:creator>NeilGouws</dc:creator>
      <dc:date>2015-10-06T19:48:37Z</dc:date>
    </item>
    <item>
      <title>Hi Neil,you´re right and in</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/route-maps-and-interface-tracking/m-p/2722805#M253736</link>
      <description>&lt;P&gt;Hi Neil,&lt;/P&gt;&lt;P&gt;you´re right and in order to route to the cellular interface you'll add the same dummy route reachable through the cellular interface with a worse AD:&lt;/P&gt;&lt;P&gt;ip route x.x.x.x y.y.y.y Cellular0 50&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 07 Oct 2015 09:28:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/route-maps-and-interface-tracking/m-p/2722805#M253736</guid>
      <dc:creator>Jose Jara</dc:creator>
      <dc:date>2015-10-07T09:28:37Z</dc:date>
    </item>
    <item>
      <title>Josehow will a static route</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/route-maps-and-interface-tracking/m-p/2722806#M253737</link>
      <description>&lt;P&gt;Jose&lt;/P&gt;&lt;P&gt;how will a static route help with the route-map and setting the interface in the route-map&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;No default routing is used/allowed.&lt;/P&gt;&lt;P&gt;The route-map basically decides, based on a ACL, if traffic is allowed to go out the Dialer/Cellular interface.&lt;/P&gt;&lt;P&gt;In this case, that traffic is Office 365 traffic&lt;/P&gt;</description>
      <pubDate>Wed, 07 Oct 2015 09:36:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/route-maps-and-interface-tracking/m-p/2722806#M253737</guid>
      <dc:creator>NeilGouws</dc:creator>
      <dc:date>2015-10-07T09:36:45Z</dc:date>
    </item>
    <item>
      <title>You will set the next-hop in</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/route-maps-and-interface-tracking/m-p/2722807#M253738</link>
      <description>&lt;P&gt;You will set the next-hop in the route-map&amp;nbsp;to a dummy route&amp;nbsp;reachable through the dialer interface, in order to do the tracking. Then, in case the tracking fails, you will reach this dummy route (the same)&amp;nbsp;through the Cellular interface. So, you do not need to set the interface in the route-map just this dummy next-hop.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Oct 2015 10:07:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/route-maps-and-interface-tracking/m-p/2722807#M253738</guid>
      <dc:creator>Jose Jara</dc:creator>
      <dc:date>2015-10-07T10:07:21Z</dc:date>
    </item>
    <item>
      <title>Ok thanks that makes sense,</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/route-maps-and-interface-tracking/m-p/2722808#M253739</link>
      <description>&lt;P&gt;Ok thanks that makes sense, provided that I know what the next hop is and hoping that it doesn't change unexpectedly&lt;/P&gt;</description>
      <pubDate>Wed, 07 Oct 2015 11:25:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/route-maps-and-interface-tracking/m-p/2722808#M253739</guid>
      <dc:creator>NeilGouws</dc:creator>
      <dc:date>2015-10-07T11:25:14Z</dc:date>
    </item>
    <item>
      <title>Just an update, still waiting</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/route-maps-and-interface-tracking/m-p/2722809#M253740</link>
      <description>&lt;P&gt;Just an update, still waiting for telecoms company to supply more info on reliability of the next hop&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;P&gt;in theory and in 1 instance your recommendation worked, but at this stage it's not the complete solution&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Tue, 13 Oct 2015 05:29:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/route-maps-and-interface-tracking/m-p/2722809#M253740</guid>
      <dc:creator>NeilGouws</dc:creator>
      <dc:date>2015-10-13T05:29:02Z</dc:date>
    </item>
    <item>
      <title>Hopefully it does work or we</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/route-maps-and-interface-tracking/m-p/2722810#M253741</link>
      <description>&lt;P&gt;Hopefully it does work or we can try come up with another solution, from working in ISPs I never seen dynamic ips though on there side usually just the client side connecting in.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Oct 2015 07:16:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/route-maps-and-interface-tracking/m-p/2722810#M253741</guid>
      <dc:creator>Mark Malone</dc:creator>
      <dc:date>2015-10-13T07:16:22Z</dc:date>
    </item>
    <item>
      <title>Hi Neil,</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/route-maps-and-interface-tracking/m-p/2722811#M253742</link>
      <description>&lt;P&gt;Hi Neil,&lt;/P&gt;
&lt;P&gt;I am also facing the same problem, cloud you let me know if you have resolved it.&lt;/P&gt;
&lt;P&gt;Also regarding the below configuration, is it the complete one.&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;track 1 interface Dialer1 ip routing&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;!&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;interface Vlan1&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&amp;nbsp;ip policy route-map LOCAL-BREAK-OUT&lt;BR /&gt;!&lt;BR /&gt;route-map LOCAL-BREAK-OUT permit 10&lt;BR /&gt;&amp;nbsp;match ip address O365traffic&lt;BR /&gt;&amp;nbsp;set interface Dialer1, &lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;There is no Track command after the set interface dialer1 command, so how will track get executed. how will the failover to Dialer0 happen.&lt;/P&gt;
&lt;P&gt;It could be great if you can help me with this.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jul 2016 03:53:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/route-maps-and-interface-tracking/m-p/2722811#M253742</guid>
      <dc:creator>jesurexon.jegaprathaban</dc:creator>
      <dc:date>2016-07-07T03:53:27Z</dc:date>
    </item>
  </channel>
</rss>

