When we try and do a fail over test the VM's on the failed host just show a disconnected status? Both Hosts can see the same LUN #'s on our san. And we can broswer the datastore from both hosts. We only have 2 VMS running on cluster seems to happen to both of them.
I can vmoton VM's from one host to the other fine.
Anyone have any ideas? We are running ESX Server 3I, and Virtual Center 2.5
Thanks,
MC
How are you doing your failover test?
Well I tried 2 ways
1. I shutdown the host from virtual center
2. Unplug the power cables from one of the Hosts.
Both ways gives me same resluts.
Thanks,
MC
Does the behavior change if you check the option to allow power on to violate availability constraints?
First, a clarification: HA has nothing to do with vmotion.
vmotion is a migration of a running vm to another host; HA is the functionality where vms from a failed host are restarted on a different host in the HA cluster. Since the failed host has, well,.. failed, there is nothing to vmotion.
So, have you enabled HA on the cluster, and you have not set failover priority for the vms to disabled? (just making sure)
Try disabling en re-enabling HA on the cluster.
Yes it still happens. The machine fails to start and shows a disconnected status.
Thanks,
MC
Yes, I have 2 network cards in each server with default gatway set.
Thanks,
MC
MC,
where are the VMX files of the VMs located ?? on the host or on the shared storage. If you have the VMX files on the host, you will be able to do the VMotion but when a host fails, the VMs will remain disconnected. Can you check & confirm this please ??
Niru
and ofcourse don't forget to award the points for the right answers plz..
Under VMWare Ha -> Virtual Machine Options I have it Set to
Restart Priority set : HIGH
Isolation Priority set: Power Off
Thanks,
MC
The hosts are install on the direct attached storage, But the Guest VMs are on the shared Lun.
Thanks,
MC