Start a Conversation

Unsolved

This post is more than 5 years old

A

7086

August 9th, 2018 11:00

R620 ESXi 6.5 CIM data Unknown

Hello, I finally upgraded my servers to ESXi 6.5 U2 with the Dell Customized images. (VMware-VMvisor-Installer-6.5.0.update02-8294253.x86_64-DellEMC_Customized-A00.iso -- I didn't use build 8935087 because I had already downloaded the previous one and didn't notice that they were different versions).  At the same time, I upgraded the iDRAC Enterprise and lifecycle controller to 2.60.60.60, and BIOS to 2.7, then downloaded the update bootable media (https://dell.app.box.com/v/BootableR620) to ensure that everything was up to date; as far as I can tell, everything is.
Now, when I monitor the server hardware health in vcenter, I'm seeing a lot of "unknown" statuses.  In particular; memory, "other", and Watchdog.

Am I missing a driver somewhere?

I'm also getting emailed alerts from iDRAC about the watchdog which is rather annoying. I can't see any other details about why it's failing;

Event Message: The watchdog timer expired.
Severity: Critical
Detailed Description: The operating system or potentially an application failed to communicate to the baseboard management controller (BMC) within the timeout period.
Recommended Action: Check the operating system, application, hardware, and system event log for exception events.
Message ID: ASR0000



I also came across this Dell article explaining that this can happen, but the resolution does nothing to remedy the issue.

Does anyone know what's going on here?


cim data unknown.png

Moderator

 • 

8.7K Posts

August 9th, 2018 14:00

Hi,

Try the steps in this article. https://kb.vmware.com/s/article/2148520

5 Posts

August 10th, 2018 10:00

Hi, thanks for the reply, but I don't think this KB applies to me. Although I did upgrade from 5.5 to 6.5, I'm using vCenter 6.5 U2b with ESXi 6.5 U2 (EMC DELL customized) and the problems mentioned in the article are resolved in 6.5 U1d.  I might try and upgrade to 6.5 U2b (although I don't see a Dell version of that yet).

I'm not getting the error "No host data available", I'm just getting "Unknown" in certain Hardware Status as per the screenshot.
While looking through some of those logs in that KB, I did notice that I'm getting similar errors in the vsphere_client_virgo.log file, so it's definitely something related.

[ERROR] data-service-pool-800        70018808 100725 200610 c.v.v.c.c.cimdataadapter.impl.HealthInfoToCimDataAdapter          returning unknown, unexpected rateUnit value: DMI-discrete
[ERROR] data-service-pool-790        70018837 100725 200610 c.v.v.c.c.cimdataadapter.impl.HealthInfoToCimDataAdapter          returning unknown, unexpected rateUnit value: int-drive
[ERROR] data-service-pool-795        70018865 100725 200610 c.v.v.c.c.cimdataadapter.impl.HealthInfoToCimDataAdapter          returning unknown, unexpected rateUnit value: ACPI-discrete

5 Posts

August 10th, 2018 11:00

(somehow my reply didn't post - strange - I'll try and repost)

Thanks for the reply, but I don't think that KB applies to my situation.  I'm not getting that error specifically and I'm running ESXi 6.5 U2 where that KB states that the error is fixed with 6.5 U1d.

While looking through the vsphere_client_virgo.log files, I am seeing similar errors flooding it which must be related somehow. It's definitely a problem with the CIM provider.  Here are some snippets;

[ERROR] data-service-pool-794        70019225 100725 200610 c.v.v.c.c.cimdataadapter.impl.HealthInfoToCimDataAdapter          returning unknown, unexpected rateUnit value: ACPI-discrete
[ERROR] data-service-pool-790        70019267 100725 200610 c.v.v.c.c.cimdataadapter.impl.HealthInfoToCimDataAdapter          returning unknown, unexpected rateUnit value: int-drive [ERROR] data-service-pool-790        70019244 100725 200610 c.v.v.c.c.cimdataadapter.impl.HealthInfoToCimDataAdapter          returning unknown, unexpected rateUnit value: watchdog
[ERROR] data-service-pool-795 70019259 100725 200610 c.v.v.c.c.cimdataadapter.impl.HealthInfoToCimDataAdapter returning unknown, unexpected rateUnit value: DMI-discrete
[ERROR] data-service-pool-795        70019251 100725 200610 c.v.v.c.c.cimdataadapter.impl.HealthInfoToCimDataAdapter          returning unknown, unexpected rateUnit value: predictive-discrete [ERROR] data-service-pool-795        70019251 100725 200610 c.v.v.c.c.cimdataadapter.impl.HealthInfoToCimDataAdapter          returning unknown, unexpected rateUnit value: severity-discrete
[ERROR] data-service-pool-800        70018958 100725 200610 c.v.v.c.c.cimdataadapter.impl.HealthInfoToCimDataAdapter          returning unknown, unexpected rateUnit value: unspecified(0x25)
[ERROR] data-service-pool-800        70018958 100725 200610 c.v.v.c.c.cimdataadapter.impl.HealthInfoToCimDataAdapter          returning unknown, unexpected rateUnit value: present-discrete

 This wasn't an issue on 5.5, and yesterday I loaded the Dell iSM 3.2.0 (iDRAC Service Module) vib onto my hosts, with still no change in behaviour.

 

5 Posts

August 10th, 2018 11:00

my replies keep getting marked as spam.  I've notified a moderator to see if it can be released.  I'm not typing a reply a 3rd time....

in short, the article you provided doesn't apply to me as it's marked resolved in 6.5 U1d and I'm running 6.5 U2 and also the errors don't match.  It does seem slightly related though because I'm seeing a lot of errors in the 2nd log file from that KB about CIM errors "HealthInfoToCimDataAdapter" with various errors like;
"unexpected rateUnit value: ACPI-discrete", int-drive, DMI-discrete, etc..

1 Message

October 10th, 2018 04:00

Same identical situation

Dell PowerEdge R640

ESX from 6.0 to 6.5 U2

FW upgraded to the last release

1 Message

October 11th, 2018 14:00

I have exactly the same issue happens on my Dell PowerEdge R430. I was working fine, but after I upgrade Dell BIOS, some sensor status become unknown. I upgrade VMware ESXi 6.5 to "DellEMC Customized Image ESXi 6.5 Update 2 A00 (based on ESXi VMKernel Release Build 8294253)" but still cannot solve this issue.

1 Message

October 22nd, 2018 09:00

Check this out. I'm running into the same issue https://kb.vmware.com/s/article/57171
No Events found!

Top