<?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: ISP Failover and DHCP in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/isp-failover-and-dhcp/m-p/527014#M108909</link>
    <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/176255"&gt;@pomologist&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you want the static ISP to be primary, and the DHCP ISP to be secondary, configure the static route for the static ISP just like the document.&amp;nbsp; Then set the metric for the DHCP default route to be &lt;STRONG&gt;higher&lt;/STRONG&gt; than the static route.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="TomYoung_0-1673644886141.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/47004i7243A039E7CDA719/image-size/medium?v=v2&amp;amp;px=400" role="button" title="TomYoung_0-1673644886141.png" alt="TomYoung_0-1673644886141.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Only the default route to the static ISP will be active (A) in the route table (Show Runtime Stats).&amp;nbsp; When there is a failure (cannot ping the Path Monitoring IP addresses), that default route will be removed.&amp;nbsp; The DHCP ISP default route will then be used.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Very important!&amp;nbsp; Do not use only one destination IP address under Path Monitoring!&amp;nbsp; Use at least 2 with the Failure Condition set to "all."&amp;nbsp; Then if one public IP goes down for maintenance, your Internet does not fail over.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Tom&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 13 Jan 2023 21:31:40 GMT</pubDate>
    <dc:creator>TomYoung</dc:creator>
    <dc:date>2023-01-13T21:31:40Z</dc:date>
    <item>
      <title>ISP Failover and DHCP</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/isp-failover-and-dhcp/m-p/527008#M108907</link>
      <description>&lt;P&gt;Hello, I am following this guide to set up ISP failover.&amp;nbsp;&amp;nbsp;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PLL8CAO" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PLL8CAO&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The problem is that my failover ISP (Starlink), does not provide me a static IP address&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;How would you recommend accomplishing what I want to do when the failover ISP provides a DHCP address?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Fri, 13 Jan 2023 20:50:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/isp-failover-and-dhcp/m-p/527008#M108907</guid>
      <dc:creator>pomologist</dc:creator>
      <dc:date>2023-01-13T20:50:44Z</dc:date>
    </item>
    <item>
      <title>Re: ISP Failover and DHCP</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/isp-failover-and-dhcp/m-p/527014#M108909</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/176255"&gt;@pomologist&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you want the static ISP to be primary, and the DHCP ISP to be secondary, configure the static route for the static ISP just like the document.&amp;nbsp; Then set the metric for the DHCP default route to be &lt;STRONG&gt;higher&lt;/STRONG&gt; than the static route.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="TomYoung_0-1673644886141.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/47004i7243A039E7CDA719/image-size/medium?v=v2&amp;amp;px=400" role="button" title="TomYoung_0-1673644886141.png" alt="TomYoung_0-1673644886141.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Only the default route to the static ISP will be active (A) in the route table (Show Runtime Stats).&amp;nbsp; When there is a failure (cannot ping the Path Monitoring IP addresses), that default route will be removed.&amp;nbsp; The DHCP ISP default route will then be used.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Very important!&amp;nbsp; Do not use only one destination IP address under Path Monitoring!&amp;nbsp; Use at least 2 with the Failure Condition set to "all."&amp;nbsp; Then if one public IP goes down for maintenance, your Internet does not fail over.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Tom&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Jan 2023 21:31:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/isp-failover-and-dhcp/m-p/527014#M108909</guid>
      <dc:creator>TomYoung</dc:creator>
      <dc:date>2023-01-13T21:31:40Z</dc:date>
    </item>
    <item>
      <title>Re: ISP Failover and DHCP</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/isp-failover-and-dhcp/m-p/527295#M108944</link>
      <description>&lt;P&gt;Thank you so much!&amp;nbsp; That works perfectly!&amp;nbsp; I really appreciate your help.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Jan 2023 01:10:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/isp-failover-and-dhcp/m-p/527295#M108944</guid>
      <dc:creator>pomologist</dc:creator>
      <dc:date>2023-01-17T01:10:28Z</dc:date>
    </item>
  </channel>
</rss>

