<?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 Traceroute through FTD vs SLA monitor in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/traceroute-through-ftd-vs-sla-monitor/m-p/5049981#M1110331</link>
    <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I'm trying to allow traceroute through the firewall as per the below doc, however, when I update the Platform Settings to permit traceroute on Inside, Outside and another zone, SLA monitor which is tracking the primary ISP goes down and failover to the secondary ISP.&amp;nbsp; I've set the rate-limit and burst-limit to 3.&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/security/firepower-ngfw/215237-allow-traceroute-through-firepower-threa.html" target="_blank"&gt;Allow Traceroute through Firepower Threat Defense (FTD) - Cisco&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The SLA, Track and routing configs below, basically it's monitoring and tracking the primary ISP1's nexthop addresses (1.1.1.1 and 2.2.2.2 in the below example), and if both fails the floating default route would kick in.&lt;/P&gt;&lt;P&gt;#####SLA monitor configuration####&lt;/P&gt;&lt;P&gt;&amp;gt; show sla monitor configuration&lt;BR /&gt;SA Agent, Infrastructure Engine-II&lt;BR /&gt;Entry number: 1&lt;BR /&gt;Owner:&lt;BR /&gt;Tag:&lt;BR /&gt;Type of operation to perform: echo&lt;BR /&gt;Target address: 1.1.1.1&lt;BR /&gt;Interface: ISP1&lt;BR /&gt;Number of packets: 1&lt;BR /&gt;Request size (ARR data portion): 28&lt;BR /&gt;Operation timeout (milliseconds): 5000&lt;BR /&gt;Type Of Service parameters: 0x0&lt;BR /&gt;Verify data: No&lt;BR /&gt;Operation frequency (seconds): 15&lt;BR /&gt;Next Scheduled Start Time: Start Time already passed&lt;BR /&gt;Group Scheduled : FALSE&lt;BR /&gt;Life (seconds): Forever&lt;BR /&gt;Entry Ageout (seconds): never&lt;BR /&gt;Recurring (Starting Everyday): FALSE&lt;BR /&gt;Status of entry (SNMP RowStatus): Active&lt;BR /&gt;Enhanced History:&lt;/P&gt;&lt;P&gt;Entry number: 2&lt;BR /&gt;Owner:&lt;BR /&gt;Tag:&lt;BR /&gt;Type of operation to perform: echo&lt;BR /&gt;Target address: 2.2.2.2&lt;BR /&gt;Interface: ISP1&lt;BR /&gt;Number of packets: 1&lt;BR /&gt;Request size (ARR data portion): 28&lt;BR /&gt;Operation timeout (milliseconds): 5000&lt;BR /&gt;Type Of Service parameters: 0x0&lt;BR /&gt;Verify data: No&lt;BR /&gt;Operation frequency (seconds): 15&lt;BR /&gt;Next Scheduled Start Time: Start Time already passed&lt;BR /&gt;Group Scheduled : FALSE&lt;BR /&gt;Life (seconds): Forever&lt;BR /&gt;Entry Ageout (seconds): never&lt;BR /&gt;Recurring (Starting Everyday): FALSE&lt;BR /&gt;Status of entry (SNMP RowStatus): Active&lt;BR /&gt;Enhanced History:&lt;/P&gt;&lt;P&gt;&amp;gt;&lt;/P&gt;&lt;P&gt;####track configuration####&lt;/P&gt;&lt;P&gt;&amp;gt; show track&lt;BR /&gt;Track 1&lt;BR /&gt;Response Time Reporter 2 reachability&lt;BR /&gt;Reachability is Up&lt;BR /&gt;112 changes, last change 01:34:05&lt;BR /&gt;Latest operation return code: OK&lt;BR /&gt;Latest RTT (millisecs) 1&lt;BR /&gt;Tracked by:&lt;BR /&gt;STATIC-IP-ROUTING 0&lt;BR /&gt;Track 2&lt;BR /&gt;Response Time Reporter 1 reachability&lt;BR /&gt;Reachability is Up&lt;BR /&gt;98 changes, last change 2d04h&lt;BR /&gt;Latest operation return code: OK&lt;BR /&gt;Latest RTT (millisecs) 1&lt;BR /&gt;Tracked by:&lt;BR /&gt;STATIC-IP-ROUTING 0&lt;BR /&gt;&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;####routing####&lt;BR /&gt;route ISP1 0.0.0.0 0.0.0.0 192.168.100.1 1 track 1&lt;BR /&gt;route ISP1 0.0.0.0 128.0.0.0 192.168.100.1 1 track 2&lt;BR /&gt;route ISP1 128.0.0.0 128.0.0.0 192.168.100.1 1 track 2&lt;BR /&gt;route ISP2 0.0.0.0 0.0.0.0 192.168.200.1 5&lt;/P&gt;&lt;P&gt;####&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The ACP is allowing icmp3 and icmp11 from OUTSIDE zone to the host that I want to allow traceroute. (the destination host does not resides in INSIDE, but a different zone)&lt;/P&gt;&lt;P&gt;I notice that the above Cisco doc says "&lt;STRONG&gt;Caution&lt;/STRONG&gt;&lt;SPAN&gt;: Ensure&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;ICMP Destination Unreachable (Type 3) and ICMP Time Exceeded (Type 11)&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;are allowed from Outside to Inside in the ACL policy or Fastpath'ed in Pre-filter policy.", not sure whether this is causing the issue.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Any suggestions are very much appreciated.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Many thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 25 Mar 2024 12:05:29 GMT</pubDate>
    <dc:creator>atsukane</dc:creator>
    <dc:date>2024-03-25T12:05:29Z</dc:date>
    <item>
      <title>Traceroute through FTD vs SLA monitor</title>
      <link>https://community.cisco.com/t5/network-security/traceroute-through-ftd-vs-sla-monitor/m-p/5049981#M1110331</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I'm trying to allow traceroute through the firewall as per the below doc, however, when I update the Platform Settings to permit traceroute on Inside, Outside and another zone, SLA monitor which is tracking the primary ISP goes down and failover to the secondary ISP.&amp;nbsp; I've set the rate-limit and burst-limit to 3.&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/security/firepower-ngfw/215237-allow-traceroute-through-firepower-threa.html" target="_blank"&gt;Allow Traceroute through Firepower Threat Defense (FTD) - Cisco&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The SLA, Track and routing configs below, basically it's monitoring and tracking the primary ISP1's nexthop addresses (1.1.1.1 and 2.2.2.2 in the below example), and if both fails the floating default route would kick in.&lt;/P&gt;&lt;P&gt;#####SLA monitor configuration####&lt;/P&gt;&lt;P&gt;&amp;gt; show sla monitor configuration&lt;BR /&gt;SA Agent, Infrastructure Engine-II&lt;BR /&gt;Entry number: 1&lt;BR /&gt;Owner:&lt;BR /&gt;Tag:&lt;BR /&gt;Type of operation to perform: echo&lt;BR /&gt;Target address: 1.1.1.1&lt;BR /&gt;Interface: ISP1&lt;BR /&gt;Number of packets: 1&lt;BR /&gt;Request size (ARR data portion): 28&lt;BR /&gt;Operation timeout (milliseconds): 5000&lt;BR /&gt;Type Of Service parameters: 0x0&lt;BR /&gt;Verify data: No&lt;BR /&gt;Operation frequency (seconds): 15&lt;BR /&gt;Next Scheduled Start Time: Start Time already passed&lt;BR /&gt;Group Scheduled : FALSE&lt;BR /&gt;Life (seconds): Forever&lt;BR /&gt;Entry Ageout (seconds): never&lt;BR /&gt;Recurring (Starting Everyday): FALSE&lt;BR /&gt;Status of entry (SNMP RowStatus): Active&lt;BR /&gt;Enhanced History:&lt;/P&gt;&lt;P&gt;Entry number: 2&lt;BR /&gt;Owner:&lt;BR /&gt;Tag:&lt;BR /&gt;Type of operation to perform: echo&lt;BR /&gt;Target address: 2.2.2.2&lt;BR /&gt;Interface: ISP1&lt;BR /&gt;Number of packets: 1&lt;BR /&gt;Request size (ARR data portion): 28&lt;BR /&gt;Operation timeout (milliseconds): 5000&lt;BR /&gt;Type Of Service parameters: 0x0&lt;BR /&gt;Verify data: No&lt;BR /&gt;Operation frequency (seconds): 15&lt;BR /&gt;Next Scheduled Start Time: Start Time already passed&lt;BR /&gt;Group Scheduled : FALSE&lt;BR /&gt;Life (seconds): Forever&lt;BR /&gt;Entry Ageout (seconds): never&lt;BR /&gt;Recurring (Starting Everyday): FALSE&lt;BR /&gt;Status of entry (SNMP RowStatus): Active&lt;BR /&gt;Enhanced History:&lt;/P&gt;&lt;P&gt;&amp;gt;&lt;/P&gt;&lt;P&gt;####track configuration####&lt;/P&gt;&lt;P&gt;&amp;gt; show track&lt;BR /&gt;Track 1&lt;BR /&gt;Response Time Reporter 2 reachability&lt;BR /&gt;Reachability is Up&lt;BR /&gt;112 changes, last change 01:34:05&lt;BR /&gt;Latest operation return code: OK&lt;BR /&gt;Latest RTT (millisecs) 1&lt;BR /&gt;Tracked by:&lt;BR /&gt;STATIC-IP-ROUTING 0&lt;BR /&gt;Track 2&lt;BR /&gt;Response Time Reporter 1 reachability&lt;BR /&gt;Reachability is Up&lt;BR /&gt;98 changes, last change 2d04h&lt;BR /&gt;Latest operation return code: OK&lt;BR /&gt;Latest RTT (millisecs) 1&lt;BR /&gt;Tracked by:&lt;BR /&gt;STATIC-IP-ROUTING 0&lt;BR /&gt;&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;####routing####&lt;BR /&gt;route ISP1 0.0.0.0 0.0.0.0 192.168.100.1 1 track 1&lt;BR /&gt;route ISP1 0.0.0.0 128.0.0.0 192.168.100.1 1 track 2&lt;BR /&gt;route ISP1 128.0.0.0 128.0.0.0 192.168.100.1 1 track 2&lt;BR /&gt;route ISP2 0.0.0.0 0.0.0.0 192.168.200.1 5&lt;/P&gt;&lt;P&gt;####&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The ACP is allowing icmp3 and icmp11 from OUTSIDE zone to the host that I want to allow traceroute. (the destination host does not resides in INSIDE, but a different zone)&lt;/P&gt;&lt;P&gt;I notice that the above Cisco doc says "&lt;STRONG&gt;Caution&lt;/STRONG&gt;&lt;SPAN&gt;: Ensure&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;ICMP Destination Unreachable (Type 3) and ICMP Time Exceeded (Type 11)&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;are allowed from Outside to Inside in the ACL policy or Fastpath'ed in Pre-filter policy.", not sure whether this is causing the issue.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Any suggestions are very much appreciated.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Many thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 25 Mar 2024 12:05:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/traceroute-through-ftd-vs-sla-monitor/m-p/5049981#M1110331</guid>
      <dc:creator>atsukane</dc:creator>
      <dc:date>2024-03-25T12:05:29Z</dc:date>
    </item>
    <item>
      <title>Re: Traceroute through FTD vs SLA monitor</title>
      <link>https://community.cisco.com/t5/network-security/traceroute-through-ftd-vs-sla-monitor/m-p/5050099#M1110333</link>
      <description>&lt;P&gt;Ftd mgmt by fmc? If yes in fmc increase little the rate limit of icmp.&lt;/P&gt;
