Virtual Machines status not correct vissible

Hello,

We have at the office 3 ESX servers, after upgrading to the new version of VirtualCenter 2.0.2 I can see that only on one of our ESX server nodes the status is correct visuable

see screenshot

http://www.fekanv.be/vmware.jpg

Regards,
Kurt

TRy reinstalling vmware tools

I was having the same problem and a service vmware-vpxa restart brought back all of the status lights for my vms.

I see you beat me to the punch bjmoore !

Our shop too has been experiencing this issue. It started after VC 2.0.1 Patch 2. It happens pretty much anytime after a host is rebooted, or the Virtual Center service is restarted on the VC server.

For us this happens 100% of the time upon a host reboot/VC service restart. Every time we have to restart the vpxa client on the host.

I have an open ticket with support, but they haven't been able to fix this issue.

Is anyone else experiencing this issue?

To compare notes. Our VC server is win2k3 R2 SP2, SQL2005 SP2. Fully patched ESX 3.0.1 hosts. Our VMs are a mix of linux and windows. We are running from an iSCSI SAN.

Message was edited by: joelgb

Yep that did the trick

service vmware-vpxa restart

I hope they fix it in the near future

kurt remember to assign points for helpful/correct answers.

See you on VMTN

Pardon my ignorance but where exactly is this vpxa service - on the ESX host itself or the guest VMs? If on the ESX host how do you go about restarting it?

Many thanks.

Chris

You'd SSH into the console of your ESX server, su - to get root access and then type "service vmware-vpxa" restart. It should show you progress for restarting the service. After a few minutes VC will poll the ESX host again and the status lights should reappear.

Fantastic - that's done the trick. Many thanks.

I'm also getting this problem.
I can get the status back by #service vmware-vpxa restart but then if I restart the virtual center service, i lose all the vm status and have to run service vmware-vpxa restart on each host again. Has everyone who upgraded to 2.0.2 got this problem?

I have the same issue :

VCenter 2.0.2
ESX 3.0.2

Some VM's didn't show the status so I restarted the vmware-vpxa service.
Now all VM's don't show the status.
I've done this 15 minutes ago.

???

I saw a similar problem after I restarted the VC service on the windows server it was hosted on. I might suggest restarting that service, then restarting mgmt-vmware and vmware-vpxa again.

good luck!

Now took a look at the affected server and still the VM*s status is missing.

So I did

service vmware-vpxa stop
service mgmt-vmware restart
service vmware vpxa start

and now the status is back 🐵 but VMware needs to fix it.
I do not want to connect to each ESX (we have about 50 at the moment)
and issue those commands ... what about a centralized CLI interface in VCenter guys ???

It would be easier with it to implement those workarounds ... :o)))

I've got the same issue. Just upgraded VirtualCenter to 2.0.2

VCenter 2.0.2
ESX 3.0.1

Some VMs had a status, some did not. After restarting the VCenter Service I have no status on any VMs

After restarting mgmt and vpxa I now have status on all of my windows server guests, but not for my Linux Guests.

FYI - If I point my VIClient to my host server instead of my Virtual Center Server, I have a status on all guests (even before stopping and restarting mgmt and vpxa)

Message was edited by:
hazent

I see the status of Winodws & Linux VM's after restarting

mgmt-vmware and vmware-vpxa

Did someone create a SR with VMware ?

I think I will create one today.

I've got a SR open...still working on it though.

I just recreated all of my VM-related alarms and that seemed to clear it up, at least for now...

My guess is that even after recreating all your VM alarms, if you restart the Virtual Center Service your status lights will stop working again. At least that is what happens on our setup.

I had a SR open but after trying many things (recreating alarms, reinstalling the vpxa agents on the ESX hosts, total fresh reinstall of virtual center and database on a VM instead of a physical host), it was closed because our ESX servers are not running on supported hardware. We run IBM x345's(not supported) an equallogic SAN, qlogic 4052c HBAs, and each box has Quad Port Intel Gigabit NICs.

bjmoore: If you don't mind, what hardware are you running and are you on totally supported hardware? How much troubleshooting have you done with this issue?

Looks like you're right. After I restarted the VirtualCenter service the status lights disappeared again. I'm on fully supported hardware. Mostly I've been back and forward with support. It seems like they're still trying to get a handle on a lot of the new 2.0.2 bugs. At least this one's not major.

That's not nice !
We have an ELA Platinum.
I will create a SR next monday because I spend today much time in restarting the agents and I can imagine that restarting the VCenter service would end up in loosing all status information.

