Azure site to site VPN connection status unknown

Anand Raj 1 Reputation point
2022-03-04T16:08:29.9+00:00

Hello Team,

I'm trying to create site to site VPN. The client is using fortigate.

I have followed this document and created the VPN gateway, local gateway resources and connections,

https://docs.fortinet.com/document/fortigate/7.0.5/administration-guide/255100/ipsec-vpn-to-azure-with-virtual-network-gateway

I have recommended the same config on fortigate end as well.

Still I see connection as Unknown status.

What else need to be corrected. I tried all vpn troubleshooting guide but could not find any solutions.

Thanks
Anand.

Azure VPN Gateway
Azure VPN Gateway
An Azure service that enables the connection of on-premises networks to Azure through site-to-site virtual private networks.
1,404 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. ChaitanyaNaykodi-MSFT 23,426 Reputation points Microsoft Employee
    2022-03-05T03:13:48.227+00:00

    Hello @Anand Raj , welcome to the Microsoft Q&A forum.

    Just confirming that you have followed this troubleshooting guide and it did not help resolve the issue. If it helps you can follow below mentioned additional troubleshooting steps to further debug this issue.

    1. Troubleshoot Azure VPN Gateway using diagnostic logs, you can troubleshoot multiple VPN gateway-related events including configuration activity, VPN Tunnel connectivity.
    2. Perform a packet capture on your S2S VPN to help pinpoint this issue.

    Hope this helps! Please let us know if this does not help resolve the issue. Thank you!

    0 comments No comments

  2. Anand Raj 1 Reputation point
    2022-03-13T06:45:56.707+00:00

    Hello Chaitanya,

    Thanks for the response.

    Since the status of the connection is Unknown, Diagnostic logs do not have many pieces of information. All it has was the CPU status alone used to troubleshoot.

    Current CPU Usage : 0 %
    Current Memory Available: 5030 MBs

    I fix the issue, by specifying the address space in the local network gateway. Since Address space was not mandatory, I left it blank.

    That was causing me the issue.

    Thanks
    Anand.

    0 comments No comments