https://live.paloaltonetworks.com/t5/next-generation-firewall/ike-phase-1-negotiation-is-failed-as-initiator-aggressive-mode/m-p/582019#M2912 <P>to troubleshoot phase1 it's ideal if you have access to the logs of the receiving end, as the initiator will have very minimal logging available</P> <P>if you can't access the remote side, see if they are able to initiate a connection so you can see which part in the negotiation fails</P> <P>most likely it's a problem with the ID or the available cipher pairs between the two peers</P> Thu, 28 Mar 2024 09:50:37 GMT reaper 2024-03-28T09:50:37Z https://live.paloaltonetworks.com/t5/next-generation-firewall/ike-phase-1-negotiation-is-failed-as-initiator-aggressive-mode/m-p/581966#M2908 <P>Hi All,<BR /><BR /><SPAN>We are facing an issue where IKE phase-1 negotiation has failed as the initiator in aggressive mode. The SA (Security Association) has failed between 199.X.X.X [500] and 162.X.X.X [500], with the cookie: fa14dad50518163e:0000000000. Can someone else please assist me in resolving this?</SPAN></P> Thu, 28 Mar 2024 01:17:48 GMT https://live.paloaltonetworks.com/t5/next-generation-firewall/ike-phase-1-negotiation-is-failed-as-initiator-aggressive-mode/m-p/581966#M2908 ShaikAbdul 2024-03-28T01:17:48Z https://live.paloaltonetworks.com/t5/next-generation-firewall/ike-phase-1-negotiation-is-failed-as-initiator-aggressive-mode/m-p/582019#M2912 <P>to troubleshoot phase1 it's ideal if you have access to the logs of the receiving end, as the initiator will have very minimal logging available</P> <P>if you can't access the remote side, see if they are able to initiate a connection so you can see which part in the negotiation fails</P> <P>most likely it's a problem with the ID or the available cipher pairs between the two peers</P> Thu, 28 Mar 2024 09:50:37 GMT https://live.paloaltonetworks.com/t5/next-generation-firewall/ike-phase-1-negotiation-is-failed-as-initiator-aggressive-mode/m-p/582019#M2912 reaper 2024-03-28T09:50:37Z