<?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 Static Route Path Monitoring Clarification in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/static-route-path-monitoring-clarification/m-p/315307#M81244</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Let's say a scenario where I have a default route configured to go out interface 2 with a Metric of 10&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then I have another static route to go out interface 3 with metric of 5. On this route I setup path monitoring to ping an ip address that is accessible to both interface 2 and interface 3. Does the static route path monitoring ensure that its "ping" is only going over the interface that it is applied to (in this case interface 3)? Basically im pointing at the fact both interface can see the monitored IP and the monitor would always be up or at least it would go down and after the failover go back up (because of interface 2's ability to ping that IP). I assume it only goes over the interface the monitor is applied to but for sanity's sake I wanted to ask.&lt;/P&gt;</description>
    <pubDate>Mon, 09 Mar 2020 18:34:54 GMT</pubDate>
    <dc:creator>RITS54468998</dc:creator>
    <dc:date>2020-03-09T18:34:54Z</dc:date>
    <item>
      <title>Static Route Path Monitoring Clarification</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/static-route-path-monitoring-clarification/m-p/315307#M81244</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Let's say a scenario where I have a default route configured to go out interface 2 with a Metric of 10&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then I have another static route to go out interface 3 with metric of 5. On this route I setup path monitoring to ping an ip address that is accessible to both interface 2 and interface 3. Does the static route path monitoring ensure that its "ping" is only going over the interface that it is applied to (in this case interface 3)? Basically im pointing at the fact both interface can see the monitored IP and the monitor would always be up or at least it would go down and after the failover go back up (because of interface 2's ability to ping that IP). I assume it only goes over the interface the monitor is applied to but for sanity's sake I wanted to ask.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Mar 2020 18:34:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/static-route-path-monitoring-clarification/m-p/315307#M81244</guid>
      <dc:creator>RITS54468998</dc:creator>
      <dc:date>2020-03-09T18:34:54Z</dc:date>
    </item>
    <item>
      <title>Re: Static Route Path Monitoring Clarification</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/static-route-path-monitoring-clarification/m-p/315313#M81245</link>
      <description>&lt;P&gt;Yes it goes from the interface where path monitoring is enabled. In your case, it will be interface 3. As whenever you configure path monitoring for any static route, you mention source IP/interface which belong to the interface on which the monitoring is getting applied.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you want to monitor both the routes, you need to apply path monitoring separately on both routes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope it helps you!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Mayur&lt;/P&gt;</description>
      <pubDate>Mon, 09 Mar 2020 19:06:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/static-route-path-monitoring-clarification/m-p/315313#M81245</guid>
      <dc:creator>SutareMayur</dc:creator>
      <dc:date>2020-03-09T19:06:27Z</dc:date>
    </item>
  </channel>
</rss>

