<?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 URGENT VPN failover help needed in Panorama Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/panorama-discussions/urgent-vpn-failover-help-needed/m-p/600727#M2509</link>
    <description>&lt;P&gt;Hello Everyone,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have an existing policy-based site-to-site VPN between our Palo Alto and client's Meraki.&lt;/P&gt;
&lt;P&gt;The current VPN is to their Primary WAN IP address(Primary ISP). Now they have a secondary ISP. Both the primary and secondary ISPs are configured on the client's Meraki. I have to configure VPN failover on Palo Alto. Please help me out. I have read multiple articles but I have got more confused.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 15 Oct 2024 13:03:18 GMT</pubDate>
    <dc:creator>msdphi</dc:creator>
    <dc:date>2024-10-15T13:03:18Z</dc:date>
    <item>
      <title>URGENT VPN failover help needed</title>
      <link>https://live.paloaltonetworks.com/t5/panorama-discussions/urgent-vpn-failover-help-needed/m-p/600727#M2509</link>
      <description>&lt;P&gt;Hello Everyone,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have an existing policy-based site-to-site VPN between our Palo Alto and client's Meraki.&lt;/P&gt;
&lt;P&gt;The current VPN is to their Primary WAN IP address(Primary ISP). Now they have a secondary ISP. Both the primary and secondary ISPs are configured on the client's Meraki. I have to configure VPN failover on Palo Alto. Please help me out. I have read multiple articles but I have got more confused.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Oct 2024 13:03:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/panorama-discussions/urgent-vpn-failover-help-needed/m-p/600727#M2509</guid>
      <dc:creator>msdphi</dc:creator>
      <dc:date>2024-10-15T13:03:18Z</dc:date>
    </item>
    <item>
      <title>Re: URGENT VPN failover help needed</title>
      <link>https://live.paloaltonetworks.com/t5/panorama-discussions/urgent-vpn-failover-help-needed/m-p/609527#M2546</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/722572629"&gt;@msdphi&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is Palo alto side initiator here? I am assuming it and below are the configuration steps ( high level ).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;On Palo Alto side, you need to configure two separate IPSEC tunnels towards client side ( towards &lt;STRONG&gt;ISP1&lt;/STRONG&gt; and &lt;STRONG&gt;ISP2&lt;/STRONG&gt; ). For both the tunnels, you will have same proxy IDs.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Let’s say you have configured &lt;STRONG&gt;tunnel.1&lt;/STRONG&gt; interface for the tunnel with &lt;STRONG&gt;ISP1&lt;/STRONG&gt; &lt;STRONG&gt;IP&lt;/STRONG&gt; and &lt;STRONG&gt;tunnel.2&lt;/STRONG&gt; interface for tunnel with &lt;STRONG&gt;ISP2&lt;/STRONG&gt; &lt;STRONG&gt;IP.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Now you will add two static routes for tunnel destination hosts/network pointing to &lt;STRONG&gt;tunnel.1&lt;/STRONG&gt; and &lt;STRONG&gt;tunnel.2&lt;/STRONG&gt; interfaces. &lt;STRONG&gt;Here, keep higher metric on the route pointing towards tunnel.2 interface. e.g. 10 metric for the route pointing to tunnel.1 and metric 11 for the route pointing to tunnel.2 interface&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For failover, you need to use path monitoring on the static route pointing towards &lt;STRONG&gt;tunnel.1&lt;/STRONG&gt; i.e. your primary ISP.&lt;/P&gt;
&lt;P&gt;For this, you need to assign IP address on the tunnel interface i.e. &lt;STRONG&gt;tunnel.1&lt;/STRONG&gt; and take one remote end IP which is responding to ping requests. So, you can configure that IP as a destination. Firewall will ping that IP during configured internals. If primary tunnel goes down, remote end IP will stop responding to the ping requests. As soon as path monitoring is detected as &lt;STRONG&gt;DOWN ,&amp;nbsp;&lt;/STRONG&gt;the route pointing to &lt;STRONG&gt;tunnel.1&lt;/STRONG&gt; interface will be removed from the forwarding routing table. So, after that automatically, request will be send towards &lt;STRONG&gt;tunnel.2&lt;/STRONG&gt; interface which nothing but your backup tunnel.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Once primary tunnel is back online and remote IP starts pinging from primary tunnel interface, route towards tunnel.1 interface will be added back and traffic will be pointed to Primary tunnel with ISP1. For static route path monitoring, refer &lt;A href="https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-networking-admin/static-routes/static-route-removal-based-on-path-monitoring" target="_blank"&gt;this&lt;/A&gt;&amp;nbsp;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Client team also need to handle all the required configuration on their end so they can accept traffic from Palo Also side.&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="SutareMayur_0-1729506688079.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/63138i0A40C48B8933799D/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="SutareMayur_0-1729506688079.png" alt="SutareMayur_0-1729506688079.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 21 Oct 2024 10:31:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/panorama-discussions/urgent-vpn-failover-help-needed/m-p/609527#M2546</guid>
      <dc:creator>SutareMayur</dc:creator>
      <dc:date>2024-10-21T10:31:54Z</dc:date>
    </item>
  </channel>
</rss>

