[VMware vCenter - Alarm Health status changed alarm] com.vmware.vim.sms status changed from green to yellow

Got this error message in my email today:

-------- Original Message --------

From :
To :
Cc :
Sent on : 10/20 07:45:11 PM CDT
Subject : [VMware vCenter - Alarm Health status changed alarm] com.vmware.vim.sms status changed from yellow to green

Target: Datacenters
Stateless event alarm

Alarm Definition:
([Event alarm expression: Status change])

Event details:
com.vmware.vim.sms status changed from yellow to green

More specifically, I got about 20 of these..switching from green to yellow, yellow to green, and back and forth and back and forth.

What to do?



Sponsored Links





Sponsored Links



a bit of digging…

And I found this thread on Communities.Vmware.Com

I just got off the phone with vmware and they confirmed that this is fixed in 4.1u1. Below are the details from the Release Notes for 4.1u1:

*************

Storage Monitoring Service synchronizations are erroneously sent as health status changed alarms
Storage Monitoring Service synchronizes its data every 30 minutes. When a synchronization occurs, the health status of Storage Monitoring Service changes to yellow. This synchronization operation is reported as a warning, which is not the intended behavior. These false warnings are delivered using the action that is set for the health status changed alarm. Therefore, the alarm can cause commands to run, or cause warnings to be sent as notification emails or SNMP notification traps.

This issue is resolved in this release. Warnings are no longer sent for this synchronization operation.

*************

Release Notes:

http://www.vmware.com/support/vsphere4/doc/vsp_vc41_u1_rel_notes.html

First, it’s a bug, fixed in esx 4.1 update 1. My clusters are not on esx 4.1 update 1. Considering I am fairly new to ESX and vmware, I figure it may take a bit of time before I figure out how to update (including researching implications, possible downtimes, etc.etc.).

In the meantime, thankfully there is a workaround

Please try configure “Health status changed alarm” from “UNSET” to “ALERT” or others.

And so far so good…

configure Health status changed alarm from UNSET to ALERT part 1

configure Health status changed alarm from UNSET to ALERT part 2

VMware

Leave a Comment

Your email address will not be published. Required fields are marked *

Spam protection by WP Captcha-Free