vMotion working or not in entire vCenter

[RajuVCP]

HI All,

Sometime we may come across with vMotion errors , the VM may not get migrated to other host in cluster due to various reasons. In such scenario when ever we get hardware crash the VMs running on them could not able to move to other host in the cluster and this makes total downtime of the VMs.

What i was looking for some script which can check if vMotion funtionality is working  or not..in my different vCenter. Script can also give results which all are host/Cluster working good with vMotion and which all host/clusters have vMotion issues.

With these we can pre identify the vMotion and rectify the vMotion issue before host goes down.

[LucD]

Not sure if you test the functioning of vMotion without actually vMotioning a VM.
You can start the vMotion as a background task (RunAsync), and on completion check the content of $Task.Info.Result.

Or eventually check the events for failed vMotions.

Get-VIEvent -Start (Get-Date).AddDays(-7) -MaxSamples ([int]::MaxValue) |

where{$_ -is [VMware.Vim.VmRelocateFailedEvent]}

[RajuVCP]

Thanks LuCD for quick response as always :smileyhappy:.

Here I was don't want to do complete VM migration from one host to another. I just want to check or do checklist if vMotion is working in my infra or not.

Some times we get vMotion errors due to unknown reasons. To overcome such vMotion issues as a precautionary measure want to do a checklist or test if vMotion is good or not. Something script could able to do vMotion functionality test and show result for the host vMotion works perfectly and also shows the host where vMotion have issues.

Thanks :smileyhappy:

[LucD]

Would steps 2) and 3) in KB1003734 be a checklist that could discover the issues with vMotion you are experiencing?

If not, what kind of issues do you encounter?

[RajuVCP]

Thanks LucD ,

The KB is mostly for vMotion issues.

The common vMotion issue I face is

1. Change host and datastore vMotion is greyed out.

2. Change host vMotion is greyed out.

3.vMotion hungs at certain percentage like 14% , 21%.

likewise.....

in such issue we were not aware how many host has such vMotion issues, until those host goes down due to hardware or other reason and we come to know the VM's didn't moved to other host.

I was looking something...which should just test vMotion funcationality from one host to other host in the cluster across entire vCenter. its fine even if we take first VM from each host to get migrated to other host in each vCenter to test vMotion functionality.