vMotion fails at 20% ” The operation is not allowed in the current state .”

I built new hosts which were added to an existing cluster. After taking them out of maintenance mode, I cannot vMotion VMs to the new hosts. I followed this KB article and this blog post. Nothing worked. I was on the verge of resetting one host.

vim-cmd vimsvc/task_list showed several tasks like below, it didn’t seem right.

‘vim.Task:haTask–vim.StorageResourceManager.ConfigureDatastoreIORMOnHost-94’,
‘vim.Task:haTask–vim.StorageResourceManager.ConfigureDatastoreIORMOnHost-95’,
‘vim.Task:haTask–vim.StorageResourceManager.ConfigureDatastoreIORMOnHost-96’,
‘vim.Task:haTask–vim.StorageResourceManager.ConfigureDatastoreIORMOnHost-97’,
‘vim.Task:haTask–vim.StorageResourceManager.ConfigureDatastoreIORMOnHost-98’,
‘vim.Task:haTask–vim.StorageResourceManager.ConfigureDatastoreIORMOnHost-99’,
‘vim.Task:haTask–vim.StorageResourceManager.ConfigureDatastoreIORMOnHost-100’,
‘vim.Task:haTask–vim.StorageResourceManager.ConfigureDatastoreIORMOnHost-101’,
‘vim.Task:haTask–vim.StorageResourceManager.ConfigureDatastoreIORMOnHost-102’,
‘vim.Task:haTask–vim.StorageResourceManager.ConfigureDatastoreIORMOnHost-103’,
‘vim.Task:haTask–vim.StorageResourceManager.ConfigureDatastoreIORMOnHost-104’,

I thought of checking jumbo frame which turned out to the culprit. This cluster uses VSS. I changed the MTU to 9000 for VMkernel NAS interface but forgot to do so at the vSwitch level which is 1500 by default. After changing the MTU at the vSwitch level, it worked immediately.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s