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
Ben ConnerCTO, SAS developerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Luciano PatrãoICT Senior Infraestructure  Engineer  Commented:
Hi,

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?
0
Ben ConnerCTO, SAS developerAuthor Commented:
Yes, the client works fine.  It is only the update manager that thinks it is powered off.
0
Luciano PatrãoICT Senior Infraestructure  Engineer  Commented:
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/article/1003490

Then reconnect again the host.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Ben ConnerCTO, SAS developerAuthor Commented:
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.
0
Ben ConnerCTO, SAS developerAuthor Commented:
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.
0
Luciano PatrãoICT Senior Infraestructure  Engineer  Commented:
Dis you restarted the management services??

Remove and add should be the last option and yes will have impact in your Veeam backup / Replication.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ben ConnerCTO, SAS developerAuthor Commented:
Not yet; will do that after a replication job finishes in a few minutes.
0
Ben ConnerCTO, SAS developerAuthor Commented:
Looks like rebooting it fixed the issue.  Sometimes I really do have simple problems.  Thanks for the guidance!

--Ben
0
Luciano PatrãoICT Senior Infraestructure  Engineer  Commented:
restarting the management service should do the same.

But glade that is fixed.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.