Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

ESXi 6.x Host unable to reset host sensors from vCenter (51821)

Last Updated: 12/27/2018Categories: TroubleshootingTotal Views: 20864Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

When resetting the host sensors, vCenter Web Client fails with the error similar to:

The "Resetting  host sensors..." operation failed for the entity with the following error message. An error occurred while trying to communicate with the remote service. See the server logs for details

Cause

This issue occurs because of warning notifications due to hardware events that have triggered sensor indicators.

Impact / Risks

Clearing sensors and warnings could be indicating hardware issues and or failures to investigate thoroughly

Resolution

Try these methods to try and address the warnings and sensors issue that may be inter-related.

Important: Before proceeding, ensure to confirm with the hardware vendor that this is not a hardware issue.

To resolve this issue, reset the event log:

Clear the BIOS Hardware Logs (IML for HP Servers and DRAC Hardware Logs for Dell Servers).

Select the ESXi host that reports the memory warning.

Click the Hardware Status tab in the vSphere Client.

Select the System event log view from the list.

Select Reset event log and click Update.

Click Reset sensors.

Restart the host.

After restarting the host, select the ESXi host and click the Hardware Status tab.

Click Update in the Alerts and Warnings view under the triggered warning.

If the warning persists:

Connect to the host using an SSH session.

Run this command in the command prompt:

/etc/init.d/sfcbd-watchdog restart

From the vSphere Client, select the ESXi host and click the Hardware Status tab.

Click Update in the Alerts and Warnings view under the triggered warning.

To clear the IPMI System Event.log file and reset the sensors:

Open vSphere Client and login locally to the host as root user.

In the vCenter Server Inventory, select the ESXi/ESX host.

Click the Hardware Status tab.

Click System Event log under View.

Click Reset Event Log. ...

Click Reset Sensors to reset the host sensors.

Note:

If the issue persists, place the host in the maintenance mode and then remove and re-add it to the cluster.

If you see warnings and alerts related to memory and IPMI alert, see "Host IPMI system event log status" alarm in vCenter Server (1033725).

Related Information

vCenter Web Client fails when updating or resetting the host sensors (2150577)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 6.0.x

VMware vCenter Server 6.0 Beta

Take Our Survey

Support Assistant