&lt;P&gt;I think you hit the limit and hence the ftd drop some icmp which make route down&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Mon, 25 Mar 2024 15:37:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/traceroute-through-ftd-vs-sla-monitor/m-p/5050099#M1110333</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-03-25T15:37:20Z</dc:date>
    </item>
    <item>
      <title>Re: Traceroute through FTD vs SLA monitor</title>
      <link>https://community.cisco.com/t5/network-security/traceroute-through-ftd-vs-sla-monitor/m-p/5050155#M1110338</link>
      <description>&lt;P&gt;hi, yes, the FTDs are FMC managed.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Mar 2024 16:50:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/traceroute-through-ftd-vs-sla-monitor/m-p/5050155#M1110338</guid>
      <dc:creator>atsukane</dc:creator>
      <dc:date>2024-03-25T16:50:25Z</dc:date>
    </item>
    <item>
      <title>Re: Traceroute through FTD vs SLA monitor</title>
      <link>https://community.cisco.com/t5/network-security/traceroute-through-ftd-vs-sla-monitor/m-p/5050157#M1110339</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Devices&amp;gt;Platform Settings&amp;gt;icmp&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Rate limit&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Increase it little&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;MHM&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 25 Mar 2024 16:55:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/traceroute-through-ftd-vs-sla-monitor/m-p/5050157#M1110339</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-03-25T16:55:36Z</dc:date>
    </item>
    <item>
      <title>Re: Traceroute through FTD vs SLA monitor</title>
      <link>https://community.cisco.com/t5/network-security/traceroute-through-ftd-vs-sla-monitor/m-p/5050158#M1110340</link>
      <description>&lt;P&gt;Thanks, I'll try that.&lt;/P&gt;&lt;P&gt;I've since found this link as well&amp;nbsp;&lt;A href="https://integratingit.wordpress.com/2019/10/12/ftd-allow-traceroute/" target="_blank"&gt;FTD allow ICMP/traceroute – integrating IT (wordpress.com)&lt;/A&gt;&amp;nbsp;which seems to involve more than the Cisco doc, but from the URL it looks like this was written back in 2019 so not all steps stated here may be required.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Mar 2024 16:59:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/traceroute-through-ftd-vs-sla-monitor/m-p/5050158#M1110340</guid>
      <dc:creator>atsukane</dc:creator>
      <dc:date>2024-03-25T16:59:33Z</dc:date>
    </item>
    <item>
      <title>Re: Traceroute through FTD vs SLA monitor</title>
      <link>https://community.cisco.com/t5/network-security/traceroute-through-ftd-vs-sla-monitor/m-p/5050163#M1110341</link>
      <description>&lt;P&gt;If rate not help you then check&lt;/P&gt;
&lt;P&gt;Acp is allow icmp destiantion unreachable and icmp time exceeded for traceroute&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Add to it icmp reply' I know the traffic toward FTD interface not effect by ACP but let only check.&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Mon, 25 Mar 2024 17:09:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/traceroute-through-ftd-vs-sla-monitor/m-p/5050163#M1110341</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-03-25T17:09:28Z</dc:date>
    </item>
    <item>
      <title>Re: Traceroute through FTD vs SLA monitor</title>
      <link>https://community.cisco.com/t5/network-security/traceroute-through-ftd-vs-sla-monitor/m-p/5053506#M1110537</link>
      <description>&lt;P&gt;Device&amp;gt;platform setting&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Icmp&lt;/P&gt;
&lt;P&gt;Add to this list icmp reply&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Waiting your reply&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&amp;nbsp;&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Sat, 30 Mar 2024 17:46:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/traceroute-through-ftd-vs-sla-monitor/m-p/5053506#M1110537</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-03-30T17:46:28Z</dc:date>
    </item>
  </channel>
</rss>

