Forum Discussion
2 node failover cluster cant ping cluster network name from not owner node
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 ?
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-manually-configure-tutorial
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.