topic Re: Ipsec Proxy_id configuration issue in General Topics

Ipsec Proxy_id configuration issue

Venkatesan_radhakrishnan — Sun, 21 Jul 2019 16:40:42 GMT

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..."

Re: Ipsec Proxy_id configuration issue

BPry — Mon, 22 Jul 2019 01:14:09 GMT

@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

Venkatesan_radhakrishnan — Mon, 22 Jul 2019 06:29:00 GMT

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

Re: Ipsec Proxy_id configuration issue

aleksandar.astardzhiev — Mon, 22 Jul 2019 07:39:37 GMT

@Venkatesan_radhakrishnan,

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