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=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxNzAzIiwiaGFzaCI6IjljYTFhOTFhLWQxMmEtNDkzMS1hOWNiLWM4M2U0ZDI2YmY5ZSJ9
1-800-691-1991 | 9am - 8pm ET
EN

Host hardware sensor status changed warning

Challenge

A lot of sensors are reported with the unknown state under the Host Hardware Sensor Status Changed alarm.
 

 User-added image

Cause

In version 6.5 Veeam ONE is using CIM-XML over MOB to monitor hardware status.

Prior to v6.5, some hardware sensors did not return the correct status due to a known VMware issue - when host's sensors display wrong status via vCenter Server's Managed Objects Browser (MOB). In v6.5 a more accurate hardware monitoring protocol CIM-XML is used, which completely eliminates such behavior. Be aware that vSphere Client uses the same protocol to obtain sensors' states.

Moreover, starting with Veeam ONE v6.5 the hardware monitoring became more granular, and you may notice way more sensors available in v6.5 compared to v6.0. But for some sensors, VMware does not have any state and returns the 'unknown' status. Please keep in mind that the correct state for 'well-known sensors' is always available via CIM-XML (which is utilized by Veeam ONE by default).

User-added image

The alarm may or may not be triggered depending on the deployment scenarios of Veeam ONE 6.5. If you have fulfilled an upgrade from 6.0 to 6.5, the alarm will be triggered.


User-added image
 User-added image
If you have fulfilled a fresh installation of 6.5, the alarm will not be triggered, although some of the sensors may be reported with the 'unknown' state on the Hardware tab.

 User-added image

The actual state of error and warning, however, should trigger the alarm as expected.

Solution

Be sure to compare sensors' state in Veeam ONE and on hosts' Hardware Status tab in vCenter Client, as well as to check the VMware rollup state in vCenter and host MOB as described in KB1007.

More information

Patch #1 does not fix this behavior.
KB ID:
1703
Product:
Veeam ONE
Version:
6.5.0.676, 7.x
Published:
2013-04-09
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

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!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.