Today we configured a new VLAN on the physical switches, now we need to configure a portgroup with vlan id on multiple ESX hosts in our cluster. To do this by hand it will cost 3 minutes per host, to script this.. you configure this in 10 seconds!

The script:

^{Get-Cluster “clustername” | Get-VMHost | Get-VirtualSwitch -Name “vSwitch0″ | New-VirtualPortGroup -Name “VLAN-23-Citrix Provisioning” -VLanId 23}

Voila!

Today I got an error when selecting the “VMware EVC” option in the Cluster Settings at my vCenter 4.0 host with multiple HP Blades with same CPU. Error message:

Method not found: ‘Vmomi.HostSystemArray EVCState.get_BadSoftwareHostsBlockingEVC()’

Solution:

This issue occurs when a system installed with vSphere 4.1 and you use vSphere 4.0 Client on that system to access vCenter Server 4.0.

To workaround this issue, install a vSphere 4.0 Client on a system on which you have not installed vSphere4.1 Client earlier and then update the EVC cluster using the vSphere 4.0 Client.

Source: VMware

View also: Clustering vCenter Server 4.0 Using Microsoft Cluster Services Part: 1

Install Virtual Center 4.0 on Node 1:

Start the installation:

Read more…

To use Microsoft Windows Cluster Service in VMware ESX you need to config you’r VM’s with independent persistent disks.

VM configuration:

I deployed two Windows 2003 SP2 Enterprise 32-Bit VM’s with both 12 GB of OS disks and two NIC’s. I called these: VMPROS-CL01 and VMPROS-CL02.

VMPROS-CL01 with ip: 172.16.254.78 and for MSCS nic ip: 1.0.0.1

VMPROS-CL01 with ip: 172.16.254.89 and for MSCS nic ip: 1.0.0.3

Registered this VM’s in domain VMpros.nl

  Read more…