Sunday, January 24, 2010

1. Download Vmware Workstation 7 (current version on vmware.com) make sure it includes the Vmware tools otherwise you will have to manually download it from here2. You need Windows 2003 Enterprise Edition (to create the cluster).3. Install VMWare Workstation, configure a VM with these attributes :HardwareRAM: 320MbHDD0: SCSI, 4 GBCDROMEthernet 1: BridgedEthernet 2: Host-onlyOptionsAdvanced: Enable Template mode4. Install Windows 2003 Enterprise Edition on it (if you are not planning to install too many things on the C: drive 7GB should be ok).5. Post OS Installation updates: VMWare Tools, Service Pack. Link to Win2k3 SP26. Post OS Installation Steps-Rename the Host-only adapter: Heartbeat Connection-Unbind Client for Microsoft Networks and File and Printer Sharing for Microsoft Networks from this adapter-Disable NetBIOS over TCP/IP and LMHOSTS lookup on this adapter-Rename the Bridged connection: Public Network Connection7. Rename this server name as DC (Domain Controller which you will need for the cluster service account). Restart.8. Confirm everything is in place, we will use this server as Templace.9. Shutdown server10. Take a snapshot of the server while being off. And Clone it twice.(make sure you select the full clone option - I had to take the snapshot prior to the clone, if not I wasn't able to clone it).11. Let's say we have Cluster Node A and Cluster Node B. Also we have DC.12. Don't turn on anything yet and do this :Edit the settings of Cluster Node A and create two new SCSI hard disks into a new folder. Do not use an existing folder in which one of the VMs resides.

Disk 1: This will be the quorum disk. Make this 0.5 GB and allocate all disk space now.Disk 2: This will be the shared data disk. Make this at least 2.0 GB and allocate all disk space now.

When adding the disks make sure to manually add the file extension .vmdkIf you don't see the extension delete and re-create adding the extension.

8. Close VMware Workstation and edit the VMware Configuration File (.VMX) file for this machine and make the following changes:

Add the following lines to create a second SCSI channel:scsi1.present = "TRUE"scsi1.virtualDev = "lsilogic"

Modify the additional hard drives to be attached to the new SCSI channel. Example:scsi1:5.present = "TRUE"scsi1:5.fileName = "I:\Cluster Shared\Quorum.vmdk"

Make sure the inverted comma is copied/pasted correctly " and not “” I created the Clones on separate disks to help the I/O of the physical disk (I hope it helped something at least).

9. Add the same lines to the VMware Configuration of Cluster Node B.

10. Turn on the DC Server we used as a template (we can disable the option Advanced: Enable Template mode if you want).Change the Servername, the public NIC IP Address (static and use the same IP address for the DNS), disable the HeartBeat NIC.Add the Active Directory role, make sure to select the option to install DNS, this will also integrate DNS to AD.This is the first DC in the network so we don't have many worries.Done we have all on going.In my case I chose name : Control / public static ip 192.168.1.1 / DNS 192.168.1.1

11. Start VMware Workstation and start Cluster Node A. Configure the new disks as Basic disks, format them with NTFS and assign drive letters(Suggestion use the Q: drive letter for the Quorum disk, 500MB).Change the Servername, the public NIC IP Address (static and use the DC IP address for the DNS), Change the HeartBeat IP Address.In my case I chose name : Node1 / public static ip 192.168.1.10 / HeartBeat 10.0.0.1

12. Start Cluster Node B. Assign the same drive letters to the same disks.Change the Servername, the public NIC IP Address (static and use the DC IP address for the DNS), Change the HeartBeat IP Address.In my case I chose name : Node2 / public static ip 192.168.1.11 / HeartBeat 10.0.0.2

13. Now we have to change the SID of the 2 clones, if not we won't be able to join Node A & B to the domain.Well to be specific, you will be able to join these servers to the domain, but when you want to login using a Domain Account you will get an error about the Domain not being SID Consistent : LinkSo avoid the troubleshooting, download NewSid to change the SID of the cloned Servers. NewSid was a tool developed by sysinternals but after MS bought them, they had to shutdown NewSid. You can still find it on the web, try this place I downloaded it from there. If it's not working let me know.You can of course use any software that let you change your Computer SID, but most of the (at the moment at least) are paid. NewSID was a great freeware tool.Ok, if you have NewSID just generate a random SID and let the tool apply the change to your system (both Node A & B).

14. Join Node A and Node B to the domain. Reboot. Make sure you are able to join the domain.If you are wondering about the new added disks that are shared by both servers:When I tried to create a folder I could, but the change was not reflrected on the other node. So just leave it empty, don't create anything on them, if you did, just delete what you have done.

15. Now we are ready for the Party, Installing and configuring MSCS Windows 2003 :I just followed this very nice guide from Microsoft

16 In case you don't want to download the file let me do a summary,Crete a Domain Account to be used as the service account for the cluster service.Add it to the local Administrator group on both Nodes.On Node A - Start - Run - Cluadmin - Select create New ClusterIt will begin with a few checkings, when it ask you about how to configure it, select custom (just to make sure we select the Q: drive as the Quorum disk).When it's time select the Q: drive for the QuorumNext - Next - type the account name/password for the cluster service.Type the cluster name, IP Address.We are done, you have your cluster running.Now Add the other Node by : right click on the cluster, New - Node - type the serve name of Node B. Next to any Window, when it comes type the password for the service account of the cluster service.Configure the Cluster properties for the HeartBeat/Only Private communication (top priority)- Public/Mixed Communication.We're done.

Test the cluster by moving the Cluster Group between each node.

I installed all on my computer which only has 1GB RAM Memory so if you are short of Memory, decrease the memory size of the DC to 256MB, reboot your computer, stop any service you don't need at that very moment, close any application you don't need, kill processes, probably it will run a little slow like me but it will work.

Thanks a lot. adding few more lines. The main problem lies with SCSI bus channel. Check out this first. It should not use the same bus ID channel. Modify accordingly your .VMX file if u are using VMWARE..

It was just a awesome article ... Lovely and easy way to perfomr the clustering on Vmware. But I wonder if u can help me on the disks issues which I am facing.

I have added the quorum and shared disks from my local system itslef. I am able to see them in Node A & B. But when I install cluster service, It is not taking the disks and not even asking for disks and after installation, I see all the resources are online ( 3 resources ) and no issues. But I can see here quorum as Local quorum. Not taking Q Drive. and I am not add the Node B to this cluster because of disk issues. Throwing an error Quorum disk is not found.

After formating the partition, when i join to the DC, observed that my both the disk on node A were missing so tried to format both the disk but it send the error {the format did not complete successfully}

Do we need to edit the settings of Node B and add the same hard disk ?(ie Quorum and Data)I am not seeing hard disk on node B and whn i tried to add the same disks then i am getting error as the settings can not be saved.

Did anyone tried these steps till the end?As when I tried to add the second Node to the cluster, I got the below errors:

Comparing the resources between the cluster and the nodes being added...A multi-node cluster can not be created because the quorum resource does not support adding nodes to the cluster.A multi-node cluster can not be created because the quorum resource does not support adding nodes to the cluster.Comparing the resources between the cluster and the nodes being added...