<?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 IPsec tunnel to Prisma Access down in Prisma SD-WAN Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/prisma-sd-wan-discussions/ipsec-tunnel-to-prisma-access-down/m-p/591895#M185</link>
    <description>&lt;P&gt;I have 2 sites, each with a virtual ION. Each has 2 WAN interfaces, behind NAT, and a pair of tunnels to Prisma Access. Site1 is fine and both tunnels are up. Site 2 was fine but at some point one of the tunnels went down.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I cannot figure out what could be the issue as their appears to be limited logging or IKE/IPsec debugging. I can see the from the CLI the down tunnel is in the "tunnel_bring_up" state. Internet from both interfaces works and I can ping tunnel endpoint from either WAN interface.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;These tunnels were auto created using the "Connect to Prisma Access" feature and both have the same tunnel endpoint IP. Site 1 is configured in a similar fashion and is up.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any ideas where to look next?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 13 Jul 2024 19:12:52 GMT</pubDate>
    <dc:creator>BBartik</dc:creator>
    <dc:date>2024-07-13T19:12:52Z</dc:date>
    <item>
      <title>IPsec tunnel to Prisma Access down</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-sd-wan-discussions/ipsec-tunnel-to-prisma-access-down/m-p/591895#M185</link>
      <description>&lt;P&gt;I have 2 sites, each with a virtual ION. Each has 2 WAN interfaces, behind NAT, and a pair of tunnels to Prisma Access. Site1 is fine and both tunnels are up. Site 2 was fine but at some point one of the tunnels went down.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I cannot figure out what could be the issue as their appears to be limited logging or IKE/IPsec debugging. I can see the from the CLI the down tunnel is in the "tunnel_bring_up" state. Internet from both interfaces works and I can ping tunnel endpoint from either WAN interface.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;These tunnels were auto created using the "Connect to Prisma Access" feature and both have the same tunnel endpoint IP. Site 1 is configured in a similar fashion and is up.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any ideas where to look next?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 13 Jul 2024 19:12:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-sd-wan-discussions/ipsec-tunnel-to-prisma-access-down/m-p/591895#M185</guid>
      <dc:creator>BBartik</dc:creator>
      <dc:date>2024-07-13T19:12:52Z</dc:date>
    </item>
    <item>
      <title>Re: IPsec tunnel to Prisma Access down</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-sd-wan-discussions/ipsec-tunnel-to-prisma-access-down/m-p/591897#M186</link>
      <description>&lt;P&gt;So the virtual ion is behind a palo FW and the session state was stale I think. I cleared the session from the Palo and the tunnel came up.&lt;/P&gt;</description>
      <pubDate>Sat, 13 Jul 2024 19:17:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-sd-wan-discussions/ipsec-tunnel-to-prisma-access-down/m-p/591897#M186</guid>
      <dc:creator>BBartik</dc:creator>
      <dc:date>2024-07-13T19:17:16Z</dc:date>
    </item>
  </channel>
</rss>

