Hi
I am currently having problems trying to power 1 of the VMs on the ESX host. There are 5 other VMs on that ESX host which is being powered on but this particular one is rather tricky.
I am running the vSphere client on the ESX 3.5 host with Virtual Centre 4.
I have tried the following but does not help:
Thanks
Hi,
Do you have the license server for ESX 3.x installed and running on your vCenter server 4?.
Regards/Saludos
Por favor no olvides calificar las respuestas que te resultaron de ayuda o fueron correctas.
Please, don't forget the awarding points for "helpful" and/or "correct" answers.
________________________________________
Nicolás Solop
VMware vExpert 2010 - VCP 410- VCP 310 - VAC - VTSP
Was the ESX 3.5 host fully licensed or was it running in evaluation mode? As the other poster indicated were you running a licensing server and is it still accessible by the ESX host? This error typically comes when the license is no longer valid for the ESX host -
If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
Yes. It is licensed as there were others ESX servers pointing to the same Virtual Centre and working.
So you have a license server installed on your vcenter server. Is it running? The other hosts are 3.x or 4.x? Can you power on another virtual machine on the same host, or power on any on other host?
Regards/Saludos
Por favor no olvides calificar las respuestas que te resultaron de ayuda o fueron correctas.
Please, don't forget the awarding points for "helpful" and/or "correct" answers.
________________________________________
Nicolás Solop
VMware vExpert 2010 - VCP 410- VCP 310 - VAC - VTSP
nope. I can't power on other VMs.
Assuiming you have ssh access and the VMs sitting inside shared storage:
unregister VMs from problematic ESX,
$vmware-cmd -s unregister /vmfs/volumes/..../vmname.vmx
register VMs to OKAY ESX
$vmware-cmd -s register /vmfs/volumes/..../vmname.vmx
Then power on
$vmware-cmd /vmfs/volumes/..../vmname.vmx start trysoft
vcbMC-1.0.6 Beta
vcbMC-1.0.7 Lite
Also remember that firewall on the server running licenece server needs to have exceptions for 27000 & 27010 TCP ports
Seb
Morning,
It sounds to me like you are busy going through an upgrade?
ESX 4 hosts are licensed against your VC using a method that is totally different to ESX 3.5 licensing.
Do you still have your old license server running to manage your ESX 3.5 hosts? If not, this would be why you no longer can boot VMs on these hosts.
Of course, if the other hosts are all ESX 3.5 too and are working, your problem must lie elsewhere.
Bear in mind though, ESX 3.5 does not necessarily use the VC as the license server - so you could have some ESX hosts using a differnt license server to another . . but still share a VC (unusual . . but possible)