Can't connect Azure S2S VPN to Huawei Eudemon1000E-G8

Question

We are trying to integrate with a third party using Azure S2S VPN on our end. The third party's device is Huawei Eudemon1000E-G8 with a firmware version of Eudemon1000E-G V600R007C20SPC200.

After configuration on both sides, the status is "Not Connected" on our end and stuck on "Negotiating" on third party's end on IKE V1.

We tried downloading the VPN configuration for the third party to use on Azure, but Huawei device is not among device vendor. (Screenshot below)

Below is a screenshot of the configuration on our end.

P.S.

The third party gave us list of required parameters. "Authentication Algorithm" is among parameters that is required by the third party, but on Azure, there is no place to select Authentication Algorithm. The Authentication Algorithm options from the third party includes MD5, SHA1, SHA2-256, SHA2-384, SHA2-512, SM3.

This is different from Authentication Method(Pre Shared Key) which we've already agreed upon with the third party.

Thanks in advance.

Answer 1

Hi @Jubril Edun

Thanks for reaching Microsoft Azure QnA Forum.
Hope you have already followed the article : https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-troubleshoot-site-to-site-cannot-connect

1. You are not finding your VPN device in the Azure portal as that is not validated by Azure Product group for the VPN connection, but that doesn't mean that you will not be able to establish the VPN connectivity. Here, is the list of validated VPN devices: https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-vpn-devices
2. Based on your provided screenshot the authentication method configured in Azure VPN connection is SHA-256.

Could you please confirm below.

1. What is the Ike version does on-premises device support?
2. What is the Ike version configured in Azure Virtual network connection? Possibly there is an Ike version mismatch.
   However, if above is not the case.
   You may have to check the Ike logs at on-premises VPN device to see in which stage of Ike negotiation it is failing, and which particular parameter is not matching.

You can also raise a support case to troubleshoot the issue, and they will have access to check the logs and direct you towards solution. If you cannot involve Azure support, you can use the Azure network watcher for VPN troubleshooting. Here, is the article that can guide you on how to us it.
https://learn.microsoft.com/en-us/azure/network-watcher/network-watcher-diagnose-on-premises-connectivity

Please let me know if this helps or you need further support.