Post reply

Multiple Availability Group Listeners - best practice to define ports?

  • January 20, 2014 at 6:46 am

    #288613

    Hi,

    We have recently implemented our first 2012 AlwaysOn environment which comprises of 4 nodes (2 x 2 SQL Clustered instances in each DC) which we are not using autofailover on due to them being FCI's..

    We have configured our first SQL instance in an AG with an AG Listener on port 1433 (default) and set up read only routing url and list so reporting can be done from the secondary..

    All is working ok but we have a second SQL instance (prod and dr) soon to be migrated onto the same cluster and wish to create a new AG and AG Listener to function exactly like the existing one does..

    My question is, when i set up the AG on the new SQL instance can i use port 1433 for the new listener for that AG also or will it cause conflicts? And do people have a set or group of port ranges they try and use or avoid for HA endpoints \ SQL instances \ AG listeners?

    Thanks in advance for any feedback people have with their own configurations and how they have set up their own environments 🙂

  • January 20, 2014 at 7:04 am

    #1681525

    your setup is not clear from your description

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

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

  • January 20, 2014 at 7:18 am

    #1681532

    many apologies Perry..

    hope this makes more sense..

    we have 4 nodes in windows cluster (srv1,srv,2 srv3,srv4)

    srv1,srv2 is where SQL FCI - 'SQL-FIRST' reside in Datacentre 1 (primary active instance)

    srv3,srv4 is where SQL FCI - 'SQL-FIRSTDR' reside in Datacentre 2 (secondary readonly instance)

    have AGroup (AG-FIRST) set up from Instance 1 to Instance 2 with readable secondary..

    Have AGroup Listener set up on port 1433 where clients connect into and also routes read only workload through to readable secondary..

    All works ok, however there are soon to be an availability group and AG listener set up for other FCI's on the cluster nodes, eg

    srv1,srv2 is where SQL FCI - 'SQL-SECOND' reside in Datacentre 1 (primary active instance)

    srv3,srv4 is where SQL FCI - 'SQL-SECONDDR' reside in Datacentre 2 (secondary readonly instance)

    AGroup (AG-SECOND)..

    so want to know if using port 1433 would cause problems if used for 2 seperate AG Listeners (AG-FIRST and AG_SECOND) and if there are specific ports they do us for listeners..

  • January 20, 2014 at 7:30 am

    #1681540

    Even though the combination of the IP address and port number are unique, I would avoid using the std port number for the listener, I prefer to assign a free tcp port number and use that for the listener connection.

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

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

  • January 20, 2014 at 7:34 am

    #1681541

    thanks Perry, exactly what i was hoping to hear and how we will implement the next one..

    thanks again and apologies for not being clear on initial post..:-)

Viewing 5 posts - 1 through 5 (of 5 total)

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