IPSec tunnel creation issue

Reply
Highlighted
L1 Bithead

IPSec tunnel creation issue

Hello all, 

one of our customer is trying to create the IPSec tunnel between PA and Fortigate. When phase 1 is initiating in main mode negotiation failed error and we find error in system logs:

 2020-02-18 14:55:18.010 +0200 [PERR]: { 12: }: Expecting IP address type in main mode, but FQDN.
2020-02-18 14:55:18.010 +0200 [PERR]: { 12: }: 197.157.129.5[500] - 197.243.46.12[500]:(nil) invalid ID payload.
2020-02-18 14:55:18.413 +0200 [PERR]: { 12: }: Expecting IP address type in main mode, but FQDN.
2020-02-18 14:55:18.413 +0200 [PERR]: { 12: }: 197.157.129.5[500] - 197.243.46.12[500]:(nil) invalid ID payload.

 

IKE phase-1 negotiation failed. When pre-shared key is used, peer-ID must be type IP address. Received type FQDN.

 

We checked peer end but they are not configured FQDN so any one having idea about this issue.


Accepted Solutions
Highlighted
L1 Bithead

@Abdul_Razaq 

Thanks for your mail.

Finally we find the issue. In peer end device (Fortigate) there is one option called local ID its optional but they gave some value because of this we faced this error, after removing that local ID value tunnel came up and working fine.

 

Thanks everyone...

View solution in original post


All Replies
Highlighted
L6 Presenter

@Logesh How peer IP is configured at palo alto end?? 

 

For FQDN based peer ID, palo alto will only accept it when tunnel mode is set to aggressive mode.

 

With main mode, you will get such errors.

 

Hope it helps!

 

Mayur



Mayur
Highlighted
L1 Bithead

Hi Mayur,

 

Thanks for your info and i am aware this error when we are using FQDN in main mode but here we are not using FQDN.

We have configured tunnel with IP address only.

 

Regards,

Logesh S 

Highlighted
L6 Presenter

@Logesh ,

 

Can you please cross verify configuration at peer end? As error clearly showing 'peer-ID must be type IP address. Received type FQDN'.

 

Mayur



Mayur
Highlighted
L1 Bithead

@mayur

We checked both side and peer end also they configured with IP only.

Highlighted
Cyber Elite

Hello,

The logs on the receiver device should show the logs as to why it was denied/rejected. 

Regards,

Highlighted
L1 Bithead

@OtakarKlier : Thanks and we informed them to check peer end device.

Highlighted
L4 Transporter

Hi @Logesh ,

 

The error look like you have configured peer identification in palo alto IKE gateway configuration to IP address of peer. but the peer is sending a FQDN. You can check the peer identification config in the remote and local device to make sure those are matching.

Highlighted
L1 Bithead

@Abdul_Razaq 

Thanks for your mail.

Finally we find the issue. In peer end device (Fortigate) there is one option called local ID its optional but they gave some value because of this we faced this error, after removing that local ID value tunnel came up and working fine.

 

Thanks everyone...

View solution in original post

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!