Windows Server 2019 non-owner node cannot see Cluster Name or IP

%3CLINGO-SUB%20id%3D%22lingo-sub-1430740%22%20slang%3D%22en-US%22%3EWindows%20Server%202019%20non-owner%20node%20cannot%20see%20Cluster%20Name%20or%20IP%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1430740%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20trying%20to%20build%20a%20SQL%20Server%20AlwaysOn%20Availability%20Group%20with%202%20nodes%20in%20Azure.%20I%20have%20created%202%20SQL%20Server%20VMs%20and%20Managed%20to%20create%20a%20Cluster%20with%20both%20Nodes%20member%20of%20that%20cluster.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20followed%20the%20steps%20in%20this%20Article%20of%20building%20the%20Windows%20Clusters%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-sql%2Fvirtual-machines%2Fwindows%2Favailability-group-manually-configure-tutorial%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-sql%2Fvirtual-machines%2Fwindows%2Favailability-group-manually-configure-tutorial%3C%2FA%3E%3C%2FP%3E%3CP%3Ewith%201%20significant%20change%2C%20I%20used%20powershell%20to%20create%20the%20cluster.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%20color%3D%22%230000FF%22%3ENew-Cluster%20-Name%20SQLClusterName%20-Node%20(%22SQLNode1%22%2C%22SQLNode2%22)%20%E2%80%93StaticAddress%20172.100.10.100%20-NoStorage%20-ManagementPointNetworkType%20Singleton%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBecause%20if%20I%20used%20Failover%20Cluster%20Manager%20to%20build%20the%20cluster%20it%20did%20not%20created%20Cluster%20Core%20Resources%20and%20I%20did%20not%20gave%20me%20the%20option%20to%20select%20an%20IP%20for%20the%20cluster.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyway%2C%20once%20the%20cluster%20has%20been%20configured%2C%20I%20tried%20to%20configure%20AlwaysOn%26nbsp%3BAvailability%20Group%2C%20but%20the%20wizard%20fails%20to%20create%20Always%20on%20Availability%20Group%2C%20complains%20about%20it%20cannot%20connect%20to%20the%20Cluster.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20went%20on%20both%20Nodes%20and%20what%20I%20have%20realised%20is%20that%20I%20can%20ping%20to%20the%20Cluster%20Name%20or%20IP%20and%20get%20a%20response%20only%20from%20the%20Owner%20Node.%20From%20the%20cluster%20Non-owner%20node%20I%20could%20not%20ping%20the%20cluster%20name%20or%20IP.%20If%20I%20failover%20the%20cluster%20to%20the%202nd%20node%20the%26nbsp%3B%3CSPAN%3EI%20ping%20behaviour%26nbsp%3Bwill%20be%20contra%20versa.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EHas%20everyone%20else%20experienced%20this%20issue%3F%20Is%20so%2C%20how%20you%20managed%20to%20resolve%20it%3F%20Any%20help%20or%20a%20pointer%20in%20the%20right%20direction%20is%20much%20appreciated.%20Thanks%20in%20advance.%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

I am trying to build a SQL Server AlwaysOn Availability Group with 2 nodes in Azure. I have created 2 SQL Server VMs and Managed to create a Cluster with both Nodes member of that cluster. 

 

I have followed the steps in this Article of building the Windows Clusters https://docs.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/availability-group-manuall...

with 1 significant change, I used powershell to create the cluster. 

 

New-Cluster -Name SQLClusterName -Node ("SQLNode1","SQLNode2") –StaticAddress 172.100.10.100 -NoStorage -ManagementPointNetworkType Singleton

 

Because if I used Failover Cluster Manager to build the cluster it did not created Cluster Core Resources and I did not gave me the option to select an IP for the cluster. 

 

Anyway, once the cluster has been configured, I tried to configure AlwaysOn Availability Group, but the wizard fails to create Always on Availability Group, complains about it cannot connect to the Cluster. 

 

I went on both Nodes and what I have realised is that I can ping to the Cluster Name or IP and get a response only from the Owner Node. From the cluster Non-owner node I could not ping the cluster name or IP. If I failover the cluster to the 2nd node the I ping behaviour will be contra versa.

 

Has everyone else experienced this issue? Is so, how you managed to resolve it? Any help or a pointer in the right direction is much appreciated. Thanks in advance.

 

0 Replies