VMware Cloud Community
bugeyemonster
Enthusiast
Enthusiast

not enough licenses to complete a vmotion

I have a cluster with 2 HP 685c G5 blade servers in it. The license server is on the virtual center server and both servers appear to be fully licensed on the configuration tab. I have unused licenses as well. I am able to vmotion from system A to system B but not from system B to system A. If I shut down a Machine that is on A then I am not able to restart that system on A, I have to migrate it to B and start it up.

The message I get is "There are not enough licenses installed to perform the operation."

I am able to migrate systems to A but not vmotion them. Once they have been moved there however I can not power them on. If I try to vmotion the system It just fails with the message above.

The hostd log displays this when I try to power on a virtual machine

Current value 141268 exceeds soft limit 122880.

Task Created : haTask-2016-vim.VirtualMachine.powerOn-154140801

Event 622 : guestname on host hostname.xxx.xxx.edu in ha-datacenter is starting

State Transition (VM_STATE_OFF -> VM_STATE_POWERING_ON)

Failed to get License for : san. Action : Reporting Feature unlicensed Event

Event 623 : A required license SAN Usage is not reserved

Failed to get License for features. Action : throwing NotEnoughLicenses

Failed operation

Event 624 : Failed to power on guestname on hostname.xxx.xxx.edu in ha-datacenter: A general system error occurred:

State Transition (VM_STATE_POWERING_ON -> VM_STATE_OFF)

Task Completed : haTask-2016-vim.VirtualMachine.powerOn-154140801

Activation : Invoke done on

Throw vmodl.fault.NotEnoughLicenses

Result:

(vmodl.fault.NotEnoughLicenses) {

dynamicType = <unset>,

msg = ""

}

Reply
0 Kudos
10 Replies
AndreTheGiant
Immortal
Immortal

Sure that node A is licensed.

Can you create a new VM and power it on?

Which version of ESX do you have?

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Reply
0 Kudos
Troy_Clavell
Immortal
Immortal

have you checked your vmkernel port on hostB to ensure you have the check mark next to "enable vMotion"? I would assume since you can vmotion to it, it should be checked, but....

Also, hostB, can you vmkping the vmkernel address on hostA?

Reply
0 Kudos
bugeyemonster
Enthusiast
Enthusiast

esx 3.5.0 143128

I should also mention that I have 11 other esx servers grouped in three clusters with the same storage and virtual center and the same version of esx and they all work no problems.

Also this cluster used to work as intended. It stoped working a little over a week ago. I discovered the probem after adding some new storage and trying to migrate virtual machines to the new datastores using storage vmotion.

vmware support has been unable to provide an answer as of yet.

Reply
0 Kudos
bugeyemonster
Enthusiast
Enthusiast

yes vmotion is enable and the ping works in either direction.

Reply
0 Kudos
Troy_Clavell
Immortal
Immortal

maybe this KB will help in providing a resolution for you

http://kb.vmware.com/kb/1005265

Reply
0 Kudos
TB_Rich
Enthusiast
Enthusiast

Can you point the VI client at the host direct and not at VC - then try to power on the VM??

ServerA, it sounds like it is not licensed correctly - is the ESX server edition set correctly and not just the license source.

bugeyemonster
Enthusiast
Enthusiast

If I point the VI client at the esx host I am able to power on servers.

What does that mean? The problem is with virtual center?

Reply
0 Kudos
AndreTheGiant
Immortal
Immortal

Is a very strange problem.

You server is using the license server? Or has a standalone license?

Try also to restart license server.

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Reply
0 Kudos
bugeyemonster
Enthusiast
Enthusiast

The server is using the license server and I have restarted the license server that did not work.

i issued a service vmware-vpxa restart and them seems to have cleared up the problem.

Reply
0 Kudos
Troy_Clavell
Immortal
Immortal

i issued a service vmware-vpxa restart and them seems to have cleared up the problem.

you opened an SR regarding this issue and vmware didn't try this simple step?

glad to see you got it resolved though. Please consider the use of the "correct" or "helpful" buttons to award points.

Reply
0 Kudos