vMotion not working after 4.1 vCenter upgrade

[Deuce7]

Hi all,

I'm recently upgraded our vCenter from 2.5 update 5 to vCenter 4.1 on a new server. our hosts are all still 3.5 update 5.

The old server has been retired and the 2.5 vcenter licensing server app is installed on the new vCenter.

in vCenter licensing section it's saying under 'VI3 vMotion', not used' for every host.

In the 2.5 license server it reports vMotion licenses enough for all the hosts but also 0 in use.

I'm stuck now as to how I can get vMotion active again. Any help would be greatly appreciated!

-

Richard Roberts

[Troy_Clavell]

did the "enable vMotion" box get unchecked somehow on your vmkernel port?

[Deuce7]

Nope they're all still checked/enabled.

[Troy_Clavell]

I've seen this before in some of our upgrades. Have you tried to uncheck vMotion enabled , say ok, then check vMotion enabled again?

[Deuce7]

I haven't tried that, I'll try it now.

[Deuce7]

OK that got interesting results.

I unticked vMotion on 2 hosts then when I tried to reenable it said:

"Call "HostVMotionSystem.SelectVnic" for object "vmotionSystem-1025" on vCenter Server "ANTLIA.sbc.local" failed."

in recent tasks "The License server is not configured to perform the operation".

vcenter4 licensing not cooperating with 2.5 license server perhaps.

[a_p_ · Accepted solution]

Follow the steps (4 and 5) in http://kb.vmware.com/kb/1012909

André

[Deuce7]

Excellent that looks like it's cracked it.

Not all the hosts are using licenses yet so I'll just disble and enable vMotion and that should get us back up and running fully.

Thank you both for your help.

-

Richard Roberts

[pkodeer]

At the Cluster settings we disabled the checkbox called: "Turn On VMware DRS".

All Resource Pool automatically removed, but vMotion started well!

Resource pool hierarcy must be restructure!