NMSGuy
asked on
Virtual Center 2.5 - All of my templates and VM (except for 3) shows disconnected
Hello Experts,
I just upgrade my MSSQL EXP server that comes in with VC 2.5 to MSSQL Enterprise server. I was able to see all of my ESX boxes and VM's. The only problem is that most of my VMs and Templates are in disconnected state. This prohibits me for deploying a new VM from the template. I am logged in as administrator. Is there something wrong on the DB side? any thoughts?
I just upgrade my MSSQL EXP server that comes in with VC 2.5 to MSSQL Enterprise server. I was able to see all of my ESX boxes and VM's. The only problem is that most of my VMs and Templates are in disconnected state. This prohibits me for deploying a new VM from the template. I am logged in as administrator. Is there something wrong on the DB side? any thoughts?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I did remove all of the ESX servers from the Cluster > Host tab. Is it possible to add multiple ESX servers to the VC?
hi
the real purpose of using Virtual Center is to manage multiple ESX servers and if you have license for "vmotion" "DRS" "HA" you can create HA clusters DRS clusters and move VMs from one ESX server to another server without any issues.
Virtual center is really a very wonderful management tool to manage ESX environments. But the real issue is the Licensing costs which are normally something that organizations with truckloads of money to spend.
bhanu
the real purpose of using Virtual Center is to manage multiple ESX servers and if you have license for "vmotion" "DRS" "HA" you can create HA clusters DRS clusters and move VMs from one ESX server to another server without any issues.
Virtual center is really a very wonderful management tool to manage ESX environments. But the real issue is the Licensing costs which are normally something that organizations with truckloads of money to spend.
bhanu
Try bhanukir7's suggestion but if that fails,
console into the ESX server and run these commands
service vmware-vpxa stop
service mgmt-vmware stop
wait for both to say [ OK ]
service vmware-vpxa start
service mgmt-vmware start
Server should be reconnected.
* If any of these services fail, you may try to kill the service directly, but this can cause the VMs to die. Take caution if the VMs are critical and cannot be powered off.
ps -ef | grep "hostname"
kill -9 <PID>
service vmware-vpxa start
service mgmt-vmware start
This should not be done unless you really need to get the host back up at the cost of other vms. Could be as severe as a reboot command.
Hope that helps.