While planning to configure always on availability group for first time on a multi subnet cluster found following use articles, it provides clear picture in terms of design and architecture, our requirement was to build SQL 2012 cluster on DC1 along with a reporting standalone SQL instance in same DC1, along with it, we want to have DR solution in DC2 where two standalone SQL instances are present on their respective server, to achieve this configuration following articles helped,
Following article highlights Microsoft instructions on configuring Windows multi subnet cluster for Always ON availability groups,
https://msdn.microsoft.com/en-us/library/hh781257.aspx
Below are highlighted important page numbers for easy reference,
Page number 11, this diagram talks about 1 windows cluster in 2 different subnets where the A1 and A2 are in a SQL Failover cluster and rest of the nodes A3, B1, B2 in Standalone. Exactly the same way we want it for our environment. It uses FileShare Witness as optional which is a best practice to have one.
Then refer to Page 15 to 20 to understand how Quorum voting works and how majority decide.
Link for read-only configuration of AlwaysOn can be found here https://msdn.microsoft.com/en-us/library/jj542414.aspx
Detailed ports to be opened:
However, check the article below http://dsfnet.blogspot.ca/2013/04/windows-server-clustering-sql-server.html#!/2013/04/windows-server-clustering-sql-server.html this is not a Microsoft article. Infrastructure team can always review and verify if it is correct or if we need to add or remove any from the list.
Hope this helps.
