https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxNjU0IiwiaGFzaCI6IjM1OTM5NjFlLTFlMTAtNDliZi04Yzk2LTk3NmY1N2FlNDdmNyJ9
Incorrect hardware status returned from vCenter 5 when collected through vSphere API
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:
<config>
....
<vpxa>
....
....
<healthSystem>
<throttleInterval>1200</throttleInterval>
</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.
| KB ID: | 1654 |
| Product: | Veeam Management Pack for Microsoft System Center |
| Version: | 5.7 |
| Published: | 2012-07-11 |
| Last Modified: | 2020-08-28 |
Couldn't find what you were looking for?
Below you can submit an idea for a new knowledge base article.
Report a typo on this page:
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Spelling error in text
Knowledge base content request
