PALO ALTO to AWS site to site VPN not established

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

PALO ALTO to AWS site to site VPN not established

L1 Bithead

Issue:
PALO ALTO to AWS IPsec site to site VPN not able to established.

Situation

Since AWS will provide two VPN tunnel by default.
One of the VPN tunnel is established using the same public IP of PALO ALTO while the other VPN tunnel not able to established. 

Here is the logs
2022-05-24 12:55:40.905 +0800 [PNTF]: { 39: }: ====> PHASE-1 NEGOTIATION FAILED AS RESPONDER, MAIN MODE <====
====> Failed SA:x.x.x.x[500]-x.x.x.x[500] cookie:ba86d45b27ded4d0:ab606e5c9f109876 <==== Due to timeout.

I can able to ping the AWS IP on the PALO ALTO.
Packet capture show that PALO ALTO send traffic to AWS but as per AWS support they did not received traffic from the PALO ALTO.


Any idea what is the cause why the other tunnel does not established.?

1 REPLY 1

L5 Sessionator

Do you have your VPC rules that allow inbound internet traffic, or whitelisting traffic from your NGFW public IP?

Help the community! Add tags & mark solutions please.
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!