Mar 07 2018 09:17 AM
Hello
I have 2 node failover cluster based on server 2016 server. node1 is owner of cluster. I cant ping cluster network name only from cluster's owner. So I cant ping cluster name from node2 and on node2 Server Manager shows error to communicate to cluster object. But cluster status is ok. If I change node's owner ping behavior will be contra versa.
I have checked on another cluster, the same.
//Alexander
Mar 07 2018 01:02 PM
Mar 08 2018 11:20 AM
Mar 08 2018 11:14 PM
Mar 26 2018 12:09 PM
Apr 02 2018 01:51 PM
I am having the exact same problem. Has anyone provided any resolution to this problem?
Thanks
Ayaz
Apr 04 2018 12:27 PM - edited Apr 06 2018 07:19 AM
Are you able to ping the cluster name from another pc or server?
Apr 06 2018 03:13 AM
Hi, Alexander.
You may check in the DNS console if the cluster name is registered. If it is not, create an entry (A or AAAA) for it, and clear the DNS client cache.
Cheers
Apr 08 2018 05:59 AM
Sep 06 2018 11:30 AM
Did you ever get this resolved?
Sep 18 2018 04:03 AM
nope
Oct 14 2018 12:52 PM
I have the same issue
there is any update ?
Oct 15 2018 06:41 AM - edited Oct 15 2018 06:41 AM
No resolution in my datacenter. We *think* the issue is a network related issue as the issue impact physical devices and virtual devices. We are engaging a consulting firm to assist with our situation.
Jan 09 2020 07:15 PM
@Dusty Lane - did you manage to find out what caused this?
Jun 01 2020 04:27 AM
@alexander tikhomirov did you ever managed to get this sorted?
May 26 2021 02:30 AM
Hello @alexander tikhomirov ,
I'm facing same issue on production which have windows server 2016 in Azure VMs. with Alwayson availability group configured on it.
Did you get and fix for this ?
May 26 2021 02:52 AM - edited May 26 2021 03:03 AM
@darshansh705 I managed to fix this by enabling HA ports in the Azure Load Balancer (standard Load Balancer). That seems to have fixed the issue.
By the way I have SQL Server 2019 Enterprise on Windows Server 2019.
Set the following Load Balancing rule in the Azure Load Balancer for WFCS.
Setting | Description | Value |
Name | Text | WSFCEndPoint_LBRule |
IP Version | Type of IP to be used | IPv4 |
Frontend IP address | Choose an address | 10.10.xx.xx (WFCSEndPoint) |
HA Ports | Enable LB on all ports | Select (Checked) |
Port | Use the port for the availability group listener | 38888 |
Backend Port | This field is not used when Floating IP is set for direct server return | 38888 |
Backend Pool | Backend pool for Cluster Nodes | SQLPRD_BEP |
Health Probe | The name you specified for the probe | WSFCEndPointProbe |
Session Persistence | Drop down list | None |
Idle Timeout | Minutes to keep a TCP connection open | 4 |
Floating IP (direct server return) |
| Enabled |
The source of this information is this article : https://docs.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/availability-group-manuall...
The article does not talk about HA ports because it is a Standard Azure Load Balancer feature and the article was written using a Basic Azure Load Balancer.