<?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 Prisma Access IPSEC tunnel timeout IKE phase-1/phase-2 negotiation is failed as responder....Due to timeout in Prisma Access Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/prisma-access-ipsec-tunnel-timeout-ike-phase-1-phase-2/m-p/511166#M387</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hello to All,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I see a lot of failed IKE phase-1 negotiations or even IKE phase-2 negotiations Due to timeout even when I am looking the Panorama logs as the Prisma Access is the Responder. What I see in common is that many Remote Networks are using the same Service IP address.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This shouldn't be an issue as in the article below shows but maybe if too many locations connnect to the same Service IP address this could cause an issue.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/prisma/prisma-access/prisma-access-panorama-admin/prisma-access-overview/when-do-ip-addresses-change/compute-locations-and-ip-address-allocation-for-remote-networks" target="_blank"&gt;https://docs.paloaltonetworks.com/prisma/prisma-access/prisma-access-panorama-admin/prisma-access-overview/when-do-ip-addresses-change/compute-locations-and-ip-address-allocation-for-remote-networks&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Sun, 07 Aug 2022 10:00:20 GMT</pubDate>
    <dc:creator>nikoolayy1</dc:creator>
    <dc:date>2022-08-07T10:00:20Z</dc:date>
    <item>
      <title>Prisma Access IPSEC tunnel timeout IKE phase-1/phase-2 negotiation is failed as responder....Due to timeout</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/prisma-access-ipsec-tunnel-timeout-ike-phase-1-phase-2/m-p/511166#M387</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hello to All,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I see a lot of failed IKE phase-1 negotiations or even IKE phase-2 negotiations Due to timeout even when I am looking the Panorama logs as the Prisma Access is the Responder. What I see in common is that many Remote Networks are using the same Service IP address.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This shouldn't be an issue as in the article below shows but maybe if too many locations connnect to the same Service IP address this could cause an issue.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/prisma/prisma-access/prisma-access-panorama-admin/prisma-access-overview/when-do-ip-addresses-change/compute-locations-and-ip-address-allocation-for-remote-networks" target="_blank"&gt;https://docs.paloaltonetworks.com/prisma/prisma-access/prisma-access-panorama-admin/prisma-access-overview/when-do-ip-addresses-change/compute-locations-and-ip-address-allocation-for-remote-networks&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 07 Aug 2022 10:00:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-access-discussions/prisma-access-ipsec-tunnel-timeout-ike-phase-1-phase-2/m-p/511166#M387</guid>
      <dc:creator>nikoolayy1</dc:creator>
      <dc:date>2022-08-07T10:00:20Z</dc:date>
    </item>
  </channel>
</rss>

