question

NM-0091 avatar image
1 Vote"
NM-0091 asked ShreeNiraula commented

Not able to ping SQL Cluster

Hello,

I am unable to ping or connect to my SQL cluster. My cluster is a multi site failover cluster.

Below is my configuration -

  1. Environment is setup in Azure

  2. I have 2 Windows Server 2019 acting as Cluster nodes.

  3. IP Address - Node 1 - 10.1.100.10, Node 2 - 10.2.100.10.

  4. Installed failover cluster role, added the storage and created the cluster.

  5. ICMP allowed through NSG, TCP Port 1433 port also allowed.

  6. Cluster is running fine, all my other machine can ping these nodes and vice versa.

  7. Installed SQL Server 2019 failover cluster instance on both the nodes.

  8. Name of SQL Instance - SQLCluster

  9. IP Address of SQL Instance - Node 1 - 10.1.100.20, Node 2 - 10.2.100.20 (Multi side failover configuration)

  10. Failover working fine, tested on both the nodes.

  11. I can access the instance via SQL server management studio installed on both the nodes.

Problems -
1. I cant ping the SQL instance (SQLCLUSTER)
2. NSLookup shows both the ip address - 10.1.100.20, 10.2.100.20
3. If Node1 is the active node then ping to this only work from within the node and not from other node.
4. Ping is not working from any other server.

I have checked all the network and DNS configuration all working fine and setup correctly. Also, i have tried to connect from outside the nodes using the option MultiSubnetFailove=True but it also did not worked since there is no reply to ping.

This is the second time i tried this. Earlier i created the cluster but the IP address was bit conflicting so, have rebuilt it but getting the same results again.

Experts please suggest.

Thanks,
NM

sql-server-generalwindows-server-clustering
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi Guys, I am also facing the same issue, anyone finds the solution for this setup on Azure Cluster VMs. Thanks

1 Vote 1 ·
TomPhillips-1744 avatar image
1 Vote"
TomPhillips-1744 answered NM-0091 commented

In a failover cluster, there are multiple IP addresses. You do not connect via the IP addresses.

You connect to the cluster using the "network name". This is a shared resource and points to the active node. Only 1 node at a time is "active". So you cannot connect to the 2nd SQL Server until it becomes "active".

· 7
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Yes i understand that but i should be able to connect to the network name and should be able to ping the network name /active node...Right.

1 Vote 1 ·

The only port active on the SQLCluster IP would be 1433. The SQL Server "network name" is not designed for full network access, only port 1433 (or whatever you defined).

0 Votes 0 ·

so, if i am connecting using SSMS then would not it connect to 1433 by default ? or do i need to specify the port and connect ?

1 Vote 1 ·
Show more comments
ShreeNiraula avatar image
0 Votes"
ShreeNiraula answered ShreeNiraula commented

@NM-0091 I am facing the same issue, can you help me to fix this?

· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @NM-0091 Were you able to create a support ticket.? I will suggest doing so. Let us know if you don't have a support plan.

Regards,
Oury

0 Votes 0 ·

@OuryBa-MSFT , can you please help me to fix the same issue?

0 Votes 0 ·

@ShreeNiraula, are you trying to ping cluster from virtual machines or IP?

Regards,
Oury

0 Votes 0 ·
Show more comments
OuryBa-MSFT avatar image
0 Votes"
OuryBa-MSFT answered NM-0091 commented

@NM-0091 Thank you for posting your question.

Make sure that TCP/IP is enabled as a client protocol on the application server. For more information, see Configure client protocols. On application servers where you don't have SQL tools installed, verify that TCP/IP is enabled by running cliconfg.exe (SQL Server Client Network utility).

Check the application's connection string to make sure it's configured correctly. For example, make sure that the connection string specifies the correct port (1433) and fully qualified server name. See Get connection information.

Try increasing the connection timeout value. We recommend using a connection timeout of at least 30 seconds.

Test the connectivity between the application server and the Azure SQL Database by using SQL Server management Studio (SSMS), a UDL file, ping, or telnet. For more information, see Troubleshooting connectivity issues and Diagnostics for connectivity issues. Please let us know if that solve your problem. Thanks


· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hello @NM-0091 Please do let us know if the answer above helped. Please feel free to reach if you have further query. Thanks

1 Vote 1 ·

Hello thanks for the reply..I mostly tried all the options mentioned by you but i am still not able to connect.

Protocol, DNS , networking, firewall seems to be set all fine.

TCP/IP -
90877-client-protocol.png


0 Votes 0 ·
client-protocol.png (10.2 KiB)

Hello @NM-0091 I have added the right team for more traction. They will look into it. Thanks

0 Votes 0 ·

Any further update on this ?

0 Votes 0 ·