I am creating a Cluster in Windows with 3 nodes using Windows 2008R2 64bits in preparation of creating a AlwaysOn Group for SQL 2012 Server after that.
I got a little problem with the IPs (conflicting) after I have created a cluster and wonder if someone could suggest what is the best practice to do that.
I've followed 'Create a New Faiover Cluster'
http://technet.microsoft.com/en-us/library/cc755129.aspx
using the Faiover Cluster Manager to create a cluster. I loved this tool. But unfortunately, after the 3 nodes successfully added and a new cluster is created, I got a Window's message saying that there is an IP conflict with the other computer.
After working our network adminstration, it turns out that in the network setting on each node,
the IP number generated after the Cluster is not the one that is assigned within the range by the DNCP server. The IP in Ethernet adapter Local Area Connection section is ok, unchanged.
It is the one under the 'Ethernet adaptor Local Area Connection* 10' of Microsoft Failover Cluster Virtual Adapter showing a dummy '169....'.
From what our network administrator told me, it is possible that we ran out of/use up the range assigned. So, I am now given three brand new IP numbers to use for this clustering.
But I am not sure how to use it to incorporate when I run the wizard in Failover Cluster Manager again, because it does not ask. So, my question is, what is the best approach to tell the cluster manager to use these new IP numbers. I have document
link http://technet.microsoft.com/en-us/library/ms190460.aspx to show me to change the IP number after the cluster is created. I wonder if this is the best practice or right way to
do that.
Thank you.
Note: All 3 three has its IP 'reserverd', so they don't get changed or expired on each computer before the clustering set up. When all goes well, I will get new hardware with static IPs and if my assumption is correct, I hope it will eliminate the issue I am experiencing.
Martin
Martin Ng