VMware Cloud Community
Gabrie1
Commander
Commander
Jump to solution

[VCOPS] updated alert Type:Health, Sub-Type:Faults, State:Critical, Kind:VMwareAdapter Instance,

"

Alert was updated at Fri Dec 06 03:51:40 CET 2013:

Info:vCenter Service Overall Health Changed

Alert Type : Health

Alert Sub-Type : Faults

Alert State : Critical

Resource Kind : VMwareAdapter Instance

Resource Name : vcdvc013 - Productie LGF

Alert ID : 18036

VCOps Server - xxxxxxxxxx

Alert details

Anomalies:

Resource

Metric

Message Info

vcdvc013 - Productie LGF

vCenter Service Overall Health Changed

"

What are these messages? Can't really figure out what this is about and where to look for the problem.

Has this something to do with vCOPs being unable to talk to the vCenter Server?

http://www.GabesVirtualWorld.com
Reply
0 Kudos
1 Solution

Accepted Solutions
gradinka
VMware Employee
VMware Employee
Jump to solution

This is alert of type "Fault".

Fault alerts are directly reported by vCenter, e.g. there is no smart logic here on the vcops side, it just reports what vCenter is saying.

vCenter has it's own concept of "Health", which has nothing to do with vc ops, and is based on self-monitoring of it's own services.
You can view the current Health in Vi-Client (old one), go to Home->Administration->vCenter Service Status

In addition, there is some service on the VC side which reports that health value to the outside world, like vcops. If that service is down, vcops can't get the current value and will report that VC health is changed to "unknown".

So basically, go and look into your VC Smiley Happy

Alternatively, you can cancel the Fault from vcops.

View solution in original post

Reply
0 Kudos
3 Replies
gradinka
VMware Employee
VMware Employee
Jump to solution

This is alert of type "Fault".

Fault alerts are directly reported by vCenter, e.g. there is no smart logic here on the vcops side, it just reports what vCenter is saying.

vCenter has it's own concept of "Health", which has nothing to do with vc ops, and is based on self-monitoring of it's own services.
You can view the current Health in Vi-Client (old one), go to Home->Administration->vCenter Service Status

In addition, there is some service on the VC side which reports that health value to the outside world, like vcops. If that service is down, vcops can't get the current value and will report that VC health is changed to "unknown".

So basically, go and look into your VC Smiley Happy

Alternatively, you can cancel the Fault from vcops.

Reply
0 Kudos
achvn
Enthusiast
Enthusiast
Jump to solution

Hi,

I'm OO0, with no access to my emails and will be back on Tuesday the 5th of November.

Thank you,

Best Regards,

Alexis

Reply
0 Kudos
mlebied
Enthusiast
Enthusiast
Jump to solution

This is an ambiguous message the vcops is reading from vCenter, but not bringing the alert payload over. It gives an indication of a health problem in vCenter. Check the vCenter and ESXi logs carefully and you’ll find the source of the problem.