<?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: Fail Over using Path Monitoring &amp;amp; NAT configuration in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/fail-over-using-path-monitoring-amp-nat-configuration/m-p/253141#M71929</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Yes it will be the same. two VR's are recommeded, however I accomplished the same thing with one VR in the past.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClSeCAK" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClSeCAK&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClGQCA0" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClGQCA0&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 20:52:39 GMT</pubDate>
    <dc:creator>OtakarKlier</dc:creator>
    <dc:date>2019-03-11T20:52:39Z</dc:date>
    <item>
      <title>Fail Over using Path Monitoring &amp; NAT configuration</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/fail-over-using-path-monitoring-amp-nat-configuration/m-p/253120#M71925</link>
      <description>&lt;P&gt;I have a firewall wth 2 broadband circuits connected to it, one primary &amp;amp; one secondary.&amp;nbsp; My goal is to PAT all outbound traffic usinging the primary interface's public address but in a fail over situation I want to PAT all outbound traffic using the secondary interface public address. I configured path monitoring and believe that the static default route to the primary will get removed from the RIB if the circuit goes down but I'm not sure if failover will actually work since my global PAT is configured to use the pirmary interface public address &lt;STRONG&gt;Eth1/1&lt;/STRONG&gt; &amp;amp; I dont have another PAT rule configured.&amp;nbsp; I am half tempted to configure another PAT rule specifying the secondary interface but I can only imagine it will confilict with the primary.&amp;nbsp; Can someone with experience configuring failover in Palo Alto tell me if Path Monitoring is the best path to take in order to complete my goal &amp;amp; if so how NAT/PAT should be addressed.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 18:44:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/fail-over-using-path-monitoring-amp-nat-configuration/m-p/253120#M71925</guid>
      <dc:creator>MarioMarquez</dc:creator>
      <dc:date>2019-03-11T18:44:13Z</dc:date>
    </item>
    <item>
      <title>Re: Fail Over using Path Monitoring &amp; NAT configuration</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/fail-over-using-path-monitoring-amp-nat-configuration/m-p/253138#M71927</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;You will need a PAT for each outbound interface.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 20:24:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/fail-over-using-path-monitoring-amp-nat-configuration/m-p/253138#M71927</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2019-03-11T20:24:00Z</dc:date>
    </item>
    <item>
      <title>Re: Fail Over using Path Monitoring &amp; NAT configuration</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/fail-over-using-path-monitoring-amp-nat-configuration/m-p/253139#M71928</link>
      <description>&lt;P&gt;I suppose the secondary PAT rule would need to be placed under the primary in the NAT policy? Is this correct?&amp;nbsp; Also how would this work if I intend on using the secondary internet circuit&amp;nbsp;as&amp;nbsp;VPN peer backup?&amp;nbsp;&amp;nbsp;I have to dig into palo alto tunnel configurations a bit more but Im not sure that&amp;nbsp;Path Monitoring would allow the secondary circuit to be&amp;nbsp;on&amp;nbsp;standby&amp;nbsp;for use&amp;nbsp;as a backup circuit only if the primary circuit goes down&amp;nbsp;in the same way as a failover for VPN as well as internet?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 20:37:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/fail-over-using-path-monitoring-amp-nat-configuration/m-p/253139#M71928</guid>
      <dc:creator>MarioMarquez</dc:creator>
      <dc:date>2019-03-11T20:37:44Z</dc:date>
    </item>
    <item>
      <title>Re: Fail Over using Path Monitoring &amp; NAT configuration</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/fail-over-using-path-monitoring-amp-nat-configuration/m-p/253141#M71929</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Yes it will be the same. two VR's are recommeded, however I accomplished the same thing with one VR in the past.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClSeCAK" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClSeCAK&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClGQCA0" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClGQCA0&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 20:52:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/fail-over-using-path-monitoring-amp-nat-configuration/m-p/253141#M71929</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2019-03-11T20:52:39Z</dc:date>
    </item>
  </channel>
</rss>

