<?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>article IKE Gateway Commit Failure: Peer Gateway ID Must Be Defined in Prisma Access Articles</title>
    <link>https://live.paloaltonetworks.com/t5/prisma-access-articles/ike-gateway-commit-failure-peer-gateway-id-must-be-defined/ta-p/283024</link>
    <description>&lt;DIV class="lia-message-template-symptoms-zone"&gt;
&lt;H2&gt;Symptoms&lt;/H2&gt;
&lt;P&gt;When configuring the remote network or service connection the commit fails:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Commit fails on cloud&lt;/LI&gt;
&lt;LI&gt;RN or SN fails to spin up on cloud even after 10 min&lt;/LI&gt;
&lt;/OL&gt;
&lt;/DIV&gt;
&lt;DIV class="lia-message-template-diagnosis-zone"&gt;
&lt;H2&gt;Diagnosis&lt;/H2&gt;
&lt;OL&gt;
&lt;LI&gt;Please verify the commit failure reason matches the one discussed in the article. Procedure to check the commit failure reason on Prisma Access firewall&lt;/LI&gt;
&lt;LI&gt;Check the IKE Gateway configuration for the gateway you see commit failure.&amp;nbsp;&lt;A title="Verify Commit Failure Reason On Prisma Access Firewall | LIVEcommunity " href="https://live.paloaltonetworks.com/t5/Prisma-Access-Articles/Procedure-to-Check-the-Commit-Failure-Reason-on-Prisma-Access/ta-p/283222" target="_self"&gt;Verify Commit Status&lt;/A&gt;&lt;BR /&gt;
&lt;PRE&gt;Configuration Errors:IKEv1 gateway &amp;lt;gw_name&amp;gt; peer gateway ID must be defined when peer address is dynamic.(Module: ikemgr) &lt;/PRE&gt;
&lt;/LI&gt;
&lt;LI&gt;Verify the peer IP type is dynamic&lt;/LI&gt;
&lt;/OL&gt;
&lt;/DIV&gt;
&lt;DIV class="lia-message-template-solution-zone"&gt;
&lt;H2&gt;Solution&lt;/H2&gt;
&lt;P&gt;When the dynamic IP is selected, we do not know the Public IP from which the peer is connecting. IPSec would require authenticating the peer. Due to this reason, we need identification information to be defined under "Local Identification" and "Peer Identification."&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="IKE Gateway Peer Dynamic .png" style="width: 642px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/21055iBE9079662BCE812D/image-size/large?v=v2&amp;amp;px=999" role="button" title="IKE Gateway Peer Dynamic .png" alt="IKE Gateway Peer Dynamic .png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Once the identification is configured, commit and push from Panorama.&lt;/P&gt;
&lt;/DIV&gt;</description>
    <pubDate>Wed, 25 Sep 2019 15:49:29 GMT</pubDate>
    <dc:creator>Sai_Tumuluri</dc:creator>
    <dc:date>2019-09-25T15:49:29Z</dc:date>
    <item>
      <title>IKE Gateway Commit Failure: Peer Gateway ID Must Be Defined</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-access-articles/ike-gateway-commit-failure-peer-gateway-id-must-be-defined/ta-p/283024</link>
      <description>&lt;P&gt;Learn what to do when configuring the remote network or service connection the commit fails on Prisma Access.&lt;/P&gt;</description>
      <pubDate>Wed, 25 Sep 2019 15:49:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-access-articles/ike-gateway-commit-failure-peer-gateway-id-must-be-defined/ta-p/283024</guid>
      <dc:creator>Sai_Tumuluri</dc:creator>
      <dc:date>2019-09-25T15:49:29Z</dc:date>
    </item>
  </channel>
</rss>

