- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
08-19-2021 01:02 AM - edited 08-20-2021 03:33 AM
On Palo side
IPSec Crypto profile
IPSec Protocol ESP
DH group 2
LT 1h
Encryption aes-256-gcm/cbc
Authentication
sha256
IKW Crypto profile
DH Group
group2
Encryption
aes-256-cbc
Authentication
sha 256
Key LT 8h
IKEv2 Authentication Multiple 5
On Meraki side
Phase1
Encryption
AES 256
Authentication
SHA256
Pseudo-random Function
Defaults to Authentication
Diffie-Hellman group
2
Lifetime (sec)
28800
Phase2
Encryption
AES 256
Authentication
SHA256
PFS group
2
Liftime (sec)
3600
Palo Alto IKE GW Options
Passive mode Enabled
NAT-T Enabled
Advanced Option
Strict Cookie Validation turned off
Liveness Check
Interval (sec) 5
11-08-2023 06:11 AM
Thought I'd reach out to see if you resolved this issue. We are encountering something similar between a Palo VM500 running 10.2.6 and a Juniper SRX. It appears on soft ipsec rekey that the Palo renews the SA and the Palo continues to use it, but the Juniper also creates a new SA (which the Palo sees and accepts) the Juniper uses this ipsec SA. Hence dropping network traffic. Would appreciate any thoughts you have.
11-15-2023 04:11 AM
Hi Jake,
we ended up applying the latest firmware to both sides which stabilized the traffic. After updating we got rid off the hanging tunnels.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!