Yellow Bricks

by Duncan Epping

esxi

Release notes VC U3

· ·

There seems to be an incorrect advanced option in VC U3.

HA network compliance check
During the configuration of HA in VirtualCenter 2.5 Update 2, the Task & Events tabs might display the following error message and recommendation:
HA agent on <esxhostname> in cluster <clustername> in <datacenter> has an error Incompatible HA Network:
Consider using the Advanced Cluster Settings das.allowNetwork to control network usage.
Starting with VirtualCenter 2.5 Update 2, HA has an enhanced network compliance check to increase cluster reliability. This enhanced network compliance check helps to ensure correct cluster-wide heartbeat network paths. VirtualCenter 2.5 Update 3 allows you to bypass this check to prevent HA configuration problems. To bypass the check, add das.bypassNetworkVerification=yes to the HA advanced settings.

The described option should actually be “das.bypassNetCompatCheck with the values  “true” or “false. So keep this in mind!!!

Update: HA Advanced Options

· ·

A while back I wrote down all the HA advanced options. With VirtualCenter 2.5 Update 3(and the ESX patch that came with it) VMware added another extra advanced options, this is the complete list:

  • das.failuredetectiontime – Amount of milliseconds, timeout time for isolation response action(with a default of 15000 milliseconds).
  • das.isolationaddress[x] – IP adres the ESX hosts uses for it’s heartbeat, where [x] = 0-9. It will use the default gateway by default.
  • das.usedefaultisolationaddress – Value can be true or false and needs to be set in case the default gateway, which is the default isolation address shouldn’t be used for this purpose.
  • das.poweroffonisolation – Values are False or True, this is for setting the isolation response. Default a VM will be powered off.
  • das.vmMemoryMinMB – Higher values will reserve more space for failovers.
  • das.vmCpuMinMHz – Higher values will reserve more space for failovers.
  • das.defaultfailoverhost – Value is a hostname, this host will be the primary failover host.
  • das.failuredetectioninterval – Changes the heartbeat interval among HA hosts. By default, this occurs every second (1000 milliseconds).
  • das.allowVmotionNetworks – Allows a NIC that is used for VMotion networks to be
  • considered for VMware HA usage. This permits a host to have only one NIC configured for management and VMotion combined.
  • das.allowNetwork[x] – Enables the use of port group names to control the networks used for VMware HA, where [x] = 0 – ?. You can set the value to be ʺService Console 2ʺ or ʺManagement Networkʺ to use (only) the networks associated with those port group names in the networking configuration.
  • das.isolationShutdownTimeout – Shutdown time out for the isolation response “Shutdown VM”, default is 300 seconds. In other words, if a VM isn’t shutdown clean when isolation response occured it’s being powered off after 300 seconds.
  • das.bypassNetCompatCheck – Disable the “compatible network” check for HA that was introducedwith Update 2. Default value is “false”, setting it to “true” disables the check.Virtual Machine Monitoring HA advanced options
  • das.failureInterval = The polling interval for failures. Default value is 30.
  • das.maxFailureWindows = Minimum amount of seconds between failure. Default value is 3600 seconds, if VM fails within 3600 seconds VM HA doesn’t restart the machine.
  • das.maxFailures = Maximum amount of VM failures, if the amount is reached VM HA doesn’t restart the machine automatically. Default value is 3.
  • das.minUptime = The minimum uptime in seconds before VM HA starts polling. The default value is 120 seconds.

Update for ESX 3.5

· ·

After the 3.0.X updates the 3.5 updates couldn’t be far away, and here you go… And if you have a close look at the KB article of the patch you can see that VirtualCenter 2.5 Update 3 is also coming soon.

Update: Quick Migration

· ·

A couple of days ago I wrote about the Quick Migration script that Mike D wrote with Powershell. Like I said, it should be possible to integrate the script with VC. Well this has been done by Dennis of Icomasoft. Icomasoft recently released the Powershell Plugin for VirtualCenter. And with this plugin you can easily integrate your scripts into VirtualCenter which makes it even more easy to run your scripts. You can find the altered script here, it includes a nice progress bar…

Thanks Thomas, for pointing me out! And great work by Dennis!

VMware Quick Migration

· ·

How cool is this Powershell script! Mike D. wrote a powershell script that does exactly what Hyper-V’s quick migration does. It should be possible to integrate it with the VC Client, and if they open up the ESXi SDK as Mike suggest than you have the functionality for the free hypervisor from VMware. By the way talking about a free hypervisor, Hyper-V is also available as of today.