January 17, 2012 at 10:57 pm
Hi,
How many IP address include in 2 node active -passive cluster .....
i answered Five ........2 for private network
2 for public network ......
1 for virtual server which used to connect application
is this is correct or not please confirm
Regards,
Shivrudra W
January 17, 2012 at 11:19 pm
Shivrudra (1/17/2012)
Hi,How many IP address include in 2 node active -passive cluster .....
i answered Five ........2 for private network
2 for public network ......
1 for virtual server which used to connect application
is this is correct or not please confirm
you missed the IP's for msdtc and SQL Cluster IP.
I assume the "virtual server" you mentioned is the Windows Cluster IP.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
January 17, 2012 at 11:21 pm
1 for msdtc
1 for virtual name
2 private ip for healthcheck for 2 server
2 public ip (optional)
----------
Ashish
January 17, 2012 at 11:22 pm
yes ....i mean windows cluster ip is virtual server ip....
is there compulsory to use msdtc in cluster
Regards,
Shivrudra W
January 17, 2012 at 11:47 pm
yes. So that msdtc can maintain the database in consistent state during failover.
----------
Ashish
January 18, 2012 at 12:04 am
ok....thanks
Regards,
Shivrudra W
February 3, 2012 at 8:14 pm
I have two questions in short.
1. How many ip addresses are there for an Active-Active Cluster?
2. Suppose there are 8 nodes in my cluster. How many ips we need in this case?
Thanks,
Rajeev Ramachandran
February 5, 2012 at 9:33 am
Shivrudra (1/17/2012)
Hi,How many IP address include in 2 node active -passive cluster .....
i answered Five ........2 for private network
2 for public network ......
1 for virtual server which used to connect application
is this is correct or not please confirm
Based on a 2 node single instance cluster, you need the following
1 x windows cluster ip
1 x SQL server instance virtual ip
1 x MSDTC virtual ip
1 x public ip for each node (although you may team multiple NICs)
1 x heartbeat network
In fact if this is a windows 2008 cluster you don't even need a heartbeat interface. So you could team all available NICs for your public interface.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 6, 2012 at 4:42 am
Don't forget that if you are running on Windows 2008 or above, ther are useful performance benefits from having one MSDTC instance per clustered node if you are running any form of active/active cluster.
If the MSDTC instance is online to the node making the majority of requests to MSDTC, then these operations are memory only. If MSDTC is not online then you have a network delay.
The end result is you should consider creating a MSDTC cluster for each active node, with each MSDTC cluster having its own IP address.
For more details see http://blogs.technet.com/b/askcore/archive/2009/02/18/how-to-configure-multiple-instances-of-distributed-transaction-coordinator-dtc-on-a-windows-server-failover-cluster-2008.aspx
FineBuild allows you to configure a SQL cluster with eithr a single MSDTC instance or use multiple instances.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
February 6, 2012 at 5:14 am
EdVassie (2/6/2012)
Don't forget that if you are running on Windows 2008 or above, ther are useful performance benefits from having one MSDTC instance per clustered node if you are running any form of active/active cluster.If the MSDTC instance is online to the node making the majority of requests to MSDTC, then these operations are memory only. If MSDTC is not online then you have a network delay.
The end result is you should consider creating a MSDTC cluster for each active node, with each MSDTC cluster having its own IP address.
For more details see http://blogs.technet.com/b/askcore/archive/2009/02/18/how-to-configure-multiple-instances-of-distributed-transaction-coordinator-dtc-on-a-windows-server-failover-cluster-2008.aspx
FineBuild allows you to configure a SQL cluster with eithr a single MSDTC instance or use multiple instances.
Thank you for mentioning this.
One of the double checks to be performed even today :w00t:
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
March 15, 2016 at 7:57 am
I know this is a old thread but for conclusion... how many IP addresses are required?
March 16, 2016 at 3:14 am
The number of IP addresses you need depends on what you want to do and how your environment is built and what IP protocols you are using. The number of addresses you need will be the same regardless of if your cluster is Active/Active or Active/Passive.
For W2012 and above each node in the cluster will normally have an IPv4 and an IPv6 address unless you have specifically disabled IPv6. Most places that only assign IPv4 addresses will let DHCP assign the IPv6 address so you do not have to assign these yourself.
You also need to think about port numbers, particularly if you plan to use Kerberos (you should be planning to use Kerberos!). If you have both a default and named instance clusters for the SQL DB engine then each instance needs its own port. This is because you need a port-specific SPN for each instance to allow Kerberos authentication.
You may need some or all out of the list below. If your site standard is to publish both IPv4 and IPv6 addresses then you need 1 address for each protocol.
For each cluster node:
1 address for each cluster node for client traffic
1 address for each cluster node for data traffic (depending on how your storage is configured)
If you need multiple NICs to get the required throughput then consider teaming the NICs (1 client team, 1 storage team) rather than using a dedicated IP address for each NIC.
Some sites will split high-priority and low-priority data traffic into separate NIC teams each with their own IP address. This allows backups to write to disk without impacting IO for your critical DBs.
For the Windows cluster:
1 address for client traffic
1 address for cluster handshake traffic
For SQL Server:
1 address for each SQL DB engine cluster
1 address for each MSDTC cluster (MSDTC can be added as a service within the DB engine cluster and share the IP, or set up as its own cluster with its own IP)
1 address for each Availability Group listener
1 address for each Analysis Services cluster
Other components:
1 address for SSRS cluster if you decide to cluster SSRS
1 address for each Master Data Services cluster if you decide to cluster MDS
If you use SQL FineBuild to install your clusters, by default it will take the Windows Cluster IP and find the next highest unused IP address for each of the SQL Server, MSDTC and SSRS clusters. However if you need to use specific IP addresses with FineBuild these can be supplied as parameters.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply