February 22, 2022 at 2:35 pm
Hi all
Hope someone can assist with my issue. I have a two node cluster running SQL Server 2019 ENT Edition CU14 and the nodes are on different subnets. Always On has been added and working fine however I can't add the SQL Listener, keep getting the following error:
"None of the IP addresses configured for the availability group listener can be hosted by the server 'xxxxxxxxxx'.
Either configure a public cluster network on which one of the specified IP addresses can be hosted, or add another listener IP address which can be hosted on a public cluster network for this server."
The Listener VNN has been created and exists in AD. I can ping it from both nodes and have tried creating it from both Primary and Secondary nodes. I've restarted SQL Server Services AND rebooted both VMs but still no joy.
The Wintel guy checked the cluster and assures me all is healthy, Cluster Object has FULL permissions on the SQL LIstener but still no joy. Of course the IP address associated with the Listener is not being used by another object and there are no firewalls between the nodes and rest of network so it isn't a port issue (using port 1433).
I've checked MSDN and other SQL forums and followed the suggestions but no matter what I do still always get the above error so any further suggestions or advice would be much appreciated!
Thanks in advance.
Ali
February 23, 2022 at 3:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
February 23, 2022 at 4:13 pm
Is the account being used to create this a domain admin?
You are not re-using an IP that was previously in use, correct?
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
February 23, 2022 at 4:32 pm
My _DBA account is local admin on both nodes but not domain admin, I've been informed this isn't a requirement but could be wrong.
And the IP (well, two IPs really, one for each subnet) have not been previously used or in use currently by another object.
However, since the original issue a new problem has surfaced, I'm awaiting the Wintel / Network Admin to respond; I now can't ping the pre-staged SQL Listener VNN or IP from either node (host unreachable).
Once this is resolved I will try adding it once more, if that doesn't work my thought was to ask him to remove the VNN and try again, see if it can be created 'from scratch' during the Add Listener process.
Cheers
Ali
February 23, 2022 at 4:48 pm
My _DBA account is local admin on both nodes but not domain admin, I've been informed this isn't a requirement but could be wrong.
And the IP (well, two IPs really, one for each subnet) have not been previously used or in use currently by another object.
However, since the original issue a new problem has surfaced, I'm awaiting the Wintel / Network Admin to respond; I now can't ping the pre-staged SQL Listener VNN or IP from either node (host unreachable).
Once this is resolved I will try adding it once more, if that doesn't work my thought was to ask him to remove the VNN and try again, see if it can be created 'from scratch' during the Add Listener process.
Cheers
Ali
No, you need to be a domain admin
Why do you need 2 ip's for the listener? You are not trying to use the actual servers IP's to create the listener, correct?
As an example:
Server 1 = 10.1.1.1
Server2 = 20.1.1.1
Listener = 10.1.1.2, 20.1.1.2
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
February 23, 2022 at 5:04 pm
I have two IPs available to me, both are linked to the one VNN and they aren't the server IPs. As you know for multi-subnet AOs you can assign two IPs to the Listener, one for each subnet.
But that's a bit of a red herring as I get the error even when trying to add just the one IP that is in the same subnet as the current Primary Replica. The other oddity is when I get that error message it references the OTHER machine, for example:
Server A (Primary Replica), Server B (Secondary Replica)
Trying to add SQL Listener on Server A the error reads "None of the IP addresses configured for the availability group listener can be hosted by the server 'Server B'."
I don't recall ever being added to the Domain Admins when adding SQL Listeners in the past (on earlier versions of SQL Server) but I will ask the Wintel Admin if he can add me tomorrow temporarily OR add him into sysadmin role on the SQL instance and screen-share him trying to add the Listener instead of me if he isn't comfortable upping my privileges.
Cheers
Ali
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply