Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Excessive hardware alarms may be triggered when sensors are reset to an unknown state. (78633)

Last Updated: 8/30/2020Categories: TroubleshootingTotal Views: 11651Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

In ESXi host 6.5 and later you may see events like below when wbem is not able get the hardware state.

The logs will be filled with events as follows:-

2020-04-02T07:20:52.877Z error hostd[2099863] [Originator@6876 sub=Default opID=4d3fd9c8-85-2e67 user=vpxuser:management] IpmiIfcSdrReadRecordId:record id: 3D, error 192. Try again...
2020-04-02T07:20:52.877Z error hostd[2099863] [Originator@6876 sub=Default opID=4d3fd9c8-85-2e67 user=vpxuser:management] IpmiIfcSdrReadRecordId: retry expired.
2020-04-02T07:20:53.021Z warning hostd[2099863] [Originator@6876 sub=Default opID=4d3fd9c8-85-2e67 user=vpxuser:management] IpmiIfcSensorGetReading: Sensor Number 0x87, failed send cc = 0xc0
2020-04-02T07:20:53.021Z warning hostd[2099863] [Originator@6876 sub=Cimsvc opID=4d3fd9c8-85-2e67 user=vpxuser:management] Retrieve Health status failed, sensors reset to unknown state ==> All sensors get reset to Unknown.
2020-04-02T07:20:53.021Z verbose hostd[2099863] [Originator@6876 sub=Default opID=4d3fd9c8-85-2e67 user=vpxuser:management] count_events: starting communication with bmc over ipmi driver ==> Loading SEL data from IPMI.
2020-04-02T07:20:53.021Z error hostd[2099863] [Originator@6876 sub=Default opID=4d3fd9c8-85-2e67 user=vpxuser:management] count_events: ipmi returned invalid data block: data_len: 1 ccode 192  ==> Failure due to IPMI node busy.
2020-04-02T07:20:53.021Z error hostd[2099863] [Originator@6876 sub=Default opID=4d3fd9c8-85-2e67 user=vpxuser:management] sync_device_eventlog: communicate with bmc failed, no hardware sel data.

Cause

The events are generated because the error code returned from IPMI shows that queries had failed as IPMI node was busy. When the cimsvc fails to fetch the data, it resets all sensors to Unknown state.

Impact / Risks

Turning CIMSVC off will stop the plugin from polling for IPMI data and prevent reporting of hardware health information.

Resolution

This issue has been resolved in VMware ESXi 6.7, Patch Release ESXi670-202008001

Workaround

To workaround this issue apply one of the following options.

Disable wbem using the command the following command.

# 'esxcli system wbem set -e 0'.

If wbem is disabled, numeric sensor data will be refreshed via LoadStatusFromIPMI() which does not reset the sensor states (e.g. to unknown) and will not be causing excessive false alarms for numeric sensors. If wbem is disabled, any queries (like getClass, getInstance, enumInstances etc.) to sfcbd will no longer work.

VMware vSphere 6.5 can report IPMI data with or without wbem services running. The default is for wbem services off on new install.

How to disable or enable the CIM agent on the ESX/ESXi host (1025757)
https://kb.vmware.com/s/article/1025757

Disable CIMSVC plug-in from hostd.

Disabling CIMSVC will prevent the plugin from polling IPMI for hardware health information. Health status data would be not be monitored or reported for any of the sensors. However as Wbem(sfcb) is running queries sucg as getClass, getInstance, enumInstances etc, will continue to work.

Ensure the host in maintenance mode before proceeding.

SSH to the ESXi host.

Run the following command to stop the hostd process. # /etc/init.d/hostd stop

Take a backup of the /etc/vmware/hostd/config.xml file.

Edit the file and change the following value to false.

<cimsvc>

<path>libcimsvc.so</path>
<enabled>true</enabled>

</cimsvc>

Start the hostd process again. # /etc/init.d/hostd start

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
Workspace ONE Smartfolio 1.2 for iOS リリースのお知らせ (78570)

KB
•
Workspace ONE Email Notification Service 2 (ENS2) 1.7 for On-Premise リリースのお知らせ (78482)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

Take Our Survey

Support Assistant