Today I added some vSphere 5.0 u1 hosts in a new created cluster, the SAN will be delivered next week so I didn’t have central storage, to finish my new cluster setup I configured HA and DRS. After configuring HA I received this warning message:
The number of heartbeat datastores for host is 0, which is less than required: 2
Solution:
To (temporary (until the SAN is installed)) hide the warning message I configured the HA – Advanced Option:
- Log in to vCenter Server
- Right-click the cluster and click Edit Settings
- Click VMware HA > Advanced Options
- Under Option, add an entry for das.ignoreInsufficientHbDatastore
- Under Value, type: true
More information: VMware
Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.
More Posts - Website
Follow Me:
Last week I configured for a customer some new VLAN’s and created on each host new vSwitches with new portgroups, to migrate all VM’s in cluster with network label “VM Network” to “Production” I’ve created this script to automate this for all virtual machines with specific network label in cluster:
Original situation:
Script:
#====================================================================#
# SCRIPT: PowerCLI_Mass_change_network_label.ps1 #
# FUNCTION: Mass change network label Network A to Network B #
# OWNER: Sander Daems #
# VSPHERE: 5.0 Update 1 build 623860 #
# CREATED: 10/01/2013 #
# MODIFIED: 10/01/2013 #
# VERSION: v.1.0 #
#====================================================================#
# CHANGELOG: #
# #
# v.1.0 #
# - Script created; #
# #
#====================================================================#
# HOST - Specify host and connect #
#====================================================================#
$vCenterServer = Read-Host "Enter vCenter Hostname / IP"
Connect-VIServer $vCenterServer
#
#====================================================================#
# CUSTOM DEFINITIONS #
#====================================================================#
$Cluster = "Cluster01"
$SourcePortgroup = "VM Network"
$DestinationPortgroup = "Production"
#
#====================================================================#
# SCRIPT #
#====================================================================#
Get-Cluster $Cluster | Get-VM | Get-NetworkAdapter | Where {$_.NetworkName -eq $SourcePortgroup } | Set-NetworkAdapter -NetworkName $DestinationPortgroup -Confirm:$false#====================================================================#
Result:
New situation (All VM’s in cluster):
Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.
More Posts - Website
Follow Me:
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!
Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.
More Posts - Website
Follow Me:
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
Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.
More Posts - Website
Follow Me:
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…
Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.
More Posts - Website
Follow Me:
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…
Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.
More Posts - Website
Follow Me:
Recent Comments