vSphere vCenter Server Update manager thinks a host is powered off; it isn't
Hi,
Was doing an update scan yesterday in vSphere 6.0 on 2 hosts; one went fine but the other failed; the error was it couldn't complete the scan because the state of the host was 'Powered Off'. It isn't and in fact has active VMs running on it.
All I found from Googling was generic references to vCenter server failures for various situations, none of which fit this.
Any suggestions?
I haven't tried rebooting the vCenter server yet.
Thanks!
--Ben
Was doing an update scan yesterday in vSphere 6.0 on 2 hosts; one went fine but the other failed; the error was it couldn't complete the scan because the state of the host was 'Powered Off'. It isn't and in fact has active VMs running on it.
All I found from Googling was generic references to vCenter server failures for various situations, none of which fit this.
Any suggestions?
I haven't tried rebooting the vCenter server yet.
Thanks!
--Ben
ASKER
Yes, the client works fine. It is only the update manager that thinks it is powered off.
Have you try to choose the choose the option in vCenter to reconnect the ESXi host?
If doesn't work, try to restart agent agent: https://kb.vmware.com/s/ar
Then reconnect again the host.
If doesn't work, try to restart agent agent: https://kb.vmware.com/s/ar
Then reconnect again the host.
ASKER
No, hadn't done that yet. As Andrew has taught me before, pushing buttons without a good reason to can lead to unexpected consequences. :)
Will give that a shot.
Will give that a shot.
ASKER
Oh, just to make sure: the host in the client shows as normal, as do VMs on it. So vCenter server itself has no issues connecting to this host. I thought about disconnecting/re-adding the host but am concerned that will reset the internal IDs assigned to each VM, which will impact my Veeam replication job.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Not yet; will do that after a replication job finishes in a few minutes.
ASKER
Looks like rebooting it fixed the issue. Sometimes I really do have simple problems. Thanks for the guidance!
--Ben
--Ben
restarting the management service should do the same.
But glade that is fixed.
But glade that is fixed.
State is power off or disconnected from vCenter?
Can you connect remontly to the ESXi host like iLO?? Or even can you connect to the host with vSphere Client?