Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««1234

Creating a 2 Node SQL Server 2008 Virtual Cluster Part 2 Expand / Collapse
Author
Message
Posted Tuesday, October 11, 2011 1:01 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, April 14, 2014 5:49 PM
Points: 2,263, Visits: 3,758
Perry Whittle (10/11/2011)
Try installing the VMWare tools in each of the windows virtual machines, this could be why you don't see the adapters.


Thank you Perry, that was a brilliant suggestion. Yes, I installed the VMWare tools on each of the VMs and now I can see the adapters.

But I have a question. Initially, as I couldn't see the adapters I had configured the Microsoft Loopback Adapter and assigned the static IP addresses. Please let me know how to proceed with this.


Mohammed Moinudheen
Post #1188229
Posted Tuesday, October 11, 2011 4:25 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 1:59 PM
Points: 5,970, Visits: 12,873
mohammed moinudheen (10/11/2011)
But I have a question. Initially, as I couldn't see the adapters I had configured the Microsoft Loopback Adapter and assigned the static IP addresses. Please let me know how to proceed with this.


un assign the IP from the loopback adapter and then remove the adapter itself. The VMWare VMNET virtual switches take care of the network functionality


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

"Ya can't make an omelette without breaking just a few eggs"
Post #1188317
Posted Tuesday, October 11, 2011 7:02 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, April 14, 2014 5:49 PM
Points: 2,263, Visits: 3,758
Perry Whittle (10/9/2011)
For this section create 3 new Windows virtual machines.
1 of them requires just 1 virtual NIC connected to the public network.
The other 2 require 3 virtual NICs each. One connected to public, one connected to iSCSI and the other connected to heartbeat\private. You could use the following

VMNet1 Public 172.168.10.0 255.255.255.0
VMNet2 ISCSI 192.168.93.0. 255.255.255.0
VMNet3 Private 10.10.10.0. 255.255.255.0

So the domain controller will have 1 NIC connected to VMNet1
Each cluster node will have one NIC connected to VMNet1, VMNet2 and VMNet3.

Get all 3 machines installed and networked and post back for details of how to create the domain controller.


Sorry, I have one doubt, please don't get mad. It is regarding the below IP addresses you suggested.

VMNet1 Public 172.168.10.0 255.255.255.0
VMNet2 ISCSI 192.168.93.0. 255.255.255.0
VMNet3 Private 10.10.10.0. 255.255.255.0

Does this mean that we need to provide the same IP address to the following. To be more clear.

For ClusterDC
VMNet1 Public 172.168.10.0 255.255.255.0

For Node1
VMNet1 Public 172.168.10.0 255.255.255.0
VMNet2 ISCSI 192.168.93.0. 255.255.255.0
VMNet3 Private 10.10.10.0. 255.255.255.0

For Node2
VMNet1 Public 172.168.10.0 255.255.255.0
VMNet2 ISCSI 192.168.93.0. 255.255.255.0
VMNet3 Private 10.10.10.0. 255.255.255.0


Mohammed Moinudheen
Post #1188409
Posted Tuesday, October 11, 2011 7:34 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, April 14, 2014 5:49 PM
Points: 2,263, Visits: 3,758
Another doubt I have is. Do these IP addresses that needs to be configured on ClusterDC, Node1 and Node2 needs to match to what was configured on Part 1 of series, i.e. the ones that were configured in 'Virtual Network Editor' of VMWare.

Screenshot below.



Mohammed Moinudheen
Post #1188432
Posted Tuesday, October 11, 2011 7:40 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 1:59 PM
Points: 5,970, Visits: 12,873
mohammed moinudheen (10/11/2011)
Sorry, I have one doubt, please don't get mad. It is regarding the below IP addresses you suggested.

VMNet1 Public 172.168.10.0 255.255.255.0
VMNet2 ISCSI 192.168.93.0. 255.255.255.0
VMNet3 Private 10.10.10.0. 255.255.255.0

Does this mean that we need to provide the same IP address to the following. To be more clear.

For ClusterDC
VMNet1 Public 172.168.10.0 255.255.255.0

For Node1
VMNet1 Public 172.168.10.0 255.255.255.0
VMNet2 ISCSI 192.168.93.0. 255.255.255.0
VMNet3 Private 10.10.10.0. 255.255.255.0

For Node2
VMNet1 Public 172.168.10.0 255.255.255.0
VMNet2 ISCSI 192.168.93.0. 255.255.255.0
VMNet3 Private 10.10.10.0. 255.255.255.0

each machine must have a unique IP address in each of the ranges. For instance

DC public = 172.168.10.2

Node1 public = 172.168.10.3
Node1 iSCSI = 192.168.93.3
Node1 private = 10.10.10.3

Node2 public = 172.168.10.4
Node2 iSCSI = 192.168.93.4
Node2 private = 10.10.10.4

Incidentally what IP address did you assign to the NAS VM, you'll to take this into account to.
Remember IP addresses in the network have to be unique, just like computernames


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

"Ya can't make an omelette without breaking just a few eggs"
Post #1188437
Posted Tuesday, October 11, 2011 7:42 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 1:59 PM
Points: 5,970, Visits: 12,873
mohammed moinudheen (10/11/2011)
Another doubt I have is. Do these IP addresses that needs to be configured on ClusterDC, Node1 and Node2 needs to match to what was configured on Part 1 of series

You can use the ranges in the tutorial or assign your own, it's up to you. Just remember which VMNet adapter belongs to which network

From memory the tutorial uses
VMNET1 public
VMNET2 private
VMNET3 iSCSI

If you don't mind me saying it seems that you have very little experience with Windows server systems and networks in general. Research TCP/IP and IP addressing. Practice these concepts on your virtual machines until you are confident of proceeding further.


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

"Ya can't make an omelette without breaking just a few eggs"
Post #1188439
Posted Wednesday, October 19, 2011 12:42 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, April 14, 2014 5:49 PM
Points: 2,263, Visits: 3,758
[b]
If you don't mind me saying it seems that you have very little experience with Windows server systems and networks in general. Research TCP/IP and IP addressing. Practice these concepts on your virtual machines until you are confident of proceeding further.


Thanks for your help so far. I referred to Networking concepts from this book
"Pro SQL Server 2008 Failover Clustering" by Allan Hirt and found it be very useful.

Also, referred to these videos which helped me to configure networking between the VMs.
Link1
Link2
Link3

Now, Going to Part 3 of series.


Mohammed Moinudheen
Post #1192667
« Prev Topic | Next Topic »

Add to briefcase «««1234

Permissions Expand / Collapse