Errors com.vmware.vim.sms status changed

[savoy6]

i keep seeing these errors about every two hours "com.vmware.vim.sms status changed from red to green and from green to red. Any ideas on what this means?

Running ESX4, vCenter4.

Thanks ,

Savoy6

[prudhviraj]

So Jonathan any update on this thing...

As of now Is disabling ' health status changed ' alarm, the only workaround to this issue??

Thanks in advance...

[gordons_alive]

We're seeing the same thing (vSphere U2). What's frustrating is that the 'Health Status Changed Alarm' is only configured to send an SNMP trap when the status changes from yellow to red, however, SNMP traps are being sent when the status goes from green to yellow or vice versa which shouldn't happen. The end result is that we're getting unwanted noise in our alerting tools.

Does anyone have an update on this?

[jasoncllsystems]

I have the similar problem and it go off after power off the VDR.

Regards,

jlchannel

MALAYSIA VMware Communities

http://www.malaysiavm.com

'If you found this or any other answer useful please consider allocating points for helpful or correct answers ***

[Nixia]

We upgraded to 4.1 and we are still seeing the same behaviour as gordons_alive = receiving an unconfigured alert. I dont mind that it happens just stop telling me about it LOL

[rodler]

hi!

we did an new install of vsphere server 4.1.

same problem!

any news?!

tnx! gerald

[newcal]

Je suis absent jusqu'au vendredi 10 septembre, en cas d'urgence merci de contacter Melle Cindy WATU.

[jcwuerfl]

bump - same issue here with 4.1

[jsomontan]

Yeah, I'm starting to see the errors, too. I'm waiting for VMware support to call me back.

=============================================

Target: Datacenters

Stateless event alarm

Alarm Definition:

()

Event details:

com.vmware.vim.sms status changed from green to yellow

[jsomontan]

Joju from VMware suppport contacted me and we solved the issue together. It basically comes down to the trigger, at least in my case. The trigger was set to unset. So I updated trigger to be set to Alert instead of unset. And I also created another trigger to change with it changed to Normal meaning green.

See attached pic.

[jasoncllsystems]

Where is the attachment pic?

Regards,

jlchannel

MALAYSIA VMware Communities

http://www.malaysiavm.com

'If you found this or any other answer useful please consider allocating points for helpful or correct answers ***

[mastamark1]

I'm seeing this to and mine was a clean install. I just get this about once per day vs. multiple times a day. (at least thus far.)

I'd love to stop getting these things.

[jasoncllsystems]

This is happen on ESXi 4.1 as well.

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

Regards,

jlchannel

MALAYSIA VMware Communities

http://www.malaysiavm.com

'If you found this or any other answer useful please consider allocating points for helpful or correct answers ***

[mastamark1]

Ok, I just found that alert and set it from unset to alert. We'll see if that works!

Screen shots attached for those who need it in the future.

[rodler]

tnx for that, - seemed to work!

[jasoncllsystems]

Glad to hear that

Regards,

jlchannel

MALAYSIA VMware Communities

http://www.malaysiavm.com

'If you found this or any other answer useful please consider allocating points for helpful or correct answers ***

[rodler]

though, i see i do have an alarm now...?!

did you change/add something under "conditions" as well?

there are no predefined event arguments under my trigger conditions.

tnx! gerald

[mastamark1]

In my case there is nothing defined in there and the annoying 'status changed' messages have not returned.

[rodler]

did you check your alarm status in vcenter as well? in my case the "flapping" of the alarm only seemed to stop, - now it seems that the alarm stays on status "triggered"...

gerald

[ChrisS555]

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