08-05-2021 08:28 AM - edited 08-05-2021 08:31 AM
Proxy IDs on palo alto side are required to mentioned whenever peer end is acting as Policy based VPN because Palo Alto always act as Route based vpn. Now in order to check if proxy id is causing the issues, you should check the system logs by filtering VPN logs which will give you more clarity on the issue. If issue with proxy ids, you will see logs like proxy-id mismatch / negotiation failed when processing proxy ID. Proxy ID's need to be identical on both VPN peers for negotiation to be successful.
Apart from that, I would recommend you to verify the Phase 2 IPSEC parameters, routes for the traffic to be routed from tunnel.
Hope it helps!
08-05-2021 08:28 AM - edited 08-05-2021 08:31 AM
Proxy IDs on palo alto side are required to mentioned whenever peer end is acting as Policy based VPN because Palo Alto always act as Route based vpn. Now in order to check if proxy id is causing the issues, you should check the system logs by filtering VPN logs which will give you more clarity on the issue. If issue with proxy ids, you will see logs like proxy-id mismatch / negotiation failed when processing proxy ID. Proxy ID's need to be identical on both VPN peers for negotiation to be successful.
Apart from that, I would recommend you to verify the Phase 2 IPSEC parameters, routes for the traffic to be routed from tunnel.
Hope it helps!
08-07-2021 09:37 AM
Thank you for your solution and support the tunnel is up while add proper proxy id.
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!
