Ipsec Proxy_id configuration issue

Reply
Highlighted

Ipsec Proxy_id configuration issue

Hi Team,

 

 I'm not able to configure two separate proxy id in PA-3020 firewall. If I configure either the tunnel goes down or one of the proxy configured second is not working. 

 

Ipsec tunnel is IKEV2 between sonicwall and PA-3020.

I'm getting error "ikev2 child sa negotiation failed when processing traffic selector..."

 

 

 

vpn.JPG

 

 

 

L7 Applicator

Re: Ipsec Proxy_id configuration issue

@Venkatesan_radhakrishnan,

That text is really small to attempt to read, but it looks like the primary messages are due to failing to negotiate due to a lack of IKE payload. I'd verify that you have the proxy IDs configured correctly on both peers and that your IPSec Crypto actually match up. 

Re: Ipsec Proxy_id configuration issue

Hi @BPry 

 

This is the error, i'm getting once after configuring the second proxy tunnel, Whereas the the first configured proxy tunnel is working fine.

 

IKEv2 child SA negotiation failed when processing traffic selector. cannot find matching IPSec tunnel for received traffic selector. received local TS: 172.26.51.0-172.26.51.255 protocol 0 port 0-65535, received remote TS: 172.30.52.0-172.30.52.255 protocol 0 port 0-65535.

 

Regards

Venky

L4 Transporter

Re: Ipsec Proxy_id configuration issue

@Venkatesan_radhakrishnan,

 

You need to verify the Phase2 setting on both devices - Sonicwall and Palo Alto.

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 Live Community as a whole!

The Live Community thanks you for your participation!