This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 31%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECJ%3C/text%3E%3C/svg%3E)
Hello Team,
I am configuring SQL server 2019 enterprise edition with AOAG ( without Cluster).
SQL AOAG installation & configuration is done. Failover is happening properly.
When i am trying to configure SQL listener ( Object creation in AD and mapping in DNS with different IP is already done), it is creating the listener in SSMS but when i am trying to connect with deafult port, it is throwing an error.
Listener creation is done on the primary replica.
Kindly advise
And what is the error message?
Have you set up the listener with a different port from the instance itself?
Keep in mind that after a failover, you will need to update the DNS information for the listener.
Yes,, Listener is configured with different IP & port
Both Listener (X.26.92.8) and Server IP (XX.26.92.6)are in same VLN then ideally communication should be allowed within vLan,
I got that also checked with my network team and they are saying the same.
Now, what should be next step of troubleshooting
So listener and primary have different IP-addresses. Are you sure that this is supposed to work with a clusterless AG? Being mainly a developer, AGs is not really my expertise, but it is my impression that to have a listener with a clusterless AG, the listener needs to have the same IP-address as the primary. (Which means that after a failover, you need to drop and recreate the listener and update the DNS so that the listener points to the new primary.)
There is requirement for having different IP for Listener which is not matching with the pre-requisite for the clusterless SQL AOAG. ( don't know why there is requirement for different IP for listener).
We have gone ahead with Windows Cluster with SQL AOAG including listener to fulfill the requirement.
straight configuration ;
It certainly makes sense to have a specific IP for the listener. If you are looking for an HA solution, you don't want to update the IP address for the listener on failover. But a clusterless AG is not an HA solution, nor is intended to be. it can still serve as a DR solution, though.
Going with a cluster seems to be a good call.