VMotion failure

[Esys]

I have upgraded a couple of LUNs on our SAN to expand storage. I have successfully Vmotioned six machines from two of the "old" LUNs to the news ones. However, one Vm, RHEL5.64, consistently fails with the error "Failed to communicate with the remote host, either due to network errors or because the host is not responding." I can VMothion the Vm between hosts, but cannot move it to any other LUN. WOrkarounds, suggestions, whacks on the side of the head? The ESX servers are running 3.0.1, Virtual Center is 3.0.2. Other RHEL VMs have migrated happily, as have W2k3 VMs.

thx

Bll

[sbeaver]

Are you trying to migrate a running VM to another LUN whilethe VM is running? The VM would have to be off to move between luns.

[Esys]

My bad, forgot to mention the VM is shut down and powered off.

[Esys]

One other anomoly I just noticed. The disk size on the Settings page is "unknown", but the VM runs just fine.

[boydd]

Try restarting the mgmt agent on the host with the affected vm (sounds like vc is having problems gathering info on this vm). I had an instance like this - wound up the vmdk was corrupt and I had to use Platespin powerconvert to move the vm.

DB

[Esys]

More trivia, I can move the VM between hosts, I just can't change it's storage to a different LUN (which has several other VMs on it.) Results and error message are the same doesn't matter which host the VM is on or which LUN (of 5) I try to move it to.

thanks!

[Butcha]

You must be sure that your ESX hosts see all luns using the same lun ID's. I have been in a situation where certain luns on our SAN could only be accessed by certain hosts due to different ESX hosts seeing certain luns as different lun ID's.