Persistant Warning On VMs

[Eldron]

I upgraded from 2.0.1 to 2.5 a few weeks ago. Since that point I have been getting random warning and error flags on some VMs in VC. The condition will have cleared up, but the warning next to the name does not clear. If I reboot my VC server, it will clear up. Any ideas on why this happens, or what I can do to fix this behavior</span>?

[DigitalVoodoo]

This is a known issue/bug with VC - in fact, I've had the same issues since going to VC 2.0 While there isn't a definative fix, disabling/re-enabling the alarms (Hosts and Clusters, Alarms, Definitions, double-click an alarm and toggle the Enabled check box) will clear the incorrect alarms without having to bounce your VC server.

[snapper]

One thing that does seems to make a big difference, is to make a small configuration change in the alarm definitions.

For each alarm, edit the configuration and go into the reporting tab

Modify the Tolerance and Frequency values to something reasonable (they aren't by default).

ie, For Host CPU usage, change the tolerance to 5% and frequency to 120 seconds.

You will find that the alarms work much better. Adjust the settings over time to what suits your environment, if you use it for notification (email or snmp) etc.

SP

[Eldron]

Thanks for letting me know this. I was unaware of this bug.