Query re server icons in vSphere Client after system reboot

[Moggyman]

My VMware cluster got in to some kind of error state and I had to initiate a reboot of the 2 hosts supporting the cluster.  This is the first time I've had to try such a thing so I'm not sure what should happen.

Everything would appear to be OK according to the client i.e. all the servers are back up and I can remote in to them all OK, email is functioning etc etc.

However, the server icons in the client now have a red "!" against them and I can't see any error logs telling me why.  Is this normal after rebooting a cluster? Is there some kind of background operation that needs to execute before the icons change back to normal, is there somethng I need to do manually or should I be more worried?

Thanks

[kvamsi_k]

Hello there,

please see if you can provide me any screen shots.

I believe that if you see a red "!" thre should be something critical, also please check the alarms and Tasks and events tabs from both the host and the Client machines.

Please post the details so that we can work it out.

Regards,

Vamsi.

[Moggyman]

Hi

I can't see any additional info on why the shout is there.  The client reports some kind of Alert (see 'VMs on one of the 2 hosts.jpg) but doesn't tell me what it is - unless the details are tucked away in a non-obvious place.

Thanks

[iw123]

What do you see under the alarms tab?

[Moggyman]

The Alarms tabs all appear to be clear.  All servers are alive and apparently well, work is continuing and I've had no complaints. It's quite bizarre!

[kvamsi_k]

I checked the screenshots, they seemed to be fine.

Is it possible for you to send the screen shots of the Alarms and the Tasks and Events for atleast 2 machines (VMs) please.

Regards,

Vamsi.

[Moggyman]

I've attached screenshots as you kindly requested.  Nothing much to show for Server 1 however the Tasks & Events for Server 2 show the sequence of events better.

The error message in that screenshot shows what was happening when both the VMware Data Recovery Module and my Veeam Replication job were trying to backup/replicate that server.  I was just getting the "Can't do it while it's in this state" error but no guidance on what the 'state' actually was. I had a look around and Googled a bit and in the articles I found they all mentioned restarting the Management Services or rebooting the hosts.  I decided that (as I was working remotely at the time and it was Saturday i.e. the servers were not being used) maybe the best thing was to reboot the hosts.  The rest of the messages show that process and also the subsequent backup/replication jobs that have succeeded.

Thanks for looking.

[Moggyman]

Whilst sorting out another issue directly with VMware tech support, the very helpful guy I spoke to looked in to this as well.  It turned was resolved by restarting the VMware services on the Windows PC hosting the vCentre Server from end!  For reasons still unknown it seems that when I rebooted the hosts the comms between the cluster and the vCentre Server got in to a bad state and a quick restart of the services cleared it.

Many thanks for the help, comments and time spent trying to sort this out for me.

Cheers to all.

[kvamsi_k]

Not a problem... thanks for keeping updated on the status.

I was trying to find an answer using my test environment.

Good luck.

Regards,

Vamsi.