Lets Design, Implement and do Administration of ESX3

Virtualization with VMWare Infrastructure 3.0

MSCS AND VMWARE

Posted by Preetam on April 16, 2007

MSCS AND VMWARE

Few points to remember when you decide to built clustering inside VM which might be CIB or CAB.

Virtual Machine (Cluster Node) have forementioned boundaries

  • Only LSI Logic virtual SCSI Card
  • Only VMXnet
  • Only 32-Bit VMs
  • 2-Node Clustering only
  • Nic teaming is not supported
  • iSCSI clustering is not supported
  • Boot from SAN is not supported
  • VMs part of clustering cannot be part of VMHA & DRS
  • Cannot VMotion on VMs using clustering software
  • ESX 2.5 and ESX 3.0 is not supported
  • Different HBA’s card manufacturer not supported
  • When using N+I SCSIPort Miniport driver must be present on Physical Node and not Storport Miniport driver, also there must be no powerpath software installed on physical node.

If you clone VM’s with RDM enabled, RDM will be converted into vmdks You must zero-out the disk which you would like to shared disk, you can also use mapped SAN LUN, in this case you don’t need to use VMKFSTOOLS Disk must map to SAN LUN and it is recommended to have RDM set up in physical mode Upgrade of VMs, which are using MSCS, is supported only from ESX 2.5.2 to ESX 3.0.

UPGRADING RDM AND BOOT VOLUME VMFS ON DIFFERENT VOLUMES

Power off Virtual NodesUpgrade volumes from VI ClientPower on each node, in case you get error ‘Invalid argument, you have misconfigured cluster setup’, Virtual disk of ESX 2.x cannot be powered on ESX3.0. In this case you need to import this disk using VMKFSTOOLS utility

UPGRADING RDM AND BOOT VOLUME ON SAME VMFS VOLUME

Power off Virtual NodesUpgrade volumes from VI ClientUpgrade from 2 to VMFS3.0 relocates RDM and first Node VMx file, when you now upgrade the second node that unable to locate vmdk file, ignore it. In anyway it will uprade VMDK now manually edit second node’s vmx file and point to quorum and RDM file’s new location.

UPGRADING CLUSTER ACROSS BOX

Using shared pass-through RDM is similar to upgrading on same VMFS volume

Using files in shared VMFS-2 volumes
  1. Change the mode of volumes from shared to public
  2. Upgrade ESX server
  3. Upgrade VMFS volume from VI client
  4. Create LUN for each shared disk
  5. For each shared disk , create RDM pointing to respective luns

e.g vmkfstool –i oldvmdk.vmdk newrdm.vmdk –d respectivelun

  1. Finally modify VMx file for each node pointing to respective new RDMs

This is what I have understood from the document, but honestly this requires practically experience to say with confidence.

Advertisements

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: