HEARTBEAT status problem: The Heartbeat state of several virtual machines toggles from critical to OK and back again.

book

Article ID: 51671

calendar_today

Updated On:

Products

CA Server Automation CA Virtual Assurance for IM

Issue/Introduction

Description:

Traps are sent from AIM in an interval of several minutes indicating the status changes "from Critical to Normal" and "from Repaired to Critical".

Solution:

Example of traps sent from AIM:

VMware Virtual Center VM HeartBeat State Change Trap - VM SVIE3IFMST1 under ESX Server svie13esxdev1.vie-i.local, ResourcePool
N/A, Cluster RZ1-DEV-TEST, Datacenter RZ1-FWAG, VC SVIE12VMVC1 HeartBeat State changed from Critical to Normal

VMware Virtual Center VM HeartBeat State Change Trap - VM SVIE3IFMST1 under ESX Server svie13esxdev1.vie-i.local, ResourcePool
N/A, Cluster RZ1-DEV-TEST, Datacenter RZ1-FWAG, VC SVIE12VMVC1 HeartBeat State changed from Repaired to Critical

The Heartbeat state is always seen as OK in VC.

Follow the steps from the Vmware link:

http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&externalId=1017091&sliceId=1&docTypeID=DT_KB_1_1&dialogID=74739420&stateId=0%200%2074741268

This stopped the up and down messages seen on the ESX server but did not stop the problem as above.

A few tests were run using open source tool (using VC API) for the VC server in question and it resulted in the same heartbeat messages being observed as in this issue. However, no message is showing up in the VC Console itself.

This is a problem from Vmware. VMWare has recognized this problem and will come up with a fix (no date available at this time).

Environment

Release:
Component: VCAIM