Unsolved
This post is more than 5 years old
1 Rookie
•
47 Posts
0
119458
February 3rd, 2016 15:00
OME producing warning that virtual machine detects loss in guest heartbeat
We are having an issue where our OME (v2.0.1.2222) is producing warnings that multiple virtual machines on several of our virtual hosts are detecting a loss in guest heartbeat. An example warning:
Virtual machine detects a loss in guest heartbeat: vmID=3, vmConfigFile=/vmfs/volumes/50eee92f-46efd4ae-c4b1-001018f4dec0/rejsdce/rejsdce.vmx ,vmDisplayName=rejsdce
With each and every warning, 30 seconds later an info alert comes in saying the virtual machine detects or regains the guest heartbeat. An example info alert:
Virtual machine detects or regains the guest heartbeat: vmID=4, vmConfigFile=/vmfs/volumes/50eee92f-46efd4ae-c4b1-001018f4dec0/rejsdce/rejsdce.vmx, vmDisplayName=rejsdce
I'm not sure exactly how long this has been occurring, I was only made aware of it last week, but I know this was not happening 3-4 months ago. We recently updated all our virtual hosts' VMware ESXi from v5.5.0 Update 2 to v5.5.0 Update 3 Patch 81 (build-3343343) Kernel 5.5.0 (x86_64), and are in the process of updating our VMware Tools from v9.4.10, build-2092884 to v9.4.15, build-2827462--though the loss of guest heartbeat warning occurs on both Tools versions.
DELL-Pupul M
2 Intern
•
1K Posts
0
February 8th, 2016 06:00
Hi Kevina,
So, i will try to answer the question with what i understood as i really did not find a question anywhere. OME receives the alert from a device which generates the alert. The alert which you must be seeing in OME is generated on the target servers, so you may want to look at fixing it there. Unfortunately, i am not an ESXi expert and would not be able to help you much with any such problems specific to ESXi 5.0 U3. You may be able to find more answers on vmWare blogs and website.
BorislavVitanov
9 Posts
0
February 9th, 2016 07:00
Hi Dell-Pupul
I receive the same warnings but I'm not sure is this a problem of ESXi or of OMA? Is this heartbeat comes from OMA checks or from some logs in ESXi ?
DELL-Pupul M
2 Intern
•
1K Posts
0
February 9th, 2016 07:00
You should be able to see these alerts in your vsphere client if they are generated from ESXi.
KevinA-REJIS
1 Rookie
•
47 Posts
0
February 9th, 2016 09:00
Hello Dell-Pupul,
I appreciate you taking the time to help.
I've checked in vSphere with the web client, the fat client, and the Veeam ONE Monitor, but there are no heartbeat warnings for any of the servers we get a warning about in OME. Additionally, I've noticed another warning we're getting in OME now:
Virtual machine is powered ON from a suspended or a powered off state: vmID=1, vmConfigFile=/vmfs/volumes/53d8ffb9-b98a9f86-7deb-e0db550a1b3e/rejststcsweb1/rejststcsweb1.vmx, vmDisplayName=rejststcsweb1
These errors are not appearing in vSphere either, and we have not suspended or powered off any of the servers we've received the warning about.
Another member of my team has spoken with VMware about the heartbeat errors, they did not have an answer but are looking into it.
BorislavVitanov
9 Posts
0
February 14th, 2016 00:00
I believe also that this warnings are from OME, because I've received these warnings from 2 of 3 servers and only on one of them I see warning about I/O latency but on the second such warnings are not presented.
DELL-Pupul M
2 Intern
•
1K Posts
0
March 1st, 2016 10:00
Hi,
When you double click on the alert that you receive, you will see the details of that alert like Enterprise OID, source system, etc. If you just google about the enterprise OID, you should be able to figure out what that alert means. OME does not generate any alert except system up/down or health change alerts if enabled. OME just acts a receiver of these alerts to the user.