Loading

×Sorry to interrupt
CSS Error

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

vSphere ESX/ESXi hardware status sensors return different cached values in API than in vSphere Client (1037330)

Last Updated: 1/11/2017Categories: Total Views: 6502Language:
English

5 like this article

Subscribe to get an email
newsletter with new updates

5 people found this helpful Please provide article feedback:

Symptoms

PowerCLI and other API methods may report different sensor values for ESX/ESXi host status, as compared to the vSphere Client connected to vCenter Server.

For example, a list of non-green sensors obtained via PowerCLI may contain sensors which the vSphere Client reports as green:

Get-VMHost myesxhost |
% {(get-view $_.id).runtime.healthSystemRuntime.systemHealthInfo.NumericSensorInfo |
Where-Object {$_.HealthState.Label -notmatch 'Green'}}

Could return the result:

Name : VMware Rollup Health State
HealthState : VMware.Vim.ElementDescription
CurrentReading : 0
UnitModifier : 0
BaseUnits :
RateUnits :
SensorType : system
DynamicType :
DynamicProperty :

Resolution

This issue can occur when information being fetched is cached. The vmware-hostd management service refreshes hostd health information via CIM every 90 seconds, with back-off up to 10 minutes. The cache can be refreshed using the vSphere API call RefreshHealthStatusSystem() prior to retrieving health status information.

For example, to refresh health status information from PowerCLI:

(Get-View (Get-VMHost -Name esxhostname | Get-View).ConfigManager.HealthStatusSystem).RefreshHealthStatusSystem()

Note: If refreshing the sensors does not update the returned information, the sensors may be stuck in unhealthy states. To reset the state of the sensors in the IPMI subsystem, use the vSphere API call ResetSystemHealthInfo(). For example, to reset the IPMI sensors from PowerCLI:

(Get-View (Get-VMHost -Name esxhostname | Get-View).ConfigManager.HealthStatusSystem).ResetSystemHealthInfo()

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

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 vSphere PowerCLI

VMware vSphere ESXi

VMware vSphere

VMware VirtualCenter

VMware vCenter Server

VMware Infrastructure SDK

VMware ESX Server

VMware CIM SDK for ESX

VMware CIM SDK

VI Toolkit (for Windows)

VI SDK

VI Perl Toolkit

view all

Related Versions:

VMware vSphere Web Services SDK 4.1

VMware vSphere SDK for Perl 4.1

VMware vSphere SDK for Perl 4.0

VMware vSphere PowerCLI 4.1

VMware vSphere PowerCLI 4.0

VMware VirtualCenter 2.5.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

VMware Infrastructure SDK 2.0.x

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESXi 3.5.x Installable

VMware ESXi 3.5.x Embedded

VMware ESX Server 3.5.x

VMware ESX 4.1.x

VMware ESX 4.0.x

VMware CIM SDK for ESX 3.0

VMware CIM SDK 4.1

VMware CIM SDK 4.0

VMware CIM SDK (SMASH - SMI-S)

VI Toolkit (for Windows) 1.5

VI Toolkit (for Windows) 1.0

VI SDK 2.5

VI SDK 2.0

VI Perl Toolkit 1.6

VI Perl Toolkit 1.5

VI Perl Toolkit 1.0

view all

Take Our Survey

Support Assistant