<?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 Re: Cisco ASA PA ipsec issue in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-pa-ipsec-issue/m-p/473367#M103286</link>
    <description>&lt;P&gt;Hi Tom,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are you using route or policy based routing for your site to site tunnels between the PA and FTD?&lt;/P&gt;</description>
    <pubDate>Tue, 15 Mar 2022 19:19:36 GMT</pubDate>
    <dc:creator>ITforacompany</dc:creator>
    <dc:date>2022-03-15T19:19:36Z</dc:date>
    <item>
      <title>Cisco ASA PA ipsec issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-pa-ipsec-issue/m-p/472646#M103229</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have recently come across an interesting issue between a Cisco ASA ikev2 tunnel with a PA.&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I was to failover the PA to an HA peer, traffic initiated from the Cisco ASA continues to flow whilst traffic initiating from the PA stops.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I noticed when the PA fails over the ASA drops both phases and recreates them with a new SPI value whilst the PA continues to use the same SPA value. PA manages to change its SPA value to match the new SPI value only for traffic that originates from the ASA&amp;nbsp; although traffic from the PA continues to use the same SPA value which causes the traffic to not be sent.&lt;/P&gt;&lt;P&gt;My fix currently is by resetting the problematic proxy ID's from PA.&lt;/P&gt;&lt;P&gt;I have a case open with PA although has anyone come across this before as I assume this would be a common problem faced.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cisco ASA 9.8.4.xx, PA 10.1.4-h4&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 13 Mar 2022 20:51:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-pa-ipsec-issue/m-p/472646#M103229</guid>
      <dc:creator>ITforacompany</dc:creator>
      <dc:date>2022-03-13T20:51:59Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA PA ipsec issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-pa-ipsec-issue/m-p/473051#M103262</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/208442"&gt;@ITforacompany&lt;/a&gt; ,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Have you configured Liveness Check under Network &amp;gt; Network Profiles &amp;gt; IKE Gateways &amp;gt; [edit gateway] &amp;gt; Advanced Options?&amp;nbsp; I have that set to 5 seconds on an IPsec tunnel to an FTD device which is has much of the same code as an ASA.&amp;nbsp; &lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClgcCAC" target="_blank" rel="noopener"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClgcCAC&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The ASA may need the "crypto ikev2 dpd interval retry-interval" command configured.&amp;nbsp; I can't remember if it is default.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;</description>
      <pubDate>Tue, 15 Mar 2022 00:06:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-pa-ipsec-issue/m-p/473051#M103262</guid>
      <dc:creator>TomYoung</dc:creator>
      <dc:date>2022-03-15T00:06:28Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA PA ipsec issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-pa-ipsec-issue/m-p/473080#M103264</link>
      <description>&lt;P&gt;Hi Tom,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Appreciate the reply although the liveness check on the PA's and the DPD on the ASA is already configured.&lt;/P&gt;&lt;P&gt;They are different values where the PA is 5seconds and the ASA is 10seconds retry every 2 although i would not think this would be the issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 15 Mar 2022 03:23:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-pa-ipsec-issue/m-p/473080#M103264</guid>
      <dc:creator>ITforacompany</dc:creator>
      <dc:date>2022-03-15T03:23:25Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA PA ipsec issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-pa-ipsec-issue/m-p/473367#M103286</link>
      <description>&lt;P&gt;Hi Tom,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are you using route or policy based routing for your site to site tunnels between the PA and FTD?&lt;/P&gt;</description>
      <pubDate>Tue, 15 Mar 2022 19:19:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-pa-ipsec-issue/m-p/473367#M103286</guid>
      <dc:creator>ITforacompany</dc:creator>
      <dc:date>2022-03-15T19:19:36Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA PA ipsec issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-pa-ipsec-issue/m-p/474764#M103387</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/208442"&gt;@ITforacompany&lt;/a&gt; ,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Mine is still proxy-based.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;</description>
      <pubDate>Mon, 21 Mar 2022 18:45:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-pa-ipsec-issue/m-p/474764#M103387</guid>
      <dc:creator>TomYoung</dc:creator>
      <dc:date>2022-03-21T18:45:44Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA PA ipsec issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-pa-ipsec-issue/m-p/512678#M106521</link>
      <description>&lt;P&gt;Did PA ever get back to you on the case you opened or did you ever get a fix? I feel I'm having the very same issue you describe.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Aug 2022 14:21:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-pa-ipsec-issue/m-p/512678#M106521</guid>
      <dc:creator>bmartinsmm</dc:creator>
      <dc:date>2022-08-23T14:21:23Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA PA ipsec issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-pa-ipsec-issue/m-p/512742#M106532</link>
      <description>&lt;P&gt;They did and it was drawn out. They deem this issue is just between Cisco ASA's and PA's. All other parties are not affected although yet to be tested.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Their reply to CASE 02120653&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;"&lt;SPAN&gt;The root of this problem is due to IKE phase 1 SA information NOT synchronized between the Palo Alto Networks HA firewalls (only IPSEC phase 2 SAs are synchronized between HA firewalls)."&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Their initial answer was to disable the liveness check and DPD which after failing over the PA pairs did work although the issue arose again when the ASA rekeyed. The traffic dropped again for the proxy ID traffic that was originating behind the PA. This is due to the phase 1 details not being syncing between the HA pairs. The only fix at the moment is to manually run "test vpn ipsec-sa" from PA.&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I am pushing our account rep to add it as a hotfix.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Aug 2022 20:02:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-pa-ipsec-issue/m-p/512742#M106532</guid>
      <dc:creator>ITforacompany</dc:creator>
      <dc:date>2022-08-23T20:02:49Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA PA ipsec issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-pa-ipsec-issue/m-p/512745#M106534</link>
      <description>Wow....thank you for the reply. Hopefully they will add it.&lt;BR /&gt;</description>
      <pubDate>Tue, 23 Aug 2022 20:51:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-pa-ipsec-issue/m-p/512745#M106534</guid>
      <dc:creator>bmartinsmm</dc:creator>
      <dc:date>2022-08-23T20:51:28Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA PA ipsec issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-pa-ipsec-issue/m-p/572253#M115153</link>
      <description>&lt;P&gt;Hi, I got similar issue here. Any update from your side?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 09 Jan 2024 05:38:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-pa-ipsec-issue/m-p/572253#M115153</guid>
      <dc:creator>Mr.Hilmi</dc:creator>
      <dc:date>2024-01-09T05:38:03Z</dc:date>
    </item>
  </channel>
</rss>

