June 18, 2020 at 3:00 pm
Hi - I setup a new SQL FCI in Azure. Two newly created VMs with SQL 2019 installed. Cluster validates successfully and i configured the Load Balancer per the Microsoft recommendations.
I am able to connect to the SQL FCI from the node it is currently running on (can connect via SSMS or even just ping the IP address). I am unable to connect to or ping the instance from the secondary node. If the instance is moved to node2, the same applies: can connect from node2, but not node1.
Has anyone else run into this? Maybe important, maybe not - I was able to setup a non-clustered SQL instance on a 3rd VM and I have no issues connecting to that instance.
Thanks!
June 19, 2020 at 8:54 am
You talking about a true FCI here shared disk setup? Not an availability group setup?
If it is a FCI shared disk etc then the service is only ever running from NODE1 or NODE2 its never running on both, so you should only be able to connect to it on one of the machines not both
June 26, 2020 at 1:02 am
Browser service running? TCP port 1433 and UDP port 1434 allowed? Let me know.
October 25, 2020 at 12:41 pm
I am having the same problem. i posted this on another post as well. i have SQL 2016 on Windows 2016. i have setup an FCI on Azure with two nodes.
sql browser is running. tcp/1433 and udp/1434 are allowed in windows firewall as well as in the azure network security group. load balancer is configured with the probe. Probe port is opened in NSG as well as the windows firewall.
Load Balancer insights show everything normal, one node up and other down.
but i am unable to connect to the sql from anywhere but the active node. i have tried connecting without configuring the LB as well with LB but unfortunately no success.
October 26, 2020 at 3:30 am
Hi - I setup a new SQL FCI in Azure. Two newly created VMs with SQL 2019 installed. Cluster validates successfully and i configured the Load Balancer per the Microsoft recommendations.
I am able to connect to the SQL FCI from the node it is currently running on (can connect via SSMS or even just ping the IP address). I am unable to connect to or ping the instance from the secondary node. If the instance is moved to node2, the same applies: can connect from node2, but not node1.
Has anyone else run into this? Maybe important, maybe not - I was able to setup a non-clustered SQL instance on a 3rd VM and I have no issues connecting to that instance.
Thanks!
Enable TCP port 1433 and UDP Port 1434 , start SQL Server Browser.
October 26, 2020 at 10:20 am
And also make sure that Azure Load Balancer is configured properly. SQL FCI will not work without the Azure Load Balancer properly configured.
I had the exact same problem, and the issue was Azure Load Balancer.
There is one portion in the documentation that must be done using using powershell on one of the FSI nodes. Please make sure it successfully completes.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply