Veeam Support Knowledge Base
Incorrect hardware status returned from vCenter 5 when collected through vSphere API

Incorrect hardware status returned from vCenter 5 when collected through vSphere API

KB ID:	1654
Product:	Veeam Management Pack for Microsoft System Center
Version:	5.7
Published:	2012-07-11
Last Modified:	2020-08-28

By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

Oops! Something went wrong.

Please try again later.

Challenge

When nworks uses "Refresh Hardware" calls, hardware status is not updated on vSphere 5

Cause

vSphere 5 does not update the hardware status data available through API - this can be verified in vSphere Managed Objects Browser, which shows an outdated status, while the host MOB will show the correct status. By default, this information is not updated in vCenter 5. The VI Client, however, has the valid data, since it uses CIM service for watching the sensor readings.

Solution

Solution available with nworks 5.7: ensure CIMXML is working properly. Refer to KB1568 for more detail.

Workaround provided by VMware:

To avoid the discrepancy between VC MOB and ESX MOB, you have to configure "throttleinterval" (in seconds) in \etc\vmware\vpxa\vpxa.cfg file (found on the host) as below:

....

<vpxa>

....

</healthSystem>

</vpxa>

<workingDir>/var/log/vmware/vpx</workingDir>

Then run the below command to restart vpxa:

services.sh restart vpxa

No other services need to be restarted.

More Information

Applying the workaround causes significant amount of host syncs at idle time and affects VC scalability, so it is not recommended to configure very frequent updates.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

Product

Topic

Description

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Verify your email to continue your product download

We've sent a verification code to:

An email with a verification code was just sent to

Didn't receive the code? Click to resend in sec

Didn't receive the code? Click to resend

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.