<?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 Re: Static route path monitoring recovery in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/static-route-path-monitoring-recovery/m-p/253115#M71922</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Typically, the default route handles this, but if you do not have one, then yes you will need additional static routes. The monitor IP's can be anything as long as they are reachable.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope that clarifies things.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 16:20:02 GMT</pubDate>
    <dc:creator>OtakarKlier</dc:creator>
    <dc:date>2019-03-11T16:20:02Z</dc:date>
    <item>
      <title>Static route path monitoring recovery</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/static-route-path-monitoring-recovery/m-p/228907#M65799</link>
      <description>&lt;P&gt;I've configured static route path monitoring on primary ISP.&amp;nbsp; When it if fails secondary ISP comes up.&amp;nbsp; Do I need to configure static route path monitoring on secondary ISP for primary to come back when the circuit recovers?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Thu, 30 Aug 2018 15:40:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/static-route-path-monitoring-recovery/m-p/228907#M65799</guid>
      <dc:creator>treese</dc:creator>
      <dc:date>2018-08-30T15:40:00Z</dc:date>
    </item>
    <item>
      <title>Re: Static route path monitoring recovery</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/static-route-path-monitoring-recovery/m-p/228942#M65803</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;You do not need to.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.paloaltonetworks.com/documentation/80/pan-os/pan-os/networking/static-routes/static-route-removal-based-on-path-monitoring" target="_blank"&gt;https://www.paloaltonetworks.com/documentation/80/pan-os/pan-os/networking/static-routes/static-route-removal-based-on-path-monitoring&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It will come back on its own when the monitor determines the conditions are correct.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Thu, 30 Aug 2018 18:44:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/static-route-path-monitoring-recovery/m-p/228942#M65803</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2018-08-30T18:44:04Z</dc:date>
    </item>
    <item>
      <title>Re: Static route path monitoring recovery</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/static-route-path-monitoring-recovery/m-p/228944#M65804</link>
      <description>&lt;P&gt;Thanks for the quick response.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Aug 2018 18:46:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/static-route-path-monitoring-recovery/m-p/228944#M65804</guid>
      <dc:creator>treese</dc:creator>
      <dc:date>2018-08-30T18:46:55Z</dc:date>
    </item>
    <item>
      <title>Re: Static route path monitoring recovery</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/static-route-path-monitoring-recovery/m-p/253111#M71919</link>
      <description>&lt;P&gt;What if the monitoring IP's are not within the source interface subnet range? Say for instance I monitor public dns servers like 8.8.8.8/4.2.2.2 from my source ISP interface which has a public /30.&amp;nbsp; Do I need to have a seperate static routes for destination 8.8.8.8/4.2.2.2 pointing to that ISP interface next-hop?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 16:06:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/static-route-path-monitoring-recovery/m-p/253111#M71919</guid>
      <dc:creator>fcatapano1</dc:creator>
      <dc:date>2019-03-11T16:06:03Z</dc:date>
    </item>
    <item>
      <title>Re: Static route path monitoring recovery</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/static-route-path-monitoring-recovery/m-p/253115#M71922</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Typically, the default route handles this, but if you do not have one, then yes you will need additional static routes. The monitor IP's can be anything as long as they are reachable.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope that clarifies things.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 16:20:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/static-route-path-monitoring-recovery/m-p/253115#M71922</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2019-03-11T16:20:02Z</dc:date>
    </item>
  </channel>
</rss>

