<?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 Child-SA rekey negotiation fails in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-child-sa-rekey-negotiation-fails/m-p/548749#M112020</link>
    <description>&lt;P&gt;Our customer encounter intermittent connectivity issue with IPSec IKEv1 during phase 2 rekey of IPSec Child-SA. We open case with the IPSec peer device vendor, they mention that PAN is not sending message to R2011 (IPSec peer) for deleting the SA when the SA negotiation fails.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Summary of issue:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;On IPsec PA-850 peer device log, it shows IKE phase-2 negotiation is failed as responder, Due to negotiation timeout for that child-SA]&lt;/LI&gt;
&lt;LI&gt;On IPsec 4G router side SA rekey log it shows child-SA is successful established/rekey&lt;/LI&gt;
&lt;LI&gt;During that 1 hour Proxy-ID traffic for that Child-SA is down. Traffic resume on next successful Child-SA rekey, SA lifetime 1 hour.&lt;/LI&gt;
&lt;LI&gt;From debug log (as below) negotiation timeout on PA-850 trigger by intermittent packet transmission loss on Telco 4G mobile network.&amp;nbsp;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Highlight event log of “the sent the delete key message to the peer and started the negotiation as a responder.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1.re key at 5.00.07 of Child SA as responder for Proxy ID 2. Failed as negotiation as responder and didn’t send p2 delete message to peer.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2.Next re key at 5.39.12 of Child SA as responder for Proxy ID 2. Observe no existing SA (previous negotiation fail at 5.00.07am), so didn’t send p2 delete message to peer after successful rekey.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So, please advise on this behavior of the PA as a responder.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 10 Jul 2023 08:58:15 GMT</pubDate>
    <dc:creator>Purushotham</dc:creator>
    <dc:date>2023-07-10T08:58:15Z</dc:date>
    <item>
      <title>IPSec Child-SA rekey negotiation fails</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-child-sa-rekey-negotiation-fails/m-p/548749#M112020</link>
      <description>&lt;P&gt;Our customer encounter intermittent connectivity issue with IPSec IKEv1 during phase 2 rekey of IPSec Child-SA. We open case with the IPSec peer device vendor, they mention that PAN is not sending message to R2011 (IPSec peer) for deleting the SA when the SA negotiation fails.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Summary of issue:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;On IPsec PA-850 peer device log, it shows IKE phase-2 negotiation is failed as responder, Due to negotiation timeout for that child-SA]&lt;/LI&gt;
&lt;LI&gt;On IPsec 4G router side SA rekey log it shows child-SA is successful established/rekey&lt;/LI&gt;
&lt;LI&gt;During that 1 hour Proxy-ID traffic for that Child-SA is down. Traffic resume on next successful Child-SA rekey, SA lifetime 1 hour.&lt;/LI&gt;
&lt;LI&gt;From debug log (as below) negotiation timeout on PA-850 trigger by intermittent packet transmission loss on Telco 4G mobile network.&amp;nbsp;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Highlight event log of “the sent the delete key message to the peer and started the negotiation as a responder.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1.re key at 5.00.07 of Child SA as responder for Proxy ID 2. Failed as negotiation as responder and didn’t send p2 delete message to peer.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2.Next re key at 5.39.12 of Child SA as responder for Proxy ID 2. Observe no existing SA (previous negotiation fail at 5.00.07am), so didn’t send p2 delete message to peer after successful rekey.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So, please advise on this behavior of the PA as a responder.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jul 2023 08:58:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ipsec-child-sa-rekey-negotiation-fails/m-p/548749#M112020</guid>
      <dc:creator>Purushotham</dc:creator>
      <dc:date>2023-07-10T08:58:15Z</dc:date>
    </item>
    <item>
      <title>Re: IPSec Child-SA rekey negotiation fails</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-child-sa-rekey-negotiation-fails/m-p/548834#M112029</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/244332"&gt;@Purushotham&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for your question. I would verify that the PA-850 and peer are&amp;nbsp;&lt;SPAN&gt;using compatible IPSec settings, such as encryption algorithms, key lifetimes, and authentication methods,&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;Proxy IDs, and other parameters related to phase 2 negotiation.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;If you've verified the settings are good to go and you are still experiencing issues, I recommend creating a support case for this issue.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jul 2023 21:46:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ipsec-child-sa-rekey-negotiation-fails/m-p/548834#M112029</guid>
      <dc:creator>JayGolf</dc:creator>
      <dc:date>2023-07-10T21:46:07Z</dc:date>
    </item>
  </channel>
</rss>

