Hey Guys,
Well I've been using the forum for all the great info and even though I searched there wasn't a specific topic for exactly this, really only half hijacked threads that didn't actually explain what to do. So I thought I'd finally contribute something back
This is just a basic run down of what I did to finally get 2 VM's running Microsoft Cluster Services in VI3 with full VMotion support and ability.
1. Create your two VM's with Windows Enterprise and Cluster Services installed.
2. Ensure there are two NIC's to allow for the Heartbeat between the VM's. There should be a primary NIC and a private NIC that only has to talk to the other private NIC on the second VM.
3. Allocate on your SAN a raw LUN (4Gig) that is definately accessible by both ESX servers. On the first VM you should have your boot volume on one SCSI device and any other drives needed on the first SCSI controller.
4. Add a new disk to the VM then select RAW Mapping. Select the Host SCSI ID that correlates to your raw LUN that you created and select next. Make sure you place the new disk onto a spare SCSI channel. In my case 1:0. I guess it should be standalone. This will automatically create another LSI SCSI Adapter in your hardware config.
Now the confusing part: Put the disk into Virtual Mode, then select the disk to be Independant AND Non-Persistant. This was the part that stumped me for ages.
5. Power on the first VM with the new RDM disk created. You must make sure that there is NO bus sharing on the new SCSI Adapter. It should default to None anyways.
6. Log into Windows and format the new drive that it detects and assign it a drive letter, eg "Q:".
7. Shutdown the first VM and select to edit the second VM settings. Go through the same process as step 4 and make sure that the SCSI Channel is also set to 1:0 (or whatever it is in the first VM). Also make sure its Independant and Non-Persistant.
8. Power on both servers and providing your networking is setup correctly start creating a new MCS and it lock in the new Quorum disk automatically and be successfull!
Now I know this is a real brief description and yes probaly some steps could be changed / done differently but this is just what I had to do to get it going I was pulling my hair out! What I tried is just a combination of what I've found on the forums but it was still hard to find and I saw alot of new people weren't quite understanding what was being told. In the end the process really is quite simple.
I'm definately not a guru but it might actually help someone
Any questions please feel free to ask!
Well I've been using the forum for all the great info and even though I searched there wasn't a specific topic for exactly this, really only half hijacked threads that didn't actually explain what to do. So I thought I'd finally contribute something back
This is just a basic run down of what I did to finally get 2 VM's running Microsoft Cluster Services in VI3 with full VMotion support and ability.
1. Create your two VM's with Windows Enterprise and Cluster Services installed.
2. Ensure there are two NIC's to allow for the Heartbeat between the VM's. There should be a primary NIC and a private NIC that only has to talk to the other private NIC on the second VM.
3. Allocate on your SAN a raw LUN (4Gig) that is definately accessible by both ESX servers. On the first VM you should have your boot volume on one SCSI device and any other drives needed on the first SCSI controller.
4. Add a new disk to the VM then select RAW Mapping. Select the Host SCSI ID that correlates to your raw LUN that you created and select next. Make sure you place the new disk onto a spare SCSI channel. In my case 1:0. I guess it should be standalone. This will automatically create another LSI SCSI Adapter in your hardware config.
Now the confusing part: Put the disk into Virtual Mode, then select the disk to be Independant AND Non-Persistant. This was the part that stumped me for ages.
5. Power on the first VM with the new RDM disk created. You must make sure that there is NO bus sharing on the new SCSI Adapter. It should default to None anyways.
6. Log into Windows and format the new drive that it detects and assign it a drive letter, eg "Q:".
7. Shutdown the first VM and select to edit the second VM settings. Go through the same process as step 4 and make sure that the SCSI Channel is also set to 1:0 (or whatever it is in the first VM). Also make sure its Independant and Non-Persistant.
8. Power on both servers and providing your networking is setup correctly start creating a new MCS and it lock in the new Quorum disk automatically and be successfull!
Now I know this is a real brief description and yes probaly some steps could be changed / done differently but this is just what I had to do to get it going
I was pulling my hair out! What I tried is just a combination of what I've found on the forums but it was still hard to find and I saw alot of new people weren't quite understanding what was being told. In the end the process really is quite simple.I'm definately not a guru but it might actually help someone
Any questions please feel free to ask!