Our HW is HP Proliant DL 385 G1 / G2 DL 585 HDS San ...

I am seeing the same thing also running on HP hardware

Thank You everyone!
I'm glad my trials are reproducible on supported hardware. For us at least this problem showed up sometime after a 2.0.1 patch back in early June.

Heres what I have gathered so far:
It seems to me that some of the alarms are not working properly and/or are not correctly refreshing the status lights correctly. If you remove all virtual machine alarms, your status lights will never change and will always be white (by design I believe).

Some of the alarms appear to not be changing the status color initially to green. This idea is confirmed as I have noticed that a status light will change if an alarm is triggered (maybe a CPU alarm changing from white to yellow or red, and then will return back to green). From that time on, that VM's status light appears to be working fine. The alarms not initially changing the status light are: VM CPU, VM Mem, VM Disk, VM Network

I then found that If I added either one of the following two alarms, Virtual Machine State or Virtual Machine Heartbeat, the status lights would initially turn green. The status lights continue to stay green even after restarting the Virtual Center Service, no restart of vmware-vpxa on the hosts is required.

So for right now I have added the Virtual Machine Heartbeat monitor, also thinking that maybe the status lights not working are the Virtual Center service missing some heartbeats. The only oddity I am seeing is that powered-off on virtual machines have a status of green. As it was explained to me, powered-off VMs should not display a status light... I haven't had too much time to work on that issue.

Additionally I tried setting the VM State alarm up (set yellow and red triggers to none) and this alarm also makes all status lights turn green.

I've also noticed after upgrading to VC 2.0.2 the alarm actions are not working. Even after restarting VMware-vpxa and mgmt-vmware. I was able to resolve this by disabling the alarm, then re-enabling it.

I am having the same problem with HP 585 G1 /G2 and Fuijtsu Server RX600 S1 .

I have the same issue
I think its because the VC and the ESX rebuild version is not the same
VC = 2.0.2 50618
ESX's = 3.0.2 52542

I have been opened support ticket to that no resolved yet

The lust time its work for me when the VC and ESX's rebuild was the same
VC = 2.0.0 27704
ESX = 3.0.0 27701

Maybe in 3.1.0...

Current fix from support is to run the service restart options for mgmt and vpxa; this does not work for very long however. You will find that after a day the status begins to disappear from the VMs.

Don't care about the build number.

the version is important (ESX 3.0.2 and VC 2.0.2)

I am also seeing this issue, 2.0.2 with 3.01 and 3.02 mixed.

All VMware certified IBM gear.

I also see this issue.

2.02 and 3.02 on HP DL585.

Is it ok to:
service vmware-vpxa stop
service mgmt-vmware restart
service vmware vpxa start
on a production system?
I read that the vm's could restart if you did a restart on mgmt-vmware on a non patched system?

--
Regards Falk
Sweden

I can also see this issue, certified hardware: 2.02 & 3.02 HP DL385 w/ QL4050

It seems that after the 2.02/3.02 upgrade my alarms don't work anymore. I can get them to turn "green" if I add a heart-beat alarm to the VM, however they don't trigger anymore (turn orange or red) for memory or CPU. Only the HB will produce an alarm.

I may remove every alarm and re-create. That and start a ticket with VMW so they know this is a widespread problem.

I also have this problem, very heavy!!!!

3 ESX 3.0.2 (IBM 3650) (DS4800 SAN)

1 VC 2.0.2

What's the solution?

Lieber Mailserver

Vielen Dank für Ihre e-Mail. Ich bin bis am Freitag, 5.10. ausser Haus. Ihre Nachricht wird nicht weitergeleitet.

In dringenden Fällen wenden Sie sich bitte an die Zentrale: +41 32 344 86 00. Diese wird Sie mit einer zuständigen Ansprechperson verbinden.

Freundliche Grüsse
Markus Blunier

The solution is to edit every alarm, and change the values for warn and alarm to something new and apply. Then edit the alarms and change the values back. Aparently the values get truncated during the upgrade and have to be re-created before they are actually set post upgrade.

All of my alarms are now working after editing.

Thanks Bill!
i'll try tomorrow

Bill,

Editing all of the alarms changing yellow and red values; save; and change back to original values resolved my issues with the alarms as well.

Thanks for the good work,

Todd

RESOLVED Editing alarms many thanks!!!

Ercole77

This document was generated from the following thread: Virtual Machines status not correct vissible