When attempting to add a second SQL VM to a SQL VM Group getting a ping failure

Question

I can create the SQL VM Group successfully, add the first SQL VM to it and everything works as expected there. The cluster is created and the node is added to it. However, when I attempt to add a second SQL VM I get this error:

Error code: NodeUnreachable, Message: An exception occurred during a Ping request. An exception occurred during a Ping request. No such host is known.

I can ping both the cluster and first SQL VM from the second SQL VM.

I created the SQL VM Group with New-AzSqlVmGroup and am using Update-AzSqlVm to add the VMs to the group. Failover Clustering does get installed on all VMs.

I also manually added the second SQL VM to the cluster through Failover Cluster manager and that worked fine. It appears something is going on with Update-AzSqlVm that is failing to work properly.

Both VMs are in East US. One is in AZ 1 and the other is in AZ 3. Each is in a different subnet and the SQL VM Group is set to MultiSubnet for the cluster subnet type.

Why am I getting this ping failure?

Answer 1

Hi @Rob Lee

I can ping both the cluster and first SQL VM from the second SQL VM.

That is quite weird, have you double checked the hostname?

Besides, if you're using a multi-subnet cluster, please configure as a multi-subnet cluster and set the IP address resource dependency to OR.

See: SQL Server Multi-Subnet Clustering (SQL Server)

Best regards,

Cosmog

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Answer 2

Duplicate post

Answer 3

Duplicate post

Answer 4

Figured out the issue. Update-AzSqlVm takes a name as a parameter. This name is the VM name and has no relevance outside of being the resource name. I'm sure it's pertinent to the IaaS agent but internal to Windows it is meaningless. When adding the second node to the cluster, it is trying to use the VM name instead of computer name and thus failing to find it. I suppose MS expects people to either name the VM and Computer the same or add the VM name to DNS. Neither of these options is favorable and it really seems like this is a huge bug in Update-AzSqlVm.