Creating Listeners in a multi instance cluster

  • Hi,

    I have the default instance with a listener using IP:10.10.10.10 port 1433. In my second instance after creating the availability group, I want to create a Listener using the same 10.10.10.10 and Port:6001. Unfortunately I am getting error 5057.

    I have the feeling that the only way is to use a different IP and different port than the one already used, and for subsequent Listeners, other IPs and ports. In AD Listeners are actually create as Computers.

    Any advice?

    Thank you,

    dg

  • You'll need an IP for each subnet. You can use the same port. (In fact, I don't think it is possible to use a different port per subnet, but I've never tried)

    The Redneck DBA

  • The only way it worked was to use a different IP and a different port. It did not allow 1433 which is strange considering that is a different IP, which was not used before. When attempting to use 1433 with the new IP, it allow the operation to finish but advised to change the port with ALTER command.

  • from what I'm reading you're creating a new listener each time and not adding extra subnet IPs to an existing listener.

    Just add each subnet IP to the existing listener configuration

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • So basically I require only one listener no matter how many SQL Server instances I have. I can use the first listener from the Default instance to connect to every other instance on the SQL Server. AGL-Default\InstanceName)

    I do not have multiple subnets, just one.

  • each new availability group would have it's own listener and would require a unique virtual computername and IP address

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • yes, you are right, I need a listener for every Availability Group when accessing a contained databases with a contained database user.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply