<?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 Hi Darren, in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-sla-route-lookup-failure/m-p/2782530#M175297</link>
    <description>&lt;P&gt;Hi Darren,&lt;/P&gt;
&lt;P&gt;Could you please share the output of 'show route' and 'show run route',&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Akshay Rastogi&lt;/P&gt;</description>
    <pubDate>Sat, 07 Nov 2015 15:48:51 GMT</pubDate>
    <dc:creator>Akshay Rastogi</dc:creator>
    <dc:date>2015-11-07T15:48:51Z</dc:date>
    <item>
      <title>ASA SLA route lookup failure</title>
      <link>https://community.cisco.com/t5/network-security/asa-sla-route-lookup-failure/m-p/2782529#M175296</link>
      <description>&lt;P&gt;Odd problem when configuring SLA on an ASA, i keep getting route lookup failure when trying to ping an remote&amp;nbsp;host across an IPSEC tunnel. &amp;nbsp;I've tried&amp;nbsp;the below utilizing both the inside and outside interfaces but both fail. &amp;nbsp;The ping from the ASA is successful which is confusing. &amp;nbsp;I've masked the IP's. &amp;nbsp;&lt;/P&gt;
&lt;P&gt;sla monitor 1&lt;BR /&gt; type echo protocol ipIcmpEcho x.x.x.x&amp;nbsp;interface outside&lt;BR /&gt; frequency 5&lt;BR /&gt;sla monitor schedule 1 life forever start-time now&lt;/P&gt;
&lt;P&gt;sla monitor 2&lt;BR /&gt;type echo protocol ipIcmpEcho&amp;nbsp;x.x.x.x&amp;nbsp;interface inside&lt;BR /&gt;frequency 5&lt;BR /&gt;sla monitor schedule 2 life forever start-time now&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;%ASA-6-110003: Routing failed to locate next hop for icmp from NP Identity Ifc:x.x.x.x/0(inside interface of ASA) to inside:x.x.x.x/0(remote system i'm trying to ping)&lt;/P&gt;
&lt;P&gt;Successful ping:&lt;/P&gt;
&lt;P&gt;FW01# ping inside&amp;nbsp;x.x.x.x&lt;BR /&gt;Type escape sequence to abort.&lt;BR /&gt;Sending 5, 100-byte ICMP Echos to x.x.x.x, timeout is 2 seconds:&lt;BR /&gt;!!!!!&lt;BR /&gt;Success rate is 100 percent (5/5), round-trip min/avg/max = 40/44/50 ms&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thoughts or suggestions would be appreciated.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 06:49:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-sla-route-lookup-failure/m-p/2782529#M175296</guid>
      <dc:creator>Darren Sasso</dc:creator>
      <dc:date>2019-03-12T06:49:48Z</dc:date>
    </item>
    <item>
      <title>Hi Darren,</title>
      <link>https://community.cisco.com/t5/network-security/asa-sla-route-lookup-failure/m-p/2782530#M175297</link>
      <description>&lt;P&gt;Hi Darren,&lt;/P&gt;
&lt;P&gt;Could you please share the output of 'show route' and 'show run route',&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Akshay Rastogi&lt;/P&gt;</description>
      <pubDate>Sat, 07 Nov 2015 15:48:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-sla-route-lookup-failure/m-p/2782530#M175297</guid>
      <dc:creator>Akshay Rastogi</dc:creator>
      <dc:date>2015-11-07T15:48:51Z</dc:date>
    </item>
    <item>
      <title>Issue has been resolved.</title>
      <link>https://community.cisco.com/t5/network-security/asa-sla-route-lookup-failure/m-p/2782531#M175298</link>
      <description>&lt;P&gt;Issue has been resolved.&lt;/P&gt;
&lt;P&gt;I had to add the remote FW IP as interesting traffic which worked.&lt;/P&gt;
&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Nov 2015 14:56:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-sla-route-lookup-failure/m-p/2782531#M175298</guid>
      <dc:creator>Darren Sasso</dc:creator>
      <dc:date>2015-11-09T14:56:46Z</dc:date>
    </item>
    <item>
      <title>Re: Issue has been resolved.</title>
      <link>https://community.cisco.com/t5/network-security/asa-sla-route-lookup-failure/m-p/3749208#M175300</link>
      <description>&lt;P&gt;Hello Darren,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have an exatly same issue so could i ask you to clarify what does it mean that you add remote FW ip as interesting traffic?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Nov 2018 12:31:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-sla-route-lookup-failure/m-p/3749208#M175300</guid>
      <dc:creator>donpepe06</dc:creator>
      <dc:date>2018-11-19T12:31:30Z</dc:date>
    </item>
  </channel>
</rss>

