Sunday, 13 August 2023

SQLServer - Always On Availability Group TCP Port and Endpoint Conflicts

 

              Always On Availability Group and SQL Server FCI can have below port conflicts 


Having an availability group with a listener that listen on the same TCP port than the standalone instance on the same process will not result to a TCP port conflict.

Having an availability group with a listener that listen on the same TCP port than the standalone instance on a different process will result to a TCP port conflict. In this case each SQL Server process will attempt to open a socket on the same TCP port and on the same address IP.

Having Multiple availability group  running on the same TCP endpoint port is not a problem because they can open a socket on their distinct IP address. However you can face port conflicts in the case you have multiple  instances on the same node using the same endpoint port ,So in that case you need to change the TCP endpoint port .

Having several SQL Server FCI that listen on the same port is not a problem because they can open a socket on their distinct IP address. However you can face port conflicts in the case you have also a standalone instance installed on one of the cluster node

No comments:

Post a Comment