Hi all,
Starting to come across some niggling issues since upgrading, I knew this would happen on such a large environment adopting pretty early.
The latest is an issue with HA,
It seams to be restarting machines due to a HA event, most times its unsuccessful coming up with "vSphere HA unsuccessfully failed over this virtual machine, vSphere HA will retry if the maximum number of attempts has not been exceeded. Reason: The operation not allowed in the current state" or operation timed out
This will happen shortly after a disconnect of the host, (the network path these go through can be dodgy at time and is the reason we had isolation response set to leave powered on, with vSphere 5 datastore heatbeat thought i might be able to change it one day.
Either way the HA response is going completely against what the settings are
environment is all hosts running ESXi5 and vcenters running version 5 too.
My HA settings are:
Enabled Host Monitoring
admission control disabled for now
virtual machine options:
vm restart priority: medium
Host isolation response: Leave Powered On
VM Monitoring: Disabled
Datastore heatbeat set to select any of the cluster datastores
If a hosts disconnects for a minute or 2 from vCenter it should not be trying to restart guests with the settings that have been set.
Any ideas would be great
Cheers
________________________________________
Blog: http://virtualiseme.net.au
VCDX #201
Author of Mastering vRealize Operations Manager
