I am running vSphere 5.1 on a cluster of 4, identical Cisco B200 M3 blade servers, each with the same number of cores (12) and amount of memory (160G).
I am attempting to enable Fault Tolerance for one of my virtual machines: a 1 vCPU, 4GB memory, Windows Server 2008 R2 virtual machine.
When I initially enable Fault Tolerance, all goes as planned. The secondary VM is created and powers up as expected on another blade (host) in the cluster.
When I test FT fail over, the secondary quickly assumes "primary" status and takes over processing. The "new" secondary, however, is in a powered-down state which does not provide a method or the menu options to power on. I would expect that the new secondary VM would be created in the powered on state, or quickly transition to the powered on state.
Also, if I've just enabled FT, and I attempt to "Test Restart Secondary", that operation fails. The secondary will shut down, but won't start back up. The following error messages are issued in vCenter:
vCenter cannot start the Fault Tolerance Secondary VM. Reason: Cannot complete login to secondary host
vSphere HA agent failed to start Fault Tolerance secondary VM. (filename.vmx) Reason: The operation is not allowed in the current state
The only way to get the secondary to power up is to disable FT on the primary, and then re-enable FT.
I don't understand how vCenter can "login to the secondary host" in order to create and power up the secondary VM when FT is first turned on, but can't login to restart the secondary VM.
I've scoured Google and haven't found anything helpful yet.
I restarted management services on all of the hosts, but that did not clear the problem.
Any help would be appreciated.
Thank you